Corrections appreciated.
This is required blogging…and reading for that matter. A good chunk of this is taken from my CCNP posts from last year. Corrections, please.
Make my corrections! Please!
Corrections appreciated.
Corrigeme, por favor.
You can configure an EIGRP router to filter routes from being advertised or from being accepted.
Per the standard rules, please correct anything that’s wrong.
One of EIGRP’s big features is the ability to use unequal cost paths for load balancing. This is done with the variance command.
Please correct if I’m being stupid…which is a lot of the time. Hello : Discovers and maintains neighbors Destination: 224.0.0.10 Important fields: K values Update : An update to the topology such as a route withdrawal or a metric change Destination: 224.0.0.10 -or- unicast during neighbor discovery Important fields: Message sequence number Route being updated including k […]
Corrections are always welcome.
I got a call from our Systems and Security guys today to talk about a Wireshark capture they had done from a user VLAN. They had noticed two frames that were destined for some seemingly random host in the same network as they were in, but the source and destination IP addresses reported by Wireshark made no sense. The frames were from a web server to an IP address on our wireless network. The web server is on the other side of the firewall, and the wireless network is on the other side of the controller; there was no reason at all that a packet with that source and destination would show up here.