Good stuff, great summary of a couple things many don't often think of! Its funny I see the static default out an Gig Eth a lot, mostly in places where it was changed from pointing out a serial interface without any thought to what that syntax actually means. When the new circuit comes in with an ethernet hand off they just pointed the route that way.
Hi Ryan, I have a couple of question regarding this, 1. Why would we misconfigure Host B. Any specific requirement in real world. 2. And if everything is configured with /24 mask, at that time also do we need PROXY-ARP. 3. Can you please tell me some example with firewall .
Another situation I sometimes come across is on L2 switches, where the default gateway is set to an IP address that isn't in the subnet of the vlan interface of the switch's mgmt vlan. For instance, a L2 switch will have an interface vlan with an IP = 10.100.0.1/24, however the default gateway is set to 10.200.0.1 (on a different subnet). In this case, when the switch arp's for it's gateway's MAC (who own's 10.200.0.1), it must rely on the upstream L3 switch to perform proxy arp to allow for the arp response to get resolved. The L2 switch's mgmt vlan (10.100.0.1) acts just like an end-node trying to resolve a MAC for traffic not on his subnet. Make sense?
Great explanation! Just to make sure I fully understand - the only reason that customers service worked (the one with the next hop as a port) is because Verizon's router had proxy arp enabled, right? Without it enabled, it would see arp requests for ip's way outside of it's subnet and ignore them, right
Наука
Good stuff, great summary of a couple things many don't often think of! Its funny I see the static default out an Gig Eth a lot, mostly in places where it was changed from pointing out a serial interface without any thought to what that syntax actually means. When the new circuit comes in with an ethernet hand off they just pointed the route that way.
Thanks a lot, glad you enjoyed it :)
Thanks for the video. Came to understand Proxy ARP. I now understand Proxy ARP. Good job!
Thanks for all your hard work Ryan. We appreciate you!
Wow! Thanks a lot for the video. Very clear and fast explanation.
This cleared up a lot for me Ryan, thanks alot!
Hi Ryan,
I have a couple of question regarding this,
1. Why would we misconfigure Host B. Any specific requirement in real world.
2. And if everything is configured with /24 mask, at that time also do we need PROXY-ARP.
3. Can you please tell me some example with firewall .
Thanks Ryan, that was a nice explanation.
Another situation I sometimes come across is on L2 switches, where the default gateway is set to an IP address that isn't in the subnet of the vlan interface of the switch's mgmt vlan. For instance, a L2 switch will have an interface vlan with an IP = 10.100.0.1/24, however the default gateway is set to 10.200.0.1 (on a different subnet). In this case, when the switch arp's for it's gateway's MAC (who own's 10.200.0.1), it must rely on the upstream L3 switch to perform proxy arp to allow for the arp response to get resolved. The L2 switch's mgmt vlan (10.100.0.1) acts just like an end-node trying to resolve a MAC for traffic not on his subnet. Make sense?
Very clear explanation, Thank you Ryan
Good explanation. Moreover inclusion of a practical example made it more valuable. Thanks :)
Great explanation! Just to make sure I fully understand - the only reason that customers service worked (the one with the next hop as a port) is because Verizon's router had proxy arp enabled, right? Without it enabled, it would see arp requests for ip's way outside of it's subnet and ignore them, right
Superb, got the difference.
Very clear explanation, ThankS
superb explanation
Okay but what if we get assigned a different ip address from the ISP after ever new ppp session established with it?
Excellent.
that was really useful :) thanks a lot
nice explanation...
like it! thank you so much.
Amazing !
Thank you
Thanks