[maemo-developers] Localhost unavailable when wi-fi offline or not connected
From: Patrik Flykt Patrik.Flykt at nokia.comDate: Thu May 3 14:04:48 EEST 2007
- Previous message: Localhost unavailable when wi-fi offline or not connected
- Next message: Localhost unavailable when wi-fi offline or not connected
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, On Wed, 2007-05-02 at 07:10 -0500, ext David Hagood wrote: > Outbound packet detected with interface down This has one additional problem: The packets sent to the dummy interface will vanish and not be re-routed to the new interface once it's up. If the packets were meant for DNS, the application most likely would end up with a "host not found" while the connection would still be connecting in the background. If the device should not have DNS packets triggering connection creation there are problems as all applications do their name resolution before they actually connect, so nobody would be able to connect. In order to fix this, the device could of course implement its own DNS resolver, which would signal with the connectivity subsystem to get the interface up. Usually any delay in name resolution keeps the application in a frozen state, as name resolution is expected to be a fairly quick operation. If we don't mind name resolution triggering connection creation or a "host not found" error every now and then then this is not a showstopper. > More than $TIME has elapsed without an outbound packet. That we basically have with the idle timer settings and iptables. > Signals the kernel to retry the packet Hmm, is this possible with recent kernels? What about those packets to DNS and elsewhere whose state in the application has already timed out? Regards, PAtrik -- Patrik Flykt <Patrik.Flykt at nokia.com>
- Previous message: Localhost unavailable when wi-fi offline or not connected
- Next message: Localhost unavailable when wi-fi offline or not connected
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]