Embedded Plug Cmputer Debian Network problem

Status
Not open for further replies.

priestnot

Member level 5
Joined
May 1, 2006
Messages
89
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,288
Activity points
2,098
First of all this is my first post and I would like to thanks all the help you all can give...

I have detected a problem on the network of the Stratus plug.

The problem is that if I connect the ethernet cable after we connect the Stratus to the power socket, the plug does not get a IP address and there for does not connect to the network. (If I connect the ethernet cable before the power socket it gets a ip and we have network access).

When I connect the ethernet cable there is a dmesg on the serial terminal:
> eth0: link up, 100 Mb/s, full duplex, flow control disabled
So it detects the cable connection but it does not "reactivate" the network

The /etc/network/interfaces looks like this:

Code:
root@quiiq:~# cat /etc/network/interfaces
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp 
#	address 192.168.1.200
#	gateway 192.168.1.254
#	netmask 255.255.255.0
#	network 192.168.1.0
#	broadcast 192.168.1.255

The ifconfig after a connection to the power with the ethernet cable looks like this:
Code:
root@quiiq:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:26:db:00:1f:7b  
          inet addr:192.168.1.126  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::226:dbff:fe00:1f7b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:61 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6192 (6.0 KiB)  TX bytes:1354 (1.3 KiB)
          Interrupt:11 


lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

uap0      Link encap:Ethernet  HWaddr 00:26:37:d5:56:fc  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

And the ifconfig after a connection to the power without the ethernet cable looks like this:
Code:
root@quiiq:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:26:db:00:1f:7b  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:11 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

uap0      Link encap:Ethernet  HWaddr 00:26:37:d5:56:fc  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

So it does not have an IP address

After i connect the ethernet cable i get this message:
eth0: link up, 100 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

But i get this ifconfig (no Ip address)
Code:
root@quiiq:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:26:db:00:1f:7b  
          inet6 addr: fe80::226:dbff:fe00:1f7b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:86 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7024 (6.8 KiB)  TX bytes:328 (328.0 B)
          Interrupt:11 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

uap0      Link encap:Ethernet  HWaddr 00:26:37:d5:56:fc  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


I would like to know if you know a way to resolve this?


Best regards,
 

In /etc/network/interfaces, you might want to include the "auto" parameter also for the eth0 interface, like you see for the lo interface just above. So change:

Code:
allow-hotplug eth0
iface eth0 inet dhcp
To:
Code:
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
And then see if problem is solved? Other thing I can think of is check whether a dhcp client is installed, but from your problem description that seems to be the case?
 

And then see if problem is solved? Other thing I can think of is check whether a dhcp client is installed, but from your problem description that seems to be the case?

It did not solved the problem and yes i have a dhcp client or else not even the boot with cable worked.
The dhcp client that is used is dhclient...
 
Last edited:

After including "auto eth0" in /etc/network/interfaces, and connecting network cable after power up, try:
Code:
~$ sudo invoke-rc.d networking restart
(enter without sudo if you're already root).
Does that cause an IPv4 address to be assigned to eth0?
 


That gave the system a Ip but i cannot ping anything.

Any other solutions?
 

Status
Not open for further replies.
Cookies are required to use this site. You must accept them to continue using the site. Learn more…