From: x@abyss.4t2.com (Thomas Weber)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.6pre iptables masquerading seems to kill eth0
Date: 21 Jun 2001 22:51:33 +0200 [thread overview]
Message-ID: <9gtmol$9ve$1@pandemonium.abyss.4t2.com> (raw)
In-Reply-To: <3B31A652.85D2E597@idb.hist.no>
I'm on 2.4.6pre3 + freeswan/ipsec on my gateway now for 5 days.
It's an old 486/66 32MB with several isdn links, a dsl uplink (with
iptables masquerading) behind a ne2k clone and a 3c509 to the inside network.
no problems at all with the interfaces (all compiled as modules).
Tom
In article <3B31A652.85D2E597@idb.hist.no>,
Helge Hafting <helgehaf@idb.hist.no> wrote:
>I have a home network with two machines connected with
>3c905B cards. The main machine also has a isdn dialup connection.
>
>Networking works well except if I let the main machine masquerade
>so the other can use the internet too. I use iptables for this.
>It works for a day or so, then eth0 goes silent on the main machine.
>(Rebooting it shows that the other one was fine all the time.)
>
>The symptoms is that there is no contact between the two machines.
>No ping or anything. "ifconfig" shows the interface is up
>with the correct ip address, but all packets just disappear.
>There are no error messages except from programs that time out.
>
>Bringing the interface down and up
>again with ifconfig does not help. It is compiled into the
>kernel, so I can't try module reloading.
>
>Is this some sort of known problem? Or is there something
>I could do to find out more? I couldn't
>find anything in the logfiles.
next prev parent reply other threads:[~2001-06-21 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 7:46 2.4.6pre iptables masquerading seems to kill eth0 Helge Hafting
2001-06-21 20:51 ` Thomas Weber [this message]
2001-06-22 7:20 ` Helge Hafting
2001-06-25 21:13 ` Thomas Weber
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='9gtmol$9ve$1@pandemonium.abyss.4t2.com' \
--to=x@abyss.4t2.com \
--cc=linux-kernel@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