From: Andrius Adomaitis <andrius@skynet.lt>
To: lartc@vger.kernel.org
Subject: [LARTC] Strange conectivity problem on shaping box
Date: Tue, 10 Dec 2002 13:55:40 +0000 [thread overview]
Message-ID: <marc-lartc-103952860724893@msgid-missing> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
first of all I would like to appoligise if this is not right topic on this
mailling list...
Few days ago I installed new shaping/nat box with latest 2.4.20 kernel,
iproute-20010824, and iptables 1.2.7a, which was built from netfilter cvs
together with all extra netfilter patches.
Since I had nice working shaping/nat box, I just transferred all iptables and
tc setup scripts to new box, but got unexpected strange results after start.
Problem is, that I am unable to retrieve big files - e.g. telnet to remote 22
port _shows_ ssh banner, but ssh'ing to that host fails, telnet to some
remote 80 port _shows_ http proto error, but MsIE timeouts, retrieving
http://ftp.lt.kernel.org/pub/linux/kernel/v2.4/linux-2.4.20.tar.bz2.sign is
ok, but whole kernel is NOT. Also all tested hosts responds to ping....
ECN is not compiled in.
NAT is working ok, since i have communication with outside world...
CBQ and sfq shaping is done on vlan interfaces, pakets are being marked, no
other (TOS, etc) mangling is being done.
Any ideas what could be wrong? MTU problem, etc?
Please help, because I'm just lost....
Thank You.
Andrew.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE99fJkN8/5pHh2B0YRAkR7AJ4yeuKqzbRLaZbVc+ZUkHfpeBv2wACfdizT
6x9xEy3LShVvseKlr6m7rYY=
=7SBj
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-12-10 13:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-lartc-103952860724893@msgid-missing \
--to=andrius@skynet.lt \
--cc=lartc@vger.kernel.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.