Howto: Ethernet connection without a GUI

[kyonides]

Re: Howto: Ethernet connection without a GUI

Earlier this year some user said...

Hopefully you will see at least eth0 and lo listed.

Why would it be listed still, by removing those 2 packages you have just knocked out the eth0 as well. A little testing might have been an good idea as i now have to find out how to get eth0 being detected by ifconfig. Which was there prior to following your instructions.

And of course i cannot install them again either as i have no network connection for apt to be able to install from the repo. Thanks, but this tute is a big fail so far.

Now maybe you might like to tell me how to get eth0 working again, and put that into your tute to make it not so much fail

I must say that this guide actually helped me a lot by bringing my internet connection back to life. Of course, you'd need some Distro Install CD before you uninstall network-manager(-kde).

[seangee]

Re: Howto: Ethernet connection without a GUI

I must say that this guide actually helped me a lot by bringing my internet connection back to life. Of course, you'd need some Distro Install CD before you uninstall network-manager(-kde).

Worked fine for me and I never had to install anything. It doesn't knock anything out. Initially I couldn't bring up eth0 because I had blindly copied the address and was on the incorrect subnet. sudo ifconfig -a proved the device existed so all I had to do was trace the typo 8)

[NMY]

Re: Howto: Ethernet connection without a GUI

Please edit the main post with:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address <your ip address>
netmask <your netmask>
gateway <your gateway>

[kevinc]

Re: Howto: Ethernet connection without a GUI

Hi,

after some research in the different forums I found a fix that works. And by working I mean
* I can hot-plug a cable in eth0 wich is then configured via DHCP
* I can use WLAN
* And all this with this crappy KNetworkManager

All I had to do was to wipe out almost everything in /etc/network/interfaces leaving it with the bare essentials:

auto lo
iface lo inet loopback

Reboot and you're done. All of the sudden KNetworkManager works quite fine now.

Maybe this helps someone.

Christian

Very interesting. My Jaunty worked perfectly with dhcp until I tried to connect PPPoE and couldn't get it to work, then followed instructions which stopped everything from working. Going back to my dual boot Intrepid I find the /etc/network/interfaces is exactly as you mention and it works nicely with wireless and dhcp. As I need at least one working system, I'm not going to touch it until I get my Jaunty working. I've spend hours finding lots of information but nothing that has helped, yet. When I do manage to, I'll add to the post.

[pdaalder]

Re: Howto: Ethernet connection without a GUI

Hi I've been reading this topic, and I've tried what you suggested, but unfortunately it didn't deliver what I was looking for.

My interfaces file (/etc/network/interfaces) is like:
[quote]
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
[quote]

doing ifconfig returns a similar list as another poster (both eth0 and eth0:avahi). I'm not using a proxy, but just a direct conection to the ethernet cable. I know there is a connection, as I have with the same cable a connection on my other machine. I upgraded (completely reinstalled kubuntu 9.04 today, so formated partitions) today, and since today it stopped.

The machine is a Dell D820, with a Broadcom NetXtreme GB card. Any tip, never expected installing would be so stressfull. I wished I was paid by hour for this :-(.

Do you see the eth0:avahi that shows an IP address of 169.254.6.194? That means the computer was unable to find a DHCP server and it uses that address so that it can continue, but it is not a true internet connection.

The problem is in the settings you need to connect through your proxy, and I have no experience with that. How do you have your Wii connected? Who runs the proxy? Can they provide you with the information needed to connect?

[Detonate]

Re: Howto: Ethernet connection without a GUI

See if you can get connected by running:

sudo dhclient eth0

in a terminal.

[pdaalder]

Re: Howto: Ethernet connection without a GUI

no luck, also tried what this article says:
http://www.prash-babu.com/2009/05/ho...in-ubuntu.html

but no luck.

Any other thinks I can try.

[pdaalder]

Re: Howto: Ethernet connection without a GUI

oh, just so you know, I've downloaded today the version, and it is using linux 2.6.28.11-generic

[Detonate]

Re: Howto: Ethernet connection without a GUI

When you ran the dhclient command, what was the output?

[pdaalder]

Re: Howto: Ethernet connection without a GUI

pdaalder@D820:~$ sudo dhclient eth0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:15:c5:09:c5:5a
Sending on LPF/eth0/00:15:c5:09:c5:5a
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

pdaalder@D820:~$ sudo more /etc/network/interfaces
auto lo
iface lo inet loopback

iface eth0 inet dhcp
auto eth0

Note:this file wasn't there I've created it manually

root@D820:~# more /etc/resolv.conf
nameserver 208.67.222.222
nameserver 208.67.220.220

root@D820:~# more /proc/version
Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009

root@D820:~# /etc/init.d/networking restart
* Reconfiguring network interfaces...There is already a pid file /var/run/dhclient.eth0.pid with pid 3652
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:15:c5:09:c5:5a
Sending on LPF/eth0/00:15:c5:09:c5:5a
Sending on Socket/fallback
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:15:c5:09:c5:5a
Sending on LPF/eth0/00:15:c5:09:c5:5a
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

root@D820:~# ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 4048
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:15:c5:09:c5:5a
Sending on LPF/eth0/00:15:c5:09:c5:5a
Sending on Socket/fallback

root@D820:~# ifup eth0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:15:c5:09:c5:5a
Sending on LPF/eth0/00:15:c5:09:c5:5a
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

root@D820:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:c5:09:c5:5a
inet6 addr: fe80::215:c5ff:fe09:c55a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:169 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20800 (20.8 KB) TX bytes:8065 (8.0 KB)
Interrupt:18

eth0:avahi Link encap:Ethernet HWaddr 00:15:c5:09:c5:5a
inet addr:169.254.6.145 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:18

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:69 errors:0 dropped:0 overruns:0 frame:0
TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4804 (4.8 KB) TX bytes:4804 (4.8 KB)

pan0 Link encap:Ethernet HWaddr 56:9a:46:95:83:7f
inet6 addr: fe80::549a:46ff:fe95:837f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:1152 (1.1 KB)

wlan0 Link encap:Ethernet HWaddr 00:13:02:6d:70:c2
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)

