[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Network problems after system recovery



 
Hi list,

I just duplicated my system onto a Thinkpad T40 like this: 

- used netinst to install a base etch system, 
- used a generated list of installed packages from my old (dying) machine to 
install all the same packages, 
- compiled an extra kernel from Debian sources using my old kernel config with 
a couple of changes for the different hardware, 
- then copied over all my backed up data and some config files.

Foolproof, right? Well, nearly...the main problem is networking, which is not 
my strong suit, so I'm hoping for a couple of tips.

On the old machine, NetworkManager worked beautifully; once I had 
commented out all but the loopback interface from /etc/network/interfaces, it 
took care of everything - with KNetworkManager, it would automatically 
connect to a wired interface if plugged in, or to an open wireless network, 
asking me for an appropriate key or passphrase if required.

During the netinstall and package installations, the wired ethernet connection 
worked automatically with the e100 module and DHCP.

But now the installation is complete, there is a complex bundle of problems:

- with NetworkManager:

        - Wired ethernet is claimed to be connected, sometimes reporting a 
169.* ip address, in which case pinging the router fails, or a 192.* address, 
in which case the router can be pinged; in both cases I cannot connect to the 
internet, even using numerical addresses. NetworkManager reports: 

        "NetworkManager: <information>   DHCP returned name servers but system
        has disabled dynamic modification!"

        -Wireless connection using wpa_supplicant fails, 
with 
this output:

NetworkManager: <debug info>    [1157879555.879241]
[snip]
NetworkManager: <information>   SUP: sending command 'INTERFACE_ADD wireless 
wext     /var/run/wpa_supplicant '
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
NetworkManager: <information>   SUP: response was ''
NetworkManager: <WARNING>        nm_utils_supplicant_request_with_check (): 
supplicant_interface_init: supplicant error for 'INTERFACE_ADD wireless            
wext     /var/run/wpa_supplicant '.  Response: ''
NetworkManager: <WARNING>        real_act_stage2_config (): Activation 
(wireless/wireless): couldn't connect to the supplicant.
NetworkManager: <information>   Activation (wireless) failed for access point 
(default)
NetworkManager: <information>   Activation (wireless) failed.
NetworkManager: <information>   Deactivating device wireless.
NetworkManager: <information>   Activation (wireless) failure scheduled...
NetworkManager: <information>   Activation (wireless) Stage 2 of 5 (Device 
Configure) complete.
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 -   ]

- If I re-establish my interfaces file and use ifupdown:

        - Wired ethernet with DHCP fails with:

        "DHCPDISCOVER on ethernet to 255.255.255.255 port 67 interval 4
        send_packet: Message too long";

        or with a static setup, it doesn't enable browsing.

        - Wireless works, but not with wpa_supplicant. Uses DHCP and the airo 
module.

AFAIKT (which is not very) this means that there are at least two problems: 
DHCP has stopped working for the ethernet interface - presumably because of 
some installed program - and wpa_supplicant is not working for the wireless 
interface.

Any pointers as to how to begin solving these problems would be greatly 
appreciated.

Thanks,

John


  



Reply to: