Interesting. :-) So, I've never tried hooking up a cisco to a windows machine, but wouldn't have expected this, exactly. There are two lengths in an OSPF packet (just like in TCP), one of which describes the length of the OSPF data, and the other of which describes the length of the entire IP packet. Thus, it's something like this:
IP(length of IP)(OSPF(length of OSPF)..)
If you add the length of the OSPF information to the length of the IP header, you should come up with the length of the IP packet, in theory. Well, the two implementations are computing their lengths differently, or something, because they are both complaining about the two lengths not matching. I could kindof understand it on the windows side. OSPF does use a set of extensions to the OSPF hellos called link local signalling that would make these two not match (intentionally). I don't know about the cisco giving those error messages for the windows router, though....
You might try turning LLS off, depending on the version of code you're on:
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...