----- Original Message ----- From: Klaus Doering Sent: 05/20/13 04:27 PM To: debian-user@lists.debian.org Subject: Re: Odd Network Problem
On 20/05/13 15:19, george cox wrote: > I think the one thing I would want to know about my original problem > is in the squeeze version of gnome's network-manager, left-clicking > on its notification area icon would, show several options one of > which is "auto eth0", this seemed to reliably attach my laptop's > ethernet port to the default network of the printer-server. I'm pretty certain that the "auto eth0" issue is a red herring: it's only an automatically generated name for your default wired connection, and although I have't dug very deeply, the discussion in [1] would indicate that the change to "Wired connection" was made to make the naming more user friendly. > (...) but the manual clearly says when the > unit is reset if it can't find a dhcp server it will use the default > ip. (...) the print-server defaults to using .102 (...) I'd guess that the different results that you see with the old and the new laptop reflect two not exactly identical procedures. Could you t ry the following sequence: -- reset the printserver so that it falls back to it's default IP setting (192.168.0.102 ?) -- edit your /etc/network/interfaces file to include a static eth0 definition, something like this: auto eth0 iface eth0 inet static address 192.168.0.22 gateway 192.168.0.1 network 192.168.0.0 netmask 255.255.255.0 -- then cycle the interface with ifdown eth0 ifup eth0 -- check with ifconfig eth0 that the interface has the correct address, and that it is shown as UP -- try and connect -- if you now unplug the cable and plug it back in, I believe you'd have to repeat the ifdown ifup cycle What make / model print server do you have? Klaus [1] https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/386900 I can understand the motivation of the poster in [1], there often are a lot of techy details in using linux that can trip newbies up, but I hate to see details covered up. Then the system becomes a black box. In an ideal system, the gory details would be hidden, but could be revealed if the user felt like taking control. But clicking on "auto eth0" must have done something to the interface because until I did that I couldn't get connected. The print-server is a netgear WPGS606. I had a wireless access point made by them as well and I had to use that "auto eth0" before I could even ping the thing. I forget what model the access-point was, it broke six or seven months ago and I chucked it. I'll try reseting it and let you know what happens. Thanks for the help.
