All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: alucard@kanux.com
Cc: netfilter@lists.netfilter.org
Subject: Re: forwarding
Date: Tue, 18 May 2004 11:53:08 -0400	[thread overview]
Message-ID: <1084895498.7289.7.camel@localhost> (raw)
In-Reply-To: <34103.200.44.170.105.1084893176.squirrel@200.44.170.105>

On Tue, 2004-05-18 at 11:12, alucard@kanux.com wrote:
> > Although it probably did, are you sure nmap scanned port 8080? How about
> > nmap -sT -p 8080 10.73.219.156
> >
> > I would then trace both the wire and the iptables rules to find out
> > where it is breaking - John
> 
> Yes, it filters now but now it seems that the problem is in the 2nd server
> because I try to telnet to server 1's 8080 port and I get no response. Is
> it any missconfiguration on the router? take a look at this:
> ----
> root@mail:~# nmap -sT -p 8080 10.73.219.156
> 
> Starting nmap 3.48 ( http://www.insecure.org/nmap/ ) at 2004-05-18 11:06 VET
> Interesting ports on mail.aeropostal.com.ve (10.73.219.156):
> PORT     STATE    SERVICE
> 8080/tcp filtered http-proxy
> ----
> 
> the webserver in server 2 is working perfectly but im not able to reach it
> from server one, look at this in server 2, maybe im doing something wrong
> 
> [root@linserv root]# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 192.168.0.0     *               255.255.255.0   U     0      0        0 eth1
> 10.73.216.0     *               255.255.252.0   U     0      0        0 eth0
> 169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
> 127.0.0.0       *               255.0.0.0       U     0      0        0 lo
> default         192.168.0.1     0.0.0.0         UG    0      0        0 eth1
<snip>
At first glance, the routing looks correct but I hope you are not trying
to access the web server from the Linux box.  You will have more
accurate results if you try to access through it.
If you try to telnet from the Linux box, you may find it uses a source
address of 10.73.219.156. The web server will then try to respond out
interface eth0.  I believe there is an option to override the source
port of telnet - -b I think.  You will also need to ensure that nothing
is interfering in the INPUT and OUTPUT chains.  I would suggest testing
through the Linux Box rather than from it - John
-- 
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net 



  reply	other threads:[~2004-05-18 15:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 14:22 forwarding alucard
2004-05-18 14:39 ` forwarding John A. Sullivan III
2004-05-18 14:49   ` forwarding alucard
2004-05-18 14:51     ` forwarding John A. Sullivan III
2004-05-18 14:56     ` forwarding Antony Stone
2004-05-18 14:57   ` forwarding alucard
2004-05-18 14:58     ` forwarding John A. Sullivan III
2004-05-18 15:12       ` forwarding alucard
2004-05-18 15:53         ` John A. Sullivan III [this message]
2004-05-18 16:38           ` forwarding alucard
2004-05-18 17:02             ` forwarding John A. Sullivan III
2004-05-18 18:21               ` forwarding alucard
2004-05-18 18:28                 ` forwarding Antony Stone
2004-05-18 18:42                   ` forwarding alucard
2004-05-18 19:22                 ` forwarding John A. Sullivan III
2004-05-18 21:33                 ` forwarding Antony Stone
2004-05-19  4:56                   ` forwarding Juan Hernandez
2004-05-18 15:09     ` forwarding Antony Stone
2004-05-18 15:40       ` forwarding alucard
2004-05-18 15:53         ` forwarding Antony Stone
2004-05-18 14:44 ` forwarding Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2005-03-26 17:48 forwarding amir_sarbazi
2004-05-18 20:48 forwarding Daniel Chemko
2004-05-18 21:15 ` forwarding John A. Sullivan III
2004-05-18 20:33 forwarding Daniel Chemko
2004-05-18 18:23 forwarding Daniel Chemko
2004-05-18 18:42 ` forwarding Antony Stone
2004-05-18 18:50 ` forwarding alucard
2004-05-18 19:15 ` forwarding John A. Sullivan III
2004-05-18 18:04 forwarding Daniel Chemko
2004-05-18 17:04 forwarding CPD - David Cardeñosa Rubio
2004-05-18 15:33 forwarding CPD - David Cardeñosa Rubio
2004-05-18 15:47 ` forwarding John A. Sullivan III
2004-05-18 15:51 ` forwarding Antony Stone
2002-07-08  3:25 forwarding Tim
2002-07-08  0:30 ` forwarding Antony Stone
     [not found]   ` <003801c22632$521c93a0$1606d6d1@nebuchadnezza>
2002-07-08  0:53     ` forwarding Antony Stone
2002-07-08  4:03       ` forwarding Tim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1084895498.7289.7.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=alucard@kanux.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.