> > But the problem is when the link goes down for some reason, there are some
> > stale network sockets lying around in some (CLOSING) state. How can I tell
> > the kernel to kill these sockets WHEN the interface hangs up? They way it is
> > right now, the stale sockets makes the interface redial almost immediately
> > after it has hanged up.
>
> The quick and easy(ish) solution is to get
> the 2.0.34pre4 patches from ftp.uk.linux.org
> and activate the RST-provoking mode documented in
> /usr/src/linux/Documentation/networking/ip_dynaddr.txt of
> that version.
Ok, I'll try this later this evening.
>
> If you do this you will still get one redial, but not
> several like you are getting now. If you want to stop
> that one redial, you can start getting clever with ipfwadm
> commands in /etc/ppp/ip-down and ip-up.
Somebody suggested that I should only "open" the interface on UDP (DNS) and
TCP SYN. Anybody know if this is right, and if so, how do I set up the
_correct_ rules? Examples are more than welcome... (the interface is ippp0).
TIA
-- Robin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Robin Smidsrød | Privat: 33329383 | Web: http://www.smidsrod.no
Ekelyvn. 11 | Mobil : 91593393 | E-Mail: robin@smidsrod.no
N-3150 TOLVSRØD | Jobb : 33301440 | Fax: 33324622 UIN: 1682773
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu