- Subject: Re: IPTables
- From: "Ethy H. Brito" <ethy.brito@xxxxxxxxxxxx>
- Date: Wed, 11 Apr 2012 10:06:40 -0300
- In-reply-to: <e89a8ff2474fc99c5604bd608a88@google.com>
- Organization: InterNexo Ltda.
On Wed, 11 Apr 2012 05:30:49 +0000
BigAl.NZ@xxxxxxxxx wrote:
> As an update. When I try to connect I ran tcptrack on wlan0 and it
> shows the incoming connection with:
>
> Client Server State Idle Speed
> 118.92.xx.55:58674 192.168.1.71:80 RESET 1s 0 b/s
> 118.92.xx.55:58673 192.168.1.71:80 RESET 1s 0 b/s
> 118.92.xx.55:58676 192.168.1.71:80 RESET 1s 0 b/s
>
> Does this seem normal?
it does. But it seems something before Ubuntu is not right.
If I got it right, you should see something like this:
118.92.xx.55:58674 192.168.1.71:5555 ...(forward to port 5555 and not 80.
this way the iptables DNAT rule won't match)
I think your redirections at the router (192.168.1.254) is not doing what
you intended it to do.
> If I monitor eth0 I see no traffic, so the fault must be in my rule
> somewhere?
You see no traffic because 192.168.1.7 thought it was a connection to itself
at port 80 and RESETed it.
Ethy
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Netfilter Development]
[Linux Kernel Networking Development]
[Linux Networking Development]
[Linux Kernel Development]
[Linux Resources]
[LARTC]
[Bugtraq]
[Consulting]
[Free Internet Dating]
[Yosemite Forum]
[Photo]