Okay, here's the gen:
Output of "ifconfig -a"
Code:
eth0 Link encap:Ethernet HWaddr 00:23:cd:00:19:83
inet6 addr: fe80::223:cdff:fe00:1983/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1225 (1.2 KB) TX bytes:4156 (4.1 KB)
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:65536 Metric:1
RX packets:28 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2032 (2.0 KB) TX bytes:2032 (2.0 KB)
Output of "sudo lshw -numeric -C network"
Code:
*-network
description: Ethernet interface
product: IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY [13F0:200]
vendor: Sundance Technology Inc / IC Plus Corp [13F0]
physical id: c
bus info: pci@0000:02:0c.0
logical name: eth0
version: 31
serial: 00:23:cd:00:19:83
size: 100Mbit/s
capacity: 100Mbit/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=sundance driverversion=1.2 duplex=full latency=32 link=yes maxlatency=10 mingnt=10 multicast=yes port=MII speed=100Mbit/s
resources: irq:9 ioport:b400(size=128) memory:de000000-de0001ff memory:dff00000-dff0ffff
Thank you SeijiSensei, that was a real guru reply. Yes, the first command allowed me to ping the router! The second command allowed me to ping the Google DNS server!
So far, so good. As you say, it's now a case of determining why the TCP/IP configuration is not being set at boot time. Looking forward to your next diagnostic suggestion.
Bookmarks