Re: Odd Network Problem
On 20/05/13 23:08, george cox wrote:
>
>
>>
>> ----- 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 haven'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.
>>
>> [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.
All the technical details are still there, in (right click) -->
"Connection Information" and in "Edit Connections". If you really wanted
the label "auto eth0" back, just edit the connection and rename it. The
"magic" lies in the "automatically connect to this network when it is
available" (General tab), and in selecting the necessary IP setting
(most likely IPv4, DHCP).
---
After a factory reset of your print server, it cannot connect to your
wifi, and thus it cannot acquire an IP address via DHCP, and thus it
cannot pass-through DHCP request from other clients connected to the
4-port switch. Now, if your new laptop's "Wired Connection" is set up
as above, then the connection cannot be made since there is no DHCP
server available at that point. Hence my suggestion to manually set
the IP, and even go through the command line to make it more
obvious. Under those circumstances there is not much magic left, and
you have to bring down and back up the interface manually (the ifdown
eth0 -- ifup eth0 cycle in my last post).
It would still be easier to connect both, the laptop and one of the
four ethernet ports of the print server, to your router --- under the
assumption that the router is using the same subnet (192.168.0.x), has
at least two ethernet port available, and acts as the DHCP server. In
that case, your laptop will automatically connect, acquire an IP
address, and you can now access 192.168.0.102 without any further
stress.
HTH
Klaus
[2] http://kbserver.netgear.com/pdf/wgps606_user_manual.pdf
Reply to: