On 05/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Problem : I have configured my network to be up on boot, but when I checked in > network, I found it inactive, on activating it, it became active for around > 20-30 sec and automatic inactive, but during this 20-30 sec i can ping to > other > PC on network. > > Nov 5 10:52:51 localhost NetworkManager: DHCP: Got some data of length 1514. > Nov 5 10:52:51 localhost NetworkManager: DHCP: Reply message had mismatch in > length (IP header said 2772, packet was really 1514), won't use it.
Packet length 1514 is normal - it is what you get on ethernets with MTU = 1500 (1500 + 6 bytes source MAC + 6 bytes dest. MAC + 2 bytes forgot what - type, I think). Whoever is fragmenting this packet is not updating the IP header. I think buggy TCP/IP stack on something. > Nov 5 10:52:51 localhost NetworkManager: DHCP: Got some data of length 52. > Nov 5 10:52:51 localhost NetworkManager: DHCP: Reply message was not UDP > (ip_hdr->protocol = 6, IPPROTO_UDP = 17), won't use it. Another indication of buggy TCP/IP implementation. Sending UDP packets with ip_hdr->protocol set to IPPROTO_TCP. > Nov 5 10:52:52 localhost NetworkManager: DHCP: Reply message's source port > (137) was not the DHCP server port number (67), won't use it. Clue 3: 137/UDP is Netbios name service - essentially, a windows-only thing. Is your DHCP server on Windows? Binand ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ linux-india-help mailing list linux-india-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-india-help
