login
Header Space

 
 

Re: FairQ ALTQ for PF - Patch #2

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <kernel@...>
Date: Monday, April 7, 2008 - 2:42 pm

:I concur.  Keep state should be explicit.  Furthermore, I don't expect
:keep state not to work across reboots.  That's why I then write keep
:state flags S/SA.  Something clearly need to be untangled here.  Keep
:state should keep state as good as possible, but not reject connections.
:
:cheers
:  simon

    I figured out another reason why linux boxes couldn't connect to me.

    I wasn't running keep state on incoming traffic, only outgoing.  That
    means the keep state didn't have the initial SYN packet from an
    outside host making a connection into me.  No initial SYN, no window
    scaling info.

    My current pickup check is not quite sufficient, either.  I have to
    check that the SYN was observed in both directions.  Seeing just one
    of the SYNs may not be enough.  I'll have to re-read the window scaling
    rules.

    Max, or anyone... do you happen to remember whether window scaling
    is negotiated the same for both directions or whether each direction
    in a TCP connection can use a different scaling factor?

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: FairQ ALTQ for PF - Patch #2, Matthew Dillon, (Mon Apr 7, 2:42 pm)
Re: FairQ ALTQ for PF - Patch #2, Max Laier, (Mon Apr 7, 3:32 pm)
speck-geostationary