On 9/13/06, Aaron S. Joyner <[EMAIL PROTECTED]> wrote:
So this post isn't entirely useless - my gut instinct is that the
problem is related to the "u-turn" problem as described, but I'm at a
loss to explain precisely the internals of why. Assuming the NAT
implementation is anything close to *sane* on the embedded router, this
really shouldn't be a problem. Then again, don't trust the Chinese or
Korean guy who wrote the firmware to have done a sensible job on his
first programming project.
I've had appliance routers (SMS I think) which refused to recognize
"U-turn" addressing.
Unlike Brian, there are routers that do this, the Netgear I'm using
now has no problem with it.
Just out of curiosity how would you set up NAT routing in Linux to do
this, with port forwarding? For example say:
wan-interface gets it's ip address from isp via dhcp
lan-interface 192.168.1.1
lan devices use 192.168.1.1 as gateway.
for requests coming from either outside or inside:
http connections to wan ip address get forwarded to 192.168.1.2
wan ssh connections to wan ip address get forwarded to 192.168.1.3
--
Rick
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
