Linux-kernel mailing list archive 2000-23,: ip_dynaddr broken in 2.4.0-test1 ?

# ip_dynaddr broken in 2.4.0-test1 ?

Christian Nautze (christian@nautze.de)
Sun, 04 Jun 2000 22:06:36 +0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: David Lang: "Re: Hot pluggable CPUs ( was Linux 2.5 / 2.6 TODO (preliminary) )"
- Previous message: Garst R. Reese: "oops [CardBus Watcher]"
- Next in thread: Malware: "Re: ip_dynaddr broken in 2.4.0-test1 ?"
- Reply: Malware: "Re: ip_dynaddr broken in 2.4.0-test1 ?"
- Reply: Christian Nautze: "Re: ip_dynaddr broken in 2.4.0-test1 ?"
- Reply: Malware: "Re: ip_dynaddr broken in 2.4.0-test1 ?"

Hi,

i have used /proc/sys/net/ipv4/ip_dynaddr in the 2.2.x
series for my isdn auto dialup, but with the 2.4.0-test1 kernel
it didn't work anymore. If i ping a maschine when i am not
connected the resulting packets are not rewritten with the
new ip that i got from my isp. I have inserted some printk in
tcp_v4_rebuild_header in /usr/src/linux/net/ipv4/tcp_ip.c
and it seems that this function is not called after the connection
is established, but somehow later.
cat /proc/../ip_dynaddr outputs 2.
Is this a bug or changed something from 2.2.x->2.[34] ?

Best regards

Christian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: David Lang: "Re: Hot pluggable CPUs ( was Linux 2.5 / 2.6 TODO (preliminary) )"
- Previous message: Garst R. Reese: "oops [CardBus Watcher]"
- Next in thread: Malware: "Re: ip_dynaddr broken in 2.4.0-test1 ?"
- Reply: Malware: "Re: ip_dynaddr broken in 2.4.0-test1 ?"
- Reply: Christian Nautze: "Re: ip_dynaddr broken in 2.4.0-test1 ?"
- Reply: Malware: "Re: ip_dynaddr broken in 2.4.0-test1 ?"