From: Steffen Moser <moser@egu.schule.ulm.de>
To: linux-kernel@vger.kernel.org
Subject: "ip_dynaddr" broken in 2.4.0-test10
Date: Mon, 06 Nov 2000 06:32:41 +0100 [thread overview]
Message-ID: <3A064279.30960692@egu.schule.ulm.de> (raw)
Hello,
I have configured, compiled and installed "linux-2.4.0-test10" on my
SuSE Linux 6.3 machine. After doing some necessary updates the system
works quite fine now. But there is one thing which makes still some
problems: "ip_dynaddr" seems not to work anymore.
I use an ISDN connection (dial on demand) to my ISP (that assigns me a
dynamic IP address when dialling up), so I should make use of
"ip_dynaddr" to prevent the first packet from being lost. Running
"linux-2.2.17" (or any other "2.2.X") this worked without any problems:
as soon as the connection is established the source address of the first
packet is shifted to the officially assigned address.
But this seems not to work with "linux-2.4.0-test10": I don't get
response to a packet which was sent before the connection was
established, i.e. if I try -for example- to establish an
"ssh"-connection to a machine when I am "off-line", my machine starts to
dial up, but the "ssh"-connection times out, so I have to interrupt
"ssh" and start it again after the ISDN connection is established,
because the first packet always gets lost.
The "ip_dynaddr" is activated:
steffen@pc01:~ > cat /proc/sys/net/ipv4/ip_dynaddr
1
steffen@pc01:~ >
Does anybody have the same problem? Is it a bug of "2.4.0-test10" or is
it the result of missing updates of userspace programmes?
Regards,
Steffen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-06 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 5:32 Steffen Moser [this message]
2000-11-06 5:22 ` "ip_dynaddr" broken in 2.4.0-test10 David S. Miller
2000-11-06 6:09 ` Steffen Moser
2000-11-06 18:39 ` Henner Eisen
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=3A064279.30960692@egu.schule.ulm.de \
--to=moser@egu.schule.ulm.de \
--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