From: "David" <maniacdavid@cableone.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Getting AOL IM client to work with IPTABLES and IPROUTE2 (port forwarding almost)
Date: Sun, 28 Oct 2001 13:28:53 +0000 [thread overview]
Message-ID: <marc-lartc-100427589232417@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
I'm trying to get my AOL IM'r to work consistenly with 2 cable modems. It
seems like it says it can't connect (90% of the time, 10% it works, just
pure luck) when I have both of the cable modems working together with this
iproute command
ip route default equalize nexthop via ***.***.***.*** dev eth0 nexthop via
***.***.***.*** dev eth2
iptables -A POSTROUTING -t nat -j MASQUERADE -o eth2
iptables -A POSTROUTING -t nat -j MASQUERADE -o eth0
Internet and everything else works fine with that. I need a solution whether
it be some kind of forwarding (port 5190) so that anything received comes
through 1 ethernet address. It might even have to be sent out the same
ethernet address but I'm thinking either one would work if there is someway
to put a return address on the packet or something. I know AOL im'r works
100% when the linux box is routing just through 1 cable modem.
Thanks!
David
[-- Attachment #2: Type: text/html, Size: 1653 bytes --]
next reply other threads:[~2001-10-28 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 13:28 David [this message]
2001-10-28 14:02 ` [LARTC] Getting AOL IM client to work with IPTABLES and IPROUTE2 (port forwarding almost) Christoph Simon
2001-10-28 14:55 ` [LARTC] Getting AOL IM client to work with IPTABLES and IPROUTE2 Julian Anastasov
2001-10-28 15:53 ` [LARTC] Getting AOL IM client to work with IPTABLES and IPROUTE2 (port forwarding almost) Christoph Simon
2001-10-28 17:23 ` [LARTC] Getting AOL IM client to work with IPTABLES and IPROUTE2 Julian Anastasov
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-100427589232417@msgid-missing \
--to=maniacdavid@cableone.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 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.