06-02-2014 11:33 AM - edited 03-11-2019 09:16 PM
Solved! Go to Solution.
06-02-2014 12:03 PM
Your recent experience may not have had anything to do with NAT per se even though that's how it manifested itself most obviously to you.
I suspect it may have had to do with your upstream gateway's arp cache. I have often seen when replacing hardware that we need to ask the ISP to flush their ARP cache so they can re-learn the new MAC address association to your pre-existing IP.
In any case, NAT should not be adversely affected when migrating from 8.4(1) to 9.1(x).
06-02-2014 12:03 PM
Your recent experience may not have had anything to do with NAT per se even though that's how it manifested itself most obviously to you.
I suspect it may have had to do with your upstream gateway's arp cache. I have often seen when replacing hardware that we need to ask the ISP to flush their ARP cache so they can re-learn the new MAC address association to your pre-existing IP.
In any case, NAT should not be adversely affected when migrating from 8.4(1) to 9.1(x).
06-03-2014 04:53 AM
As Marvin stated, your problem is more likely to be ARP related than NAT related. However depending on your nat configuration, i would advise you to look at the release notes for 8.4(2-5) as there are some changes regarding proxy-arp that might affect you.
06-03-2014 05:26 AM
Jan, thanks for the info. I certainly will check it out. I know that 8.4 change the NAT game and this configuration was an upgrade from 8.2x.
Regards,
Dave
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide