Fedora Core 2.
I have a linksys router, port forwarding (uPnP) two external ports (high numbers) to shh and http to my linux box (22,80) I can access my linux webserver via the internal network address on port 80. But I can't access them externally. I have tried enabling the services in the redhat firewall and then just disabling the firewall. Still no dice. I can see the via the logs on the router incoming requests to the correct external port from other people. My own requests to my external IP don't show up, but I am not too worried about that.

My question is what could possibly be interfering with the packets coming in and not getting to my firewall. What are some of the magic linux network commands I could use to find out where the address is getting dropped. Ideally I would like to get this working with the firewall up, another layer of protection and all, but worried about just getting it working.

Cheers,

try running up tcpdump or tethereal (preferable) against the interface you are port forwarding to. It'll tell you if your linksys is forwarding packets and let you make an informed decision about where the problem lies.

your firewall is your router ?

Since you mention port forwardin I assume it is.

http://www.computing.net/windows2003...orum/2292.html

"You will have to set up Port Forwarding. The requests to port 80 are hitting your router and your router is not your web site - your web server is. You need to tell your router that requests on port 80 are sent to your web server. Your router most likely has a web interface that you can connect to to set up Port Forwarding. Forward port 80 to the internal ip address of your web server - 192.168.0.x or whatever your internal subnet is."

a guess what do you mean with firewall

oops just seen "redhat firewall" .its not your firewall your link sys router is the answer to your problem hopefully

My router is a firewall of sorts I guess. But I believed that the firewall that is part of fedora was my problems, but disabling it still didn't yield any results.

I will try the suggest links from angrybeaver.

Thanks

well u said redhat firewall

"tried enabling the services in the redhat firewall and then just disabling the firewall."



good luck with the links (ys)

But NATurally you follow the links


http://www.homenethelp.com/web/explain/about-NAT.asp
What If I want to host a server?
Most NAT devices allow you to create maps between the internet and your computer network - this is called port forwarding. Example: A request on port 80 from the Internet (looking for a web server on your IP address) would normally be turned away by a NAT device. A special mapping can be set up to send that request from the internet to a specific computer on your network. One of your LAN computers could host a web server on the Internet, and another computer (or the same one) could host an FTP server because the two services work on different ports. Only a few special programs on the internet will not work using this port forwarding system.

Seriously try the Network Adress Translation. If that doesn't work then go for the fancy tools imo.

Occam's Razor

PRINCIPLE OF PARSIMONY OR PRINCIPLE OF SIMPLICITY
a criterion for deciding among scientific theories or explanations. One should always choose the simplest explanation of a phenomenon, the one that requires the fewest leaps of logic.

Ok bye have some qmail-scanner patches to do

Ok forwarding an high numbered port on the router side, to port 80 on the linux box (where httpd is running).
Using tethereal I captured the following:

Capturing on eth0
0.000000 192.168.1.1 -> 192.168.1.100 TCP 2913 > http [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
0.002655 192.168.1.100 -> 192.168.1.1 TCP http > 2913 [RST, ACK] Seq=0 Ack=0 Win=0 Len=0
0.473825 192.168.1.1 -> 192.168.1.100 TCP 2913 > http [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
0.473966 192.168.1.100 -> 192.168.1.1 TCP http > 2913 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0
0.975467 192.168.1.1 -> 192.168.1.100 TCP 2913 > http [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
0.975605 192.168.1.100 -> 192.168.1.1 TCP http > 2913 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0
2.088163 192.168.1.1 -> 192.168.1.255 SNMP TRAP-V1 SNMPv2-SMI::enterprises.3955.1.1.0
7 packets captured


So the request packets are getting through the router and to my linux box. The port (2913) is not the external port, I guess the router is switching it to a different port on the internal side (192.168.1.1). However I don't see the webpage in my browser. Do I have to tell apache it is behind a router and to behave differently?

internet <-> linksys router <-> internal network (192.168.1.xxx)

Seriously mate you have to tell your router to route incoming traffic on 80 to your internal linux IP on port 80

http://www.google.com/search?hl=en&i...=Google+Search

I don't want port 80 on the external side, that would open me up to any port scanning on port 80. I want a different port to go to port 80. This should be possible, even when I switch it to port 80 on the router forwarding to port 80 on the linux box I get the same issues.

So at least you wrote now that you did that. Wasn't quite clear from the above.

Have you tried DMZ just to check, that incoming 80 (or 8080 etc) is possible ? If that's not possible, ef Occam and good luck

Redirecting Around A Port 80 Block

Many Internet Service Providers (ISPs) choose to block traffic bound for their customers' port 80, the port used for web traffic. This is usually done for security or policy reasons, and makes it difficult (but not impossible) to run a web server.

This can be solved using either our MyWebHop (with Custom DNS) or WebHop (with Dynamic DNS or Static DNS) by creating a redirection to a URL which includes a non-standard port number.

http://www.dyndns.org/support/kb/portredirect.html

Maybe you have a nasty ISP ?

Which port does your web server use then? You will need to add :<port number> to your web brower address line to access the server then, and have this port forwarded to the server computer (192.168.1.100).

interesting dump. your linux box is sending back RST packets to the client (RFC 793) - are you sure you don't have any filters running? it could be tcpwrappers (/etc/hosts.deny or /etc/hosts.allow), a stray ipchains, iptables or ipf rule, or an ACL perhaps in your apache config ...

you could always put your linksys into bridging mode and run it that way - take port forwarding/NAT etc out of the equation. may not be practical depending on your setup.

both hosts.deny and hosts.allow are empty. ip tables is empty, it doesn't look like I have ipchains installed.

ipf doesn't seem to be supported by the newer kernels, and it doesn't look like its installed.
As for ACL I haven't changed anything from the default, I did not find any .htaccess files, or .acl files on my system.

As far as using port 80 on the router side, it produces the same result posted above as using a different external port and forwarding it to port 80 on the linux box (accessing via http://externalip:externalport )

I tried using the DMZ option, and got the same RST result.
8.557715 192.168.1.1 -> 192.168.1.100 TCP 4746 > http [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
8.557935 192.168.1.100 -> 192.168.1.1 TCP http > 4746 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0

I could try rebooting and seeing if it fixes anything, something is seriously messed up. What's strange is I often run bittorrent, which also use ports forwarded from the router, and it works fine, I am going to double check those results again though.

Any further ideas?