Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:Cell phone uses IPv6 (Score 1) 295 295

This is actually something you configure on your own computer. The FreeBSD command for doing it is ip6addrctl. I'm not sure what it's called on other systems. Also, note that the FreeBSD man pages are vague. You will also need to rfc-3484 to actually be able to use it. The man pages say it affects source and destination address selection, but they don't say how. It has two effects:

1. The command controls the sort used for DNS results. The default is to sort IPv6 addresses first. Properly converted applications actually get a list of IP addresses back from DNS and they are supposed to try them in order until the get one that works.

2. The command also controls which source address is paired with a destination address. This is less important, but something one might occasionally want to do.

For most ISPs in the US, it probably makes more sense to sort IPv4 first. At least for the next few years.

Comment: Re:Cell phone uses IPv6 (Score 1) 295 295

Somebody has to log in to a rather large number of routers and switches to enable IPv6 and possibly do a firmware upgrade, first. In case you haven't done it, yet, upgrading the firmware on a router/switch is the computer maintenance equivalent of going to the dentist. Especially when you save your configuration and the new firmware doesn't recognize the config file...

BTW, my cell phone has an IPv6 address, too.

Not sure how true this is, but I have heard that some of the large phone companies have so much internal switching equipment that they have run out of internal IPv4 addresses for the switching equipment (not to mention end user devices).

Comment: Why? (Score 1) 257 257

We have been maintaining Stratus VOS since 1980, but it hasn't stayed static and it's very much larger than it was in 1980.

Which gets me to my real point. If you aren't going to maintain it, keep the binaries. If you are going to maintain it, it won't be in a vacuum; so, you will need to move the software into new environments.

Comment: Re:From the TFA (Score 1) 389 389

Yeah, he hired a DJ. And he said he thought the DJ paid the licensing fee. I know that musicians hired to do gigs aren't required to pay BMI, the venue owner is. I would assume that's also true with DJs. The restaurant owner is either clueless (but he's been in business for 25 years) or he's lying through his teeth. He also claimed that he didn't have to pay royalties because he had a license to have music from the city. You are not looking at an even remotely reliable source of information here.

I can tell you as a musician that most restaurant and bar owners are at least 10 times as sleazy as the RIAA or BMI or any other rights organizations have ever been. They will exploit all their employees, including musicians and DJs, every chance they get. They deserve absolutely no sympathy.

Comment: Re:It's not a networking issue. (Score 1) 384 384

It will only work if the destination has a broken IP implementation. IFF the implementation is correct, it's supposed to either forward or drop any IP packets with a destination that isn't configured on the interface. It's never supposed to process them locally. Of course on a POS that you can't change the IP address on, one can't be sure it's actually handling the IP protocol correctly. Which would mean that putting more than one of them on a switch is probably a bad idea.

Comment: Re:You're offtopic but I'll answer anyway. (Score 1) 384 384

ICMP uses IP.

You are correct that ARP doesn't use IP.

The LAT protocol doesn't use IP, but nobody uses LAT any more.

There used to be audio distribution protocols that ran in the MAC layer on 100Mb Ethernet, but I believe they switched to running under IP when switches and routers learned how to do vLans and QOS.

Appletalk used to avoid IP, but I believe they switched, too.

Protocols the use IP are routeable; so, they are limited in utility.

See for a more complete list.

Comment: Re:It's not a networking issue. (Score 1) 384 384

Mucking with the ARP tables won't work, because the IP addresses will be wrong in the packets (unless the IP implementation in the pumps is sorely lacking).

OTOH, using vLans on a cheap managed switch is better than the 16 USB Ethernet adapters the poster suggested.

"This is lemma 1.1. We start a new chapter so the numbers all go back to one." -- Prof. Seager, C&O 351