Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+dynamic\s+IP\s+support\s+for\s+2\.4\.0\s+$SIOCKILLADDR$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+dynamic\s+IP\s+support\s+for\s+2\.4\.0\s+$SIOCKILLADDR$\s*$/: 18 ]

Total 18 documents matching your query.

1. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: Mark Cooke <mpc@xxxxxxxxxxxxxxxxxx>; Date: Sun, 4 Feb 2001 22:21:39 +0000 (GMT); ciped is great for this. I use it to tunnel ssh from my home dialup to work. Very stable, and with cipe's shared keys, there's nothing too taxing about setting it up. I just have a call to /etc/init.; /archives/netdev/2001-02/msg00020.html (8,765 bytes)
2. [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: ichael@xxxxxxxxxxxxxxx>; Date: 27 Jan 2001 22:54:51 +0000; i; /archives/netdev/2001-01/msg00319.html (10,117 bytes)
3. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: on <andrewm@xxxxxxxxxx>; Date: Sun, 28 Jan 2001 21:45:02 -0500 (EST); a; /archives/netdev/2001-01/msg00327.html (9,049 bytes)
4. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: " <acahalan@xxxxxxxxxx>; Date: Mon, 29 Jan 2001 13:59:05 +0100; .; /archives/netdev/2001-01/msg00328.html (10,335 bytes)
5. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: xxxxxxxxxxxxxxxxxxxxxx>; Date: Mon, 29 Jan 2001 19:31:36 +0100; r; /archives/netdev/2001-01/msg00334.html (9,960 bytes)
6. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: Jones <raj@xxxxxxxxxx>; Date: Mon, 29 Jan 2001 22:08:40 +0100; l; /archives/netdev/2001-01/msg00336.html (9,555 bytes)
7. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: ler" <davem@xxxxxxxxxx>; Date: 30 Jan 2001 00:47:04 +0000; x; /archives/netdev/2001-01/msg00338.html (9,601 bytes)
8. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: emlin" <vii@xxxxxxxxxx>; Date: 30 Jan 2001 00:43:32 +0000; i; /archives/netdev/2001-01/msg00339.html (10,421 bytes)
9. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: ler" <davem@xxxxxxxxxx>; Date: Wed, 31 Jan 2001 21:56:03 -0800; y; /archives/netdev/2001-01/msg00388.html (9,382 bytes)
10. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: Mark Cooke <mpc@xxxxxxxxxxxxxxxxxx>; Date: Sun, 4 Feb 2001 22:21:39 +0000 (GMT); ciped is great for this. I use it to tunnel ssh from my home dialup to work. Very stable, and with cipe's shared keys, there's nothing too taxing about setting it up. I just have a call to /etc/init.; /archives/netdev/2001-02/msg00262.html (8,837 bytes)
11. [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: "John Fremlin" <vii@xxxxxxxxxx>; Date: 27 Jan 2001 22:54:51 +0000; When the IP address of an interface changes, TCP connections with the old source address are useless. Applications are not notified of this and time out ordinarily, just as if nothing had happened. T; /archives/netdev/2001-01/msg00708.html (10,132 bytes)
12. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: "Albert D. Cahalan" <acahalan@xxxxxxxxxx>; Date: Sun, 28 Jan 2001 21:45:02 -0500 (EST); ... I get the same IP about 2/3 of the time, so it is pretty important to avoid killing connections until after the new IP is known.; /archives/netdev/2001-01/msg00716.html (9,071 bytes)
13. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: Andi Kleen <ak@xxxxxx>; Date: Mon, 29 Jan 2001 13:59:05 +0100; I prefer it when the IP is killed as soon as possible so that I can see when the connection is lost (ssh sessions get killed etc.) Another reason for killing as soon as possible is the last-ack probl; /archives/netdev/2001-01/msg00717.html (10,469 bytes)
14. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: Jamie Lokier <ln@xxxxxxxxxxxxxxxxxxxxxxxx>; Date: Mon, 29 Jan 2001 19:31:36 +0100; I like it when I get the same IP back and can continue an ssh session. My line drops regularly in mid session. Unfortunately getting the same IP is rare now, so I've been toying with running a PPP tu; /archives/netdev/2001-01/msg00723.html (10,110 bytes)
15. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: Andi Kleen <ak@xxxxxxx>; Date: Mon, 29 Jan 2001 22:08:40 +0100; Just do not set IFF_DYNAMIC on the tunnel interface then, that is why it is a flag and not hardcoded. -Andi; /archives/netdev/2001-01/msg00725.html (9,735 bytes)
16. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: "John Fremlin" <vii@xxxxxxxxxx>; Date: 30 Jan 2001 00:47:04 +0000; [...] No connections at all will be destroyed by my patch unless you enable the new killoldaddr pppd option. -- http://www.penguinpowered.com/~vii; /archives/netdev/2001-01/msg00727.html (9,729 bytes)
17. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: "John Fremlin" <vii@xxxxxxxxxx>; Date: 30 Jan 2001 00:43:32 +0000; I'll try to explain again. If you have an existing (e.g. ssh) connection to a host across the interface, and the interface comes down then pppd _will not bring it up again_ until you try to start a n; /archives/netdev/2001-01/msg00728.html (10,470 bytes)
18. Re: [PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR) (score: 1): Author: Ralf Baechle <ralf@xxxxxxxxxxx>; Date: Wed, 31 Jan 2001 21:56:03 -0800; Pretty much dependant of the type of equipment and the configuration used at the ISP's servers. I use two ISPs when I'm back in Germany of which the one always and the other one never gives me the sa; /archives/netdev/2001-01/msg00777.html (9,562 bytes)

Current List: 1 - 18
Page: [1]