| |||||||||||||
|
| |||||||||||||
Better kernel supportBetter kernel supportPosted Jul 13, 2010 8:40 UTC (Tue) by smurf (subscriber, #17840)In reply to: Better kernel support by nas Parent article: The road forward for systemd Perhaps a user space program could register its interest in a certain events (e.g. connection to a certain port) and take appropriate actions (e.g. start a daemon). That's exactly what systemd does right now. The kernel doesn't provide a mechanism to queue TCP SYN packets until the corresponding port gets opened. I don't think there should be. Either some process is listening on a port (you send a SYN+ACK back), or not (you send a REJ back).
(Log in to post comments)
Better kernel support Posted Jul 13, 2010 9:01 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
hmm, diald was caching network packets while it opened a network connection a decade ago. why can't the same mechanism be used for the inbound packets?
no, I don't remember the mechanism, but in the dial-up days I used diald extensively
Better kernel support Posted Jul 13, 2010 9:09 UTC (Tue) by paulj (subscriber, #341) [Link]
Yes it did. IIRC it used an ethertap device to forward the packets up to itself in user-space. Then when the line was up it would repoint the default route to the ppp (or whichever) device and send out the packets. Very neat.
|
|
||||||||||||