Messages in this thread | | | From | "Eloy A. Paris" <> | Subject | Re: TCP/IP endianess problem??? | Date | 24 Feb 1999 13:29:36 GMT |
| |
The thing is that everything works fine when I boot 2.0.36, so I don't know if it is Windows related or 2.2.2 related.
peloy.-
George Bonser <grep@shorelink.com> wrote: > On 24 Feb 1999, Eloy A. Paris wrote: > >> 00:50:38.467533 8.73.80.157 > 5.80.130.151: (frag 4:94@5304) [tos 0xff] >> 00:50:38.468145 110.2.5.120 > 5.82.130.151: (frag 260:5@5304) [tos 0xff] >> 00:50:38.607511 8.73.80.157 > 5.80.130.151: (frag 4:94@5304) [tos 0xff] >> 00:50:38.608101 110.2.5.120 > 5.82.130.151: (frag 260:5@5304) [tos 0xff] >> 00:50:38.897507 8.73.80.157 > 5.80.130.151: (frag 4:94@5304) [tos 0xff] >> 00:50:38.898111 110.2.5.120 > 5.82.130.151: (frag 260:5@5304) [tos 0xff] >> 00:50:39.407456 8.73.80.157 > 5.80.130.151: (frag 4:1100@5304) [tos 0xff] > > I have also noticed this backwards IP address thing with Windows machines > on the LAN and I am also running Debian. > > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |