Announcement

**penguin.ch** · Mar 30, 2007, 11:10 AM

Re: Unable to get Internet access with Live-CD

I may be missing your point, but "my" network looks slightly different:

Code:

ROOT@HAL # ifconfig
eth0   Link encap:Ethernet HWaddr 00:0F:EA:1C:F8:34
     inet addr:192.168.110.1 Bcast:192.168.110.255 Mask:255.255.255.0

You get the point I'm driving at:

Code:

ROOT@HAL # kcmshell kcm_knetworkconfmodule

There you may go (and) figure :P

**lec2004** · Mar 30, 2007, 08:54 PM

Re: Unable to get Internet access with Live-CD

Originally posted by decatur-linux

I need some help in getting my brother on Kubuntu. Unfortunately he lives about 2000 miles away, and we have to do everything by email.

Here is his situation:
He is running a Dell Dimension 8200, with a 2.53 GHz Intel Pentium 4 and 1 Gb memory. At present he is running Windows XP. He has DSL and his ISP is AT&T Yahoo. He is using a Speedstream 5100 Ethernet ADSL modem (by Efficient Networks). Apparently he is set up in the standard manner: Telephone cable-->DSL modem-->Network card. He has no trouble with Internet access under Windows XP, but he cannot get Internet access with the Kubuntu 6.06 Live-CD, or any other Live-CD that I have sent him.

Let me give you some information, first from Windows XP, and then from Kubuntu, regarding his setup and see if you can suggest reasons why he cannot get Internet access under Kubuntu.

From Belarc Advisor (a good Windows program that lists hardware and its capabilities), under Communications it shows the following:
D-Link DFE-530TX+ PCI Adapter #2
primary APIPA Address: 169.254.36.136 / 16
Physical Address: 00:40:05:07:B4:B2
WAN (PPP/SLIP) Interface
IP Address: 85.35.211.38 / 32
Gateway: 75:35:211:38
Physical Address: 00:53:45:00:00:00

Notice the APIPA Address of the network card. APIPA stands for Automatic Private IP Addressing and means that "APIPA clients can automatically self-configure an IP address and subnet mask when a DHPC server isn't available...APIPA automatically configure(s) itself with an IP address from a range that has been reserved for Microsoft...the...range is 169.254.0.1 through 169.254.255.254." Of course, the APIPA IP address is non-routable and will not work on the Internet. Yet he has Internet access: the WAN Interface has been given an acceptable IP address.

When he looks, again under Windows, for his Internet connection, this is what he finds:
Local Area Conection
D-Link DFE-530 TX+ PCI Adapter #2

"General" Tab
Connection
Status: Limited or no connectivity
Duration: hh:mm;ss (Value changes)
Speed: 100.0 Mbps
Activity
Sent Received
xx,xxx yy,yyy

"Support" Tab Limited or not connectivity. You may
not be able to access the internet or
some network resources. This problem
occurred because the network did not
assign a network address to the
computer.
Details
Property Value
Physical Address 00-40-05-07-B4-B2
IP Address 169.254.36.136
Subnet Mask 255.255.0.0
Default Gateway
DNS Server
WINS Server

Now, when he boots the Live-Cd of Kubuntu 6.06 and runs certain commands in Konsole, here is what he gets:
COMMAND: lshw
OUTPUT (selected):
*-network
description: Ethernet interface
product: RTL8139 Ethernet
vendor: D-Link System Inc
physical id: 7
bus info: pci@02:07.0
logical name: eth0
version: 10
serial: 00:40:05:07:b4:b2
width: 32 bits
bus: 33 MHz
capabilities: bus_master cap.list ethernet
physical
configuration: broadcast=yes driver=8139too
multicast=yes
resources: ioport: ec00-ecff iomemory: fe1ffcoo-
fe1ffcff irq: 185

COMMAND: ifconfig
OUTPUT:
eth0 Link encap: Ethernet HWaddr 00:40:05:07:B4:B2
UP BROADCAST RUNNING MULTICAST MTU: 1500
Metric: 1
RX packets: 0 errors: 0 dropped: 0 overruns: 0
frame: 0
TX packets: 29 errors: 0 dropped: 0 overruns: 0
carrier: 0
collisions: 0 txqueue len: 1000
RX bytes: 0(0.0b) TX bytes: 9918 (9.6 KiB)
Interrupt: 185 Base address: xcc00

lo Link encap: Local Loopback
inet addr: 127.0.0.1 mask: 255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric: 1
RX packets: 19 errors: 0 dropped: 0 overruns: 0
frame: 0
TX packets: 19 errors: 0 dropped: 0 overruns: 0
carrier: 0
collisions: 0 txqueue len: 0
RX bytes:1356 (1.3 KiB) TX bytres:1356 (1.3 KiB)

COMMAND: dmesg | grep eth
OUTPUT:
eth0: RealTek RTL8139 at 0xf88bcc00,
00:40:05:07:b4:b2, IRQ185
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link up, 100Mbps, full duplex, lpa 0x41E1

COMMAND: lsmod | grep 8139
OUTPUT:
8139too 26880 0
mii 5888 1 8139too

I am concerned that the output to ifconfig does not list an "inet address", but the output to dmesg | grp eth shows that the link is up.

Any help or pointers will be much appreciated.

The problem you have is the computer, if I am reading the belarc right, is the NIC does not have a connection to the modem. Windows will assign itself APIPA when there is no connection and Linux will simply not have a ip address. Does he happen to have wireless adapter on the machine. Do an ipconfig in Windows and what is the IP address of the NIC. You only get the 169.254 address when there is no active connection.

Announcement

Unable to get Internet access with Live-CD

Unable to get Internet access with Live-CD

Comment

Comment