Firewall rejecting traffic on port 80 or 8080, but s/b allowed
I have successfully configured the firewall (using YAST of course) on SLES8 AND SLES9 for a year now with now problems. I am testing a new web application server running Tomcat and cannot get it to consistently accept traffic on either port 8080 or port 80 (HTTP traffic, that is). I have checked that http traffic (port 80) and port 8080 should be allowed. Here are the messages I am seeing in the log when I try to connect. Feb 16 16:39:23 kingfish kernel: SFW2-INext-ACC-TCP IN=eth2 OUT= MAC=00:02:b3:f0:87:f7:00:10:0b:4e:58:01:08:00 SRC=130.13.0.4 DST=140.99.50.63 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=5523 DF PROTO=TCP SPT=2049 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 16 16:39:23 kingfish kernel: SFW2-INext-ACC-TCP IN=eth2 OUT= MAC=00:02:b3:f0:87:f7:00:10:0b:4e:58:01:08:00 SRC=130.13.0.4 DST=140.99.50.63 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=5528 DF PROTO=TCP SPT=2049 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) Feb 16 16:39:24 kingfish kernel: SFW2-INext-ACC-TCP IN=eth2 OUT= MAC=00:02:b3:f0:87:f7:00:10:0b:4e:58:01:08:00 SRC=130.13.0.4 DST=140.99.50.63 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=5531 DF PROTO=TCP SPT=2049 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402) My web browser is coming from 130.13.0.4 (a Linksys gateway/router) and my server is at 140.99.50.63. Any ideas on why this is? Thank you - Richard
Richard Mixon (qwest) wrote:
I have successfully configured the firewall (using YAST of course) on SLES8 AND SLES9 for a year now with now problems.
I am testing a new web application server running Tomcat and cannot get it to consistently accept traffic on either port 8080 or port 80 (HTTP traffic, that is).
I have checked that http traffic (port 80) and port 8080 should be allowed.
Here are the messages I am seeing in the log when I try to connect. Feb 16 16:39:23 kingfish kernel: SFW2-INext-ACC-TCP IN=eth2 OUT=
This is SuSEfirewall2 Incoming from external interface accept tcp protocol
MAC=00:02:b3:f0:87:f7:00:10:0b:4e:58:01:08:00 SRC=130.13.0.4 DST=140.99.50.63 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=5523 DF PROTO=TCP SPT=2049 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402)
Destination port was 80. It was accepted. Maybe the problem is elsewhere.
My web browser is coming from 130.13.0.4 (a Linksys gateway/router) and my server is at 140.99.50.63.
Any ideas on why this is? Why this is what? Accepting? You said you configured it this way. :-\ -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe/all, thanks for the help - see below. Joe Morris (NTM) wrote:
Richard Mixon (qwest) wrote:
I have successfully configured the firewall (using YAST of course) on SLES8 AND SLES9 for a year now with now problems.
I am testing a new web application server running Tomcat and cannot get it to consistently accept traffic on either port 8080 or port 80 (HTTP traffic, that is).
I have checked that http traffic (port 80) and port 8080 should be allowed.
Here are the messages I am seeing in the log when I try to connect. Feb 16 16:39:23 kingfish kernel: SFW2-INext-ACC-TCP IN=eth2 OUT=
This is SuSEfirewall2 Incoming from external interface accept tcp protocol
OK, my mistake. I was tailing the log while trying to hit the web site with a browser. When I saw the browsers "connection rejected" message, these three messages appeared in the log at the same time. I assumed they were error messages - my mistake. Where are those were messages documented so I can better understand them. I had a vanilla Tomcat configuration - listening on localhost at port 8080. I've never had the problem before that I can remember. Thank you all - Richard
MAC=00:02:b3:f0:87:f7:00:10:0b:4e:58:01:08:00 SRC=130.13.0.4 DST=140.99.50.63 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=5523 DF PROTO=TCP SPT=2049 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B401010402)
Destination port was 80. It was accepted. Maybe the problem is elsewhere.
My web browser is coming from 130.13.0.4 (a Linksys gateway/router) and my server is at 140.99.50.63.
Any ideas on why this is? Why this is what? Accepting? You said you configured it this way. :-\ -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
participants (2)
-
Joe Morris (NTM) -
Richard Mixon (qwest)