From: ro0ot <ro0ot@phreaker.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] MSN keeps disconnecting with load balancing
Date: Sun, 13 Nov 2005 16:36:27 +0000 [thread overview]
Message-ID: <43776B8B.7010802@phreaker.net> (raw)
In-Reply-To: <4376BF51.7040300@phreaker.net>
Is it possible to increase the cached route timeout? Yes, I am using
SNAT, will MASQUERADE help?
Ryan Castellucci wrote:
>This problem is caused by the cached route to MSN expiring, and the
>kernel trying to route the existing connection over the other internet
>connection. If you're doing SNAT, this will result in the source IP
>address changing, and MSN will reset the connection.
>
>On 11/12/05, Corey Hickey <bugfood-ml@fatooh.org> wrote:
>
>
>>ro0ot wrote:
>>
>>
>>>Hi,
>>>
>>>I have the my gateway with load balancing traffic going out over two
>>>providers. Web browsing is fine...working great.
>>>
>>>But, my clients (office staff) complains that MSN keeps disconnecting
>>>(in 5 mins). Why?
>>>
>>>
>>Do you mean MSN instant messenger? I've never used it, but I can give
>>you a few generic steps to take when you want to figure out what's going
>>wrong with a connection. Are you familiar with tcpdump and/or ethereal?
>>
>>1. Go to the computer of a client who is complaining about disconnection.
>>
>>2. ssh into your gateway and run:
>># tcpdump -i eth0 host 123.123.123.123 and port not ssh
>>Change "eth0" to the inside interface and "123.123.123.123" to the IP
>>address of your client.
>>
>>3. See if tcpdump is catching lots and lots of packets. If it is, either
>>stop programs on your clients machine that access the Internet or use
>>more filters (like "and port not imaps").
>>
>>4. Once you're not catching lots of extraneous packets, kill tcpdump and
>>run:
>># tcpdump -s 1500 -w log -i eth0 host 123.123.123.123 and port not ssh
>>Include any other filters you have to use.
>>
>>5. Have your client start up their program, and then sit there and wait.
>>Don't do anything else that would send packets through the gateway; you
>>don't want to clutter up the log.
>>
>>6. See if the problem manifests. Most likely it won't, because that's
>>just the way things are :) , but if it does you'll have a log. Kill
>>tcpdump and examine the file with:
>># tcpdump -r log
>>If you want more verbosity, use "-v", "-vv", or "-vvv". Or, if you want
>>to use a gui, copy the log file to some machine with X11 and use:
>># ethereal -r log
>>
>>
>>-Corey
>>_______________________________________________
>>LARTC mailing list
>>LARTC@mailman.ds9a.nl
>>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>>
>>
>>
>
>
>--
>Ryan Castellucci http://ryanc.org/
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-11-13 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 4:21 [LARTC] MSN keeps disconnecting with load balancing ro0ot
2005-11-13 4:39 ` Erik Elmore
2005-11-13 5:15 ` Ron Senykoff
2005-11-13 5:19 ` Corey Hickey
2005-11-13 6:25 ` Ryan Castellucci
2005-11-13 16:36 ` ro0ot [this message]
2005-11-13 16:51 ` ro0ot
2005-11-13 17:13 ` Oscar Mechanic
2005-11-14 10:41 ` Jandre Olivier
2005-11-14 17:48 ` ro0ot
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=43776B8B.7010802@phreaker.net \
--to=ro0ot@phreaker.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox