Terry Lambert writes: >> If Linux is using 0x0666, we should probably pick a different number >> since we're not wire compatible. Though coming up with a common >> protocol would be even better. > 0x666 hex is 1638 decimal, and it's taken: > > cnip 1638/tcp CableNet Info Protocol > cnip 1638/udp CableNet Info Protocol > > Basically, this is just an experimental protocol that's being played > with here, and if it ever becomes real, then it will need an IANA > protocol number assignment before it's widely deployed. Sure you're not mistaking tcp port numbers for ip protocol numbers now? ;) - arnvid -Received on Tue Oct 28 2003 - 16:10:40 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:26 UTC