How To: Manual Network Configuration without the need for Network Manager

[thierrybo]

__________________________________________________ __________________________
WPA Connection - WPA-PSK or WPA2-PSK (PSK=Pre-Shared Key) or WPA-EAP-TLS

For uses of Ra-based chipsets: rt61, rt73, rt2500 please skip directly to the WPA Section entitled WPA with Ra based chipsets

Hi,

this is not true since Hardy using new rt20xx Serialmonkey drivers compatibles with "wext" driver. I just used your standard instructions for "WPA Connection - WPA-PSK or WPA2-PSK (PSK=Pre-
Shared Key) or WPA-EAP-TLS" with my RT2500 PCI card and WPA2 on Intrepid and it works out of the box.

[drpaul]

kevdog:

This isn't wireless, but you seem to know how to deal with network connections.

I'm running 8.04 up to date. When I try to run 8.10 from the basic version, my hardwired connection can't get an address from dhclient. Here is the output [my wireless connection works fine]

ubuntu@ubuntu:~$ sudo ifconfig eth0 down
ubuntu@ubuntu:~$ sudo dhclient -r 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:16:36:b3:b4:24
Sending on LPF/eth0/00:16:36:b3:b4:24
Sending on Socket/fallback
ubuntu@ubuntu:~$ sudo ifconfig eth0 up
ubuntu@ubuntu:~$ 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
SIOCSIFADDR: No buffer space available
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:16:36:b3:b4:24
Sending on LPF/eth0/00:16:36:b3:b4:24
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
send_packet: Message too long
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Thanks for your help.

Paul

[kevdog]

Paul

What does ifconfig and lshw -C network show.

[drpaul]

OK. Here's ifconfig in the state where I enabled wireless [have to bring down eth0 or connection to the Web doesn't work. different from 8.04 where whichever interface is working seems to be used. this is b4 I took eth0 down]

eth0 Link encap:Ethernet HWaddr 00:16:36:b3:b4:24
UP BROADCAST RUNNING MULTICAST MTU:64 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2295 (2.2 KB) TX bytes:1835 (1.8 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:16436 Metric:1
RX packets:3592 errors:0 dropped:0 overruns:0 frame:0
TX packets:3592 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:168832 (168.8 KB) TX bytes:168832 (168.8 KB)

wlan0 Link encap:Ethernet HWaddr 00:18:de:1c:27:7e
inet addr:192.168.2.47 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::218:deff:fe1c:277e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1450 (1.4 KB) TX bytes:4427 (4.4 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-18-DE-1C-27-7E-37-37-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)

Here is lshw -C network
This is after I took eth0 down

*-network
description: Wireless interface
product: PRO/Wireless 3945ABG [Golan] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wmaster0
version: 02
serial: 00:18:de:1c:27:7e
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 ip=192.168.2.47 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11abg
*-network DISABLED
description: Ethernet interface
product: PRO/100 VE Network Connection
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:05:08.0
logical name: eth0
version: 02
serial: 00:16:36:b3:b4:24
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=full firmware=N/A latency=64 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: 06:4d:21:03:14:9e
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

Hope this tells you something.

Paul

[kevdog]

This part tells me your interface is disabled:

*-network DISABLED
description: Ethernet interface
product: PRO/100 VE Network Connection
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:05:08.0
logical name: eth0
version: 02
serial: 00:16:36:b3:b4:24
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e100

e100 is a wired interface. Something is happening to disable the interface. Have you checked:
dmesg | more

[drpaul]

kevdog-

I haven't checked dmesg yet, but when that data was collected eth0 was down because I executed

sudo ifconfig eth0 down

so that the system would use wlan0 to connect to the internet. This seems to be necessary with 8.10. Note that there is no IP address assigned to that interface. If I did that in 8.04 it would have one.

Paul

[kevdog]

Ok, so did you get the problem solved?

[drpaul]

Kevdog-

No. I'm just about to reboot into 8.10. What should I look for in dmesg?

Paul

[kevdog]

Make sure you take the wireless interface down, and then enable the wired interface

something like

sudo ifconfig wlan0 down
sudo ifconfig eth0 up


Dont post all of desmg. If you do end up posting part of it, only the part relevant to your network card -- it will be in a group so it should be easy to spot!

[drpaul]

kevdog-

Summary

Did as you suggested. dmesg contains only 2 lines that refer to eth0

[ 4.223709] e100 0000:05:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 4.223771] e100 0000:05:08.0: setting latency timer to 64
[ 4.250272] e100 0000:05:08.0: PME# disabled
[ 4.250663] e100: eth0: e100_probe: addr 0xd8000000, irq 20, MAC addr 00:16:36:b3:b4:24

[ 130.088519] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 135.180135] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

Not very informative to me.

After taking wlan0 down and eth0 up, I tried sudo dhclient eth0

Result

ubuntu@ubuntu:~$ 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
SIOCSIFADDR: No buffer space available
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:16:36:b3:b4:24
Sending on LPF/eth0/00:16:36:b3:b4:24
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
send_packet: Message too long
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
send_packet: Message too long
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

Any ideas?

Paul