Hi Patrik, Ben Hutchings wrote: > On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote:
>> I suspect this bug is when a task (i.e. ntp, virus updater, ...) tries >> to connect to the Internet through a socket using the first interface, >> holds it open, the kernel won't reroute to the new one and you need try >> to again. [...] >> Example: When one wlan connection is up and you try to connect throught an >> other one, you need to retry. >> >> I have tested both examples with lftp trying to connect to an IP-address >> and you cant' connect as long as lftp's socket is in effect. > > Please explain in more detail what you're doing: > - All the commands you run to reconfigure and use the network > - The routing table (as shown by 'ip r') after each reconfiguration I suspect there was a miscommunication here: if I understand correctly, Ben was looking for a simple sequence of steps and, for each step, a routing table from after that step. This would help him to understand what was happening when you ran into this problem. Perhaps he could run similar steps in a similar setup and compare, to track down where the problem lies. See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for more context. Thanks for your patience, and hope that helps. Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121104180006.GA28816@elie.Belkin