wmaster0 Link encap:UNSPEC HWaddr 00-13-02-6D-70-C2-00-00-00-00-00-00-00-00-00-00
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)

root@D820:/etc# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)
03:01.0 CardBus bridge: O2 Micro, Inc. Cardbus bridge (rev 21)
03:01.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

When I plugin the cable and check the system:

root@D820:/# dmesg
[ 1425.809137] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 1425.809143] tg3: eth0: Flow control is off for TX and off for RX.

root@D820:/# ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 4380
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:15:c5:09:c5:5a
Sending on LPF/eth0/00:15:c5:09:c5:5a
Sending on Socket/fallback

root@D820:/# dmesg
[ 1425.809137] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 1425.809143] tg3: eth0: Flow control is off for TX and off for RX.

root@D820:/# ifup eth0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:15:c5:09:c5:5a
Sending on LPF/eth0/00:15:c5:09:c5:5a
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

root@D820:~# dmesg
[ 1425.809137] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 1425.809143] tg3: eth0: Flow control is off for TX and off for RX.
[ 1507.628310] tg3 0000:09:00.0: irq 2297 for MSI/MSI-X
[ 1507.716767] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1509.330294] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 1509.330301] tg3: eth0: Flow control is off for TX and off for RX.
[ 1509.330888] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1520.212150] eth0: no IPv6 routers present

This is my try with static IP: modified /etc/network/interfaces

root@D820:~# vi /etc/network/interfaces
auto lo
iface lo inet loopback

#iface eth0 inet dhcp
#auto eth0

auto eth0
iface eth0 inet static
address 212.187.61.178
netmask 255.255.255.0
gateway 212.187.61.1

root@D820:/etc/network# ../init.d/networking restart
* Reconfiguring network interfaces...SIOCDELRT: No such process [ OK ]

retried it:
root@D820:/etc/network# ../init.d/networking restart
* Reconfiguring network interfaces... [ OK ]

root@D820:/etc/network# ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:c5:09:c5:5a
inet addr:212.187.61.178 Bcast:212.187.61.255 Mask:255.255.255.0
inet6 addr: fe80::215:c5ff:fe09:c55a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:81 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8616 (8.6 KB) TX bytes:4879 (4.8 KB)
Interrupt:18

root@D820:~# dmesg
[ 1932.000383] tg3 0000:09:00.0: irq 2297 for MSI/MSI-X
[ 1932.105029] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1933.702326] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 1933.702343] tg3: eth0: Flow control is off for TX and off for RX.
[ 1933.702929] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1943.912083] eth0: no IPv6 routers present

No internet connection, but I hope you guys understand this.

[kevinc]

Re: Howto: Ethernet connection without a GUI

@pdaalder What type of connection do you have. You mentioned 'plugging in the cable' so it's not wireless.
Of the various types of wired connections, which both nm and wicd are not good at detecting, there are those that use dhcp which is most easily detected, others require a proxy, others require a username and password, others require more information, such as DNS, sometimes primary and secondary, netmask, IP address.

If you have used this connection on another system, what information did you have to supply to be able to connect?

[Detonate]

Re: Howto: Ethernet connection without a GUI

Yes, we need to know if you are connecting through a router, or ar you connecting directly to a cable or dsl modem. One very simple reason for your problem could be a bad cable.

[pdaalder]

Re: Howto: Ethernet connection without a GUI

Not sure what you mean with type of connection, but I believe it is just a regular ethernet connection

My machine runs dual boot, so tried it with windows, but unfortunately I'm not have fun there even. Message: unable to contact your DHCP server.

The cable I use is connected normally to a windows xp machine. I compared the details of the LAN of machine A with machine B, and I adjusted the differences. No luck.

Is my card broken? I was using it last week fine (other location, so other connection, but wired also)

Do you think the provider is blocking it?

[Detonate]

Re: Howto: Ethernet connection without a GUI

Now we are on to something. It won't connect in windows either. Can you swap the cards in your two machines just to see what happens? And try another cable.

[pdaalder]

Re: Howto: Ethernet connection without a GUI

[Feeling stupid]
Damn, after all the time of research, unbelievable, it is the modem/router of the provider that was causing the problem. The problem was memory at the thingy. I called the provider, and explained what was happening, he told me that the router keeps a communication with a computer in memory. So my other computer was "unknown" and therefor it refused the connection. After rebooting (keeping energy of for 30sec) the router, the router did understood my machine, and now I'm happily typing this message of Kubuntu.

I'm in love with Kubuntu, amazing what has been accomplished, and thanks all for being that helpfull.
[/Feeling stupid]