> Yeah. But I'm stuck with a NAT (which isn't mine, btw) which uses 2.1.xxx-2.2.x > (according to nmap). Which had a default of 15 *minutes* (as I read in a HOWTO > somewhere). I'm trying to convince the sysadmin to raise it to two hours, but I > bet it'll be hard. ipchains -S timeoutval 0 0 is the only way to do this. Igmar - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- TCP keepalive seems to send to only one port Cesar Eduardo Barros
- RE: TCP keepalive seems to send to only one port David Schwartz
- Re: TCP keepalive seems to send to only one ... Cesar Eduardo Barros
- Re: TCP keepalive seems to send to only ... James Morris
- Re: TCP keepalive seems to send to o... Cesar Eduardo Barros
- Re: TCP keepalive seems to send... Igmar Palsenberg
- Re: TCP keepalive seems to ... Cesar Eduardo Barros
- RE: TCP keepalive seems to send to only ... David Schwartz
- Re: TCP keepalive seems to send to o... Cesar Eduardo Barros
- RE: TCP keepalive seems to send... David Schwartz
- Re: TCP keepalive seems to send to only one port Andi Kleen
- Re: TCP keepalive seems to send to only one ... Cesar Eduardo Barros
- Re: TCP keepalive seems to send to only one port Bernd Eckenfels