PfSense may be attaching some kind of header to its traffic that makes my N66U not want to NAT packets coming from it This leads me to think one of these situations may be going on: If I put the CentOS 7 VM (or any other VM I have) behind those virtual appliances, my N66U performs NAT on that traffic with no issue. I have a Juniper SRX virtual image as well as a Cisco ASA virtual image on my ESXi host, and both of them are configured for NAT. However, when I try to telnet to from my CentOS 7 VM, my N66U fails to NAT the traffic to my public IP. The issue is that if I try to telnet to from pfsense directly, my N66U will NAT the LAN IP of pfsense to my public IP, and the traffic goes through. I have a CentOS 7 VM that is sitting behind pfsense, and pfsense properly NATs the traffic to it's WAN IP (192.168.1.5) but when the traffic gets forwarded over to my N66U, my N66U doesn't NAT the traffic before sending the traffic outbound to my SB6141. I'm having an odd issue where my Asus N66U running Merlin isn't doing NAT on traffic coming from my pfSense VM. Before replacing my N66U with pfSense completely, I'm trying to test out some network scenarios.
I greatly appreciate anyone here who can help.
0 kommentar(er)
