I am not certain but I think that you do not want to NAT here as the proxy
will already put the external address on the packet when it issues the proxy
connection. It may be getting confused as you are trying to NAT the packet
to the external address of the box before handing the packet to SQUID.
Re: WinRoute Pro ... the NAT table for I believe. ...packet logging shows some nice information but other times the ... when the connection is torn down from the client side ... (comp.security.firewalls)
Re: Anonymizing Packets yet ensuring 0 % packet loss ... I am interested to do something at packet level cos setting up a proxy... and you call us criminals.... My crime is that of curiosity. ... (Security-Basics)
Re: RRAS Win2003: Cannot reach public IP reserved hosts behind our NAT ... From within our intranet we can access the machines by> their private addresses just fine, as these packets are not> routed to our RRAS box. ... The role of the IP# in Ethernet is only to provide a Layer3 routing> mechanism and to provide a means to resolve the MAC address. ... The> reason intranet host must use the private addresses to access the servers is> because NAT can't make "u-turns". ... When you send a packet to the external> IP# the "NAT" process takes it and creates a situation where the source and> destination MAC addresses in the packet headers are the same address. ... (microsoft.public.windows.server.networking)
Re: Weird NAT/Routing Issue. ... Try using "ip nat outside source static" instead. ... When the packet travels from outside to inside, translation occurs first, ...Translates the source of the IP packets that travel outside to ... (comp.dcom.sys.cisco)
