From: "Steen Suder, privat" <steen@suder.dk>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems with ICQ etc. on nano-setup
Date: Mon, 15 Dec 2003 02:57:53 +0000 [thread overview]
Message-ID: <marc-lartc-107145755020004@msgid-missing> (raw)
I administer a nano-setup on a dorm-network with a couple of hundred
active users.
The setup uses 2 x 2 2Mb/s DSLs, meaning two DSLs from each of two
different ISPs.
It works fine except for some minor glitches:
https-sites often kicks users. This was solved by tying outbound https
to a single DSL. Not the best solution but it works so far that users
dont kicked from the sites anymore. Now they can put credits on the
SIM-cards again ;-)
ICQ-logins is a pain as it often takes several attempts (4-8 usually) to
get connected to ICQ.
I've tested with the latest micq from a host on the LAN and it says
"Connection refused (111)". The same behaviour goes for all other
(reported) clients of all kinds on the LAN. On the same time ICQ works
fine from othe locations.
Now I'm wondering and it is somewhat ICQspecific: when one connects to
ICQ one gets redirected to another server. Perhaps this redirect causes
the connection to take another DSL on its way onto the Internet... and
maybe the new sourceaddress causes the ICQ-server to drop the connection
attempt due to difference between the initial sourceaddress and the
"second" sourceaddress.
Now, the simple way to solve this issue is to bind anything even
remotely related to ICQtraffic to one single DSL, but I'd really like to
solve this "The Proper Way".
Suggestion:
Can one "bind" traffic from one LAN-user to the same DSL, effective in
lets say 10 minutes from the initial connection?
Can some magic with conntrack be put to use?
1. How can I find out what is causing this "glitch"?
This would be rather important since it could be the cause of other
"irregularities" in the operation.
2. How is this solved?
A snippet from the /etc/sysctl.conf:
net.ipv4.route.max_size2768
net.ipv4.route.gc_min_interval=5
net.ipv4.route.gc_interval00
It's a 2.4.23-box and it does SNAT on all four DSLs.
It's pretty open from the inside towards the Internet.
--
Mvh. / Best regards,
Steen Suder <http://www.suder.dk/>
ICQ UIN 4133803
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-12-15 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 2:57 Steen Suder, privat [this message]
2003-12-15 6:25 ` [LARTC] Problems with ICQ etc. on nano-setup Ben Efros
2003-12-15 10:41 ` Steen Suder, privat
2003-12-15 12:38 ` c0g
2003-12-15 13:03 ` Steen Suder, privat
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-107145755020004@msgid-missing \
--to=steen@suder.dk \
--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.