Re: iptables fubared?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I tried this with tcpdump running on the server. It surprised me when I saw tcpdump respond. Firefox still says "cannot connect" from an external workstation, but my server is seeing something at least.

I won't bore you with all of it, but here's the first bit:

$ sudo  tcpdump -i eth0 -n "port 80"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
21:54:16.482166 IP 99.92.208.198.52890 > 10.211.163.215.http: Flags [S], seq 2014763367, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0 21:54:16.482251 IP 10.211.163.215.http > 99.92.208.198.52890: Flags [R.], seq 0, ack 2014763368, win 0, length 0 21:54:16.731133 IP 99.92.208.198.52891 > 10.211.163.215.http: Flags [S], seq 1148493083, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0 21:54:16.731183 IP 10.211.163.215.http > 99.92.208.198.52891: Flags [R.], seq 0, ack 1148493084, win 0, length 0 21:54:17.080885 IP 99.92.208.198.52890 > 10.211.163.215.http: Flags [S], seq 2014763367, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
....{{ sinpage }}....
^C
36 packets captured
36 packets received by filter
0 packets dropped by kernel

The server appears to be trying to give a response. (99.92.208.198 is my workstation external IP address). It's like FF can't get the response. Hmm.



On 10/4/2012 1:38 PM, NOSpaze wrote:
On Thu, 2012-10-04 at 12:45 -0700, Mark Space wrote:
Hi all, I'm having a bit of trouble setting up a new web server. The
last time I set up up it went smoothly, but for some reason I can't
connect to the HTTP port on this one.
Any clues what I'm missing?
You are trying to solve a problem with many variables simultaneously (I
can't even understand the purpose of your iptables rules).

Try solving one problem at the time. First: routing. If you can ping
effectively from the outside, routing is ok. Second: tcp ports. Check if
you can find the opened ports. Try debugging the problem with tcpdump.
nmap can help you check for opened ports.

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux