Can't get port forwarding to work (LinkSys)

From: Robert Oschler (Oschler@earthlink.net)
Date: 07/03/02 

From: "Robert Oschler" <Oschler@earthlink.net>
Date: Wed, 3 Jul 2002 12:07:05 -0400

I have a LinkSys BEFSR41 router with some Windows boxes and one Linux box
behind it. I want to use the Linux box as a destination for a Port
Forwarding operation. I setup the Linux box with a static IP address and
verified that it worked, it did. I put an entry into the LinkSys router's
Port Forwarding table for the desired port range, and put the Linux box's
now static IP address in as the destination.

When I try to access the Linux box through a client external to the router,
I fail to connect. Here's how I run the test:

On the Linux box I start the server program that listens for any incoming
connection on the port # entered into the router's port forwarding table. I
know this program works because other sibling stations on the LAN behind the
router can connect to it without problem.

Using a computer with a dial-up connection which is running a custom TCP-IP
client program, I enter the LinkSys router's WAN IP address and the port
number I entered into the Port Forwarding table, into the Connect settings
field of my test client program. (Note: this program connects fine with
other stations on the LAN.) The connection fails with a 10060 error.

I tried pinging the router using its WAN IP address, but the request timed
out and I'm guessing its because the router doesn't respond to pings for
security reasons. I know the WAN IP address is valid, because if I connect
to the dial-up station FROM a system behind the router, the router's WAN IP
address shows up as the IP address of the connecting client.

Any ideas? I tried this with DHCP disabled on the router and with it
enabled, didn't work in either configuration.

thx

Relevant Pages

  • Re: uCLinux on Samsung S3C4510B (ARM7TDMI) based wireless router
    ... serial port or printer port, ... linux or further. ... > router, access point and print server, all at the same time, preferably ... > and openap-ng) options as well as uCLinux. ...
    (comp.os.linux.embedded)
  • Re: Public/Private network split.
    ... > only open up port 80, that means that the only IP application would be ... I can't answer for your Linksys router but hopefully the following ... 192.168.1.xxx including the WAN port of the new wireless router. ...
    (comp.security.misc)
  • Re: VPN problems and Linksys BEFSR411????
    ... I think you need to enable port forwarding in the Advanced ... VPN solutions that use a hash for authentication of the IP header, ... test and keep an eye on the router log during the test to see what ports. ... I might also recommend enabling logging in the Linksys to send all the log ...
    (comp.security.firewalls)
  • Re: VPN problems and Linksys BEFSR411????
    ... I think you need to enable port forwarding in the Advanced ... VPN solutions that use a hash for authentication of the IP header, ... test and keep an eye on the router log during the test to see what ports. ... I might also recommend enabling logging in the Linksys to send all the log ...
    (comp.security.firewalls)
  • Re: Guarddog blocking packets in the same zone
    ... > The Linksys is plugged in behind the Linux box into one of the ports on ... > the Linksys is connected to the same switch as the LAN PC's, ... Which port on the Linksys are you connecting to the switch? ...
    (comp.os.linux.security)