Bug#692025: linux: internet connection refused after new route
On 11/01/2012 03:13 PM, Ben Hutchings wrote:
> On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote:
>> Package: linux
>> Version: linux-image
>
> Can we have a real version number please? (/proc/version will show the
> Debian package version for the running kernel).
>
Linux version 2.6.32-5-686 (Debian 2.6.32-46) (dannf@debian.org) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 09:49:36 UTC 2012
>> Severity: important
>> Tags: upstream
>>
>> When one lan interface is connected and you try to connect an other one,
>> often you can't connect to the Internet after that. You need to retry the
>> connection.
>>
>> 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 a openvpn connection is made and initiation is okey, but you
>> can't connect to the Internet, through the openvpn-connection. Retrying it
>> and you can connect.
>>
>> 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
Openvpn reconfigurates the routing by itself, and no warnings are issued
about the route or the connection. Everything seems to be okay.
Example Openvpn:
1) Connect to an openvpn server using: /usr/sbin/openvpn --config
$config --auth-user-pass account.txt --mute-replay-warnings
2) Almost every time the first connection attempt fails, and I need to
retry the connection.
Example WLAN:
1) Connect WLAN from your computer to a router 1
2) run lftp 192.168.0.123 -e "set ssl:verify-certificate no;set
dns:fatal-timeout 1m; set net:idle 30s; set net:max-retries 10; set
net:reconnect-interval-multiplier 1; set net:timeout 30s; set
xfer:disk-full-fatal true; set net:reconnect-interval-base 5; cd
\"test\"; mkdir -p \"test\"; set cmd:fail-exit yes; put -E -c \"test\"
-o \"test\"; quit"
3) Connect WLAN to router 2
I have a script that does this for me. When the script is running, the
connection change fails. Of course it didn't do it when I tried to get
the bug showing from the command line.
>
> Ben.
>
Reply to: