All of lore.kernel.org
 help / color / mirror / Atom feed
From: WP <mls100@comcast.net>
To: netfilter@lists.netfilter.org
Subject: IPTables problem perhaps related to ECN/CWR flags?
Date: Wed, 26 Jul 2006 04:45:39 -0700	[thread overview]
Message-ID: <44C755E3.7050908@comcast.net> (raw)

Greetings,

I currently setup a home network with the following topology:

Cable Modem -> Linux Computer (IPTables+NAT) -> Switch (3com 8 port 
100mbit Officeconnect) -> 4 computers.

I use Arno's IPTables Script: 
http://rocky.eld.leidenuniv.nl/iptables-firewall/arno-iptables-firewall_1.8.6c.tar.gz 
.

I run two computers running two different versions of the a server 
behind the NAT. The first version (2.0) is extremely old and runs on DOS 
6.22 and a packet driver (henceforth referred to as W2). The second 
(3.0) runs fine on Windows XP (henceforth referred to as W3). From the 
internal LAN, I can connect to both servers fine. From the outside 
though, people are only able to connect to W3 . Both listen on port 23. 
I decided to setup tcpdump and see what was going on.

I compared the packets being sent when successful (via LAN)

wireshark screenshot of tcpdump cap: 
http://s92551514.onlinehome.us/upload/LANtoW2.jpg

to the ones being ignored (via Outside)

wireshark screenshot of tcpdump cap: 
http://s92551514.onlinehome.us/upload/OUTSIDEtoW2.jpg *# note the 
connect packet is forwarded successfully, but W2 does not respond.*

...and noticed that the only difference was the ECN and CWR flags.

I did a little googling, and saw a few random posts that said some sites 
don't function with ECN enabled, and that ECN is supplied only when it 
is negotiated. So I'm thinking perhaps the outside client asks my Linux 
routing comp if it supports ECN (/proc/sys/net/ipv4/tcp_ecn is 0), Linux 
comp says yes?, packet is generated with ECN/CWR and sent to Linux, 
Linux forwards packet to W2 with those flags intact. W2, being old and 
not knowing what those flags mean, ignores the packets.

This is of course pure theory, as I have little to no knowledge of any 
of this stuff to be honest, I'm just comparing what works and what 
doesn't. So my question is this, would the CWR and ECN flags possibly 
cause W2 to act this way? If so, is there some tool I can use to strip 
those flags when forwarding packets to W2 so that they match the LAN 
packets I captured? Or is there a better solution to this whole mess?

Thanks very much,

MLS

Relevant version info etc...

Router:
Gentoo Linux 2006.0
Kernel 2.6.16
IPTables 1.3.5
Wireshark 0.99.2
TCPDump 3.9.4
LibPcap 0.9.4

W2:
MS-DOS 6.22
Intel E100B Packet Driver 11.11


             reply	other threads:[~2006-07-26 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 11:45 WP [this message]
2006-07-26 12:42 ` IPTables problem perhaps related to ECN/CWR flags? Sietse van Zanen
2006-07-26 18:12   ` WP

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=44C755E3.7050908@comcast.net \
    --to=mls100@comcast.net \
    --cc=mls1000@s92551514.onlinehome.us \
    --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.