Hide Forgot
Description of problem: I'm connecting my FreeRunner phone to my laptop via USB cable. This creates eth1 device which has to be configured manually because no dhcp or similar is running on that line. From time to time (it 100% happens at least once within the first minute the phone is connected) NetworkManager decides to remove the IP address from eth1, killing (freezing) my communication with the phone. Note that I use KDE and its respective Plasma applet/systemsettings module to configure the connections. Version-Release number of selected component (if applicable): NetworkManager-0.8.9997-2.git20110531.fc15.x86_64 kde-plasma-networkmanagement-0.9-0.47.20110323.fc15.x86_64 How reproducible: always Steps to Reproduce: 1. connect FreeRunner (or other such device), wait for kernel to settle and create eth1 2. click the network management icon, go to settings, Network Connections => Wired 3. click Add 4. file in the details: IP Address: Basic settings Method: Manual IP Address: 192.168.0.200 Subnet Mask: 255.255.255.0 Ethernet: Restrict To Interface: eth1 (note that checking or unchecking "Connect automatically" doesn't seem to have any effect) 5. try to connect to the FreeRuner: ssh root.0.202 6. disconnect and connect the phone again 7. try to connect to the FreeRuner: ssh root.0.202 8. set the address manually: ifconfig eth1 192.168.0.202 9. try to connect to the FreeRuner: ssh root.0.202 10. wait about a minute 11. check eth1 settings Actual results: 5. fails, no route to host 7. fails, no route to host eventually, these may succeed, but it is not the exact point of the bug ... 9. connected ok 10. the ssh connection freezes 11. eth1 has no IP address assigned Expected results: 5. connected ok 7. connected ok 9. connected ok 10. no freeze 11. eth1 has 192.168.0.200 Additional info: hovering over the icon, after connecting the cable, it shows things like "connecting" or "getting the address" for a (very long) while, instead of the settings being applied immediately ... like if it would try to run DHCP on it ...
I believe resetting the interfaces is the expected behaviour. I also have a freerunner or two, so I know exactly what you mean, but it is sort of a special case. I believe the best way would be to let the freerunner provide DHCP for the connected host.
(In reply to comment #1) > I believe resetting the interfaces is the expected behaviour. I doubt so ... what'd be the step 4. useful for then? however, this doesn't seem to be an issue anymore, I haven't experienced the config loss for weeks - closing