LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Network is unreachable??? (http://www.linuxquestions.org/questions/linux-networking-3/network-is-unreachable-125094/)

Tnichols 12-11-2003 09:06 PM

Network is unreachable???
 
I just installed Linux today for the first time. So I have a whole day of experience. I was surprised that I did get it going... But I do have a big problem.... I can not connect to the internet... I can not even ping anything... every time I try to ping any address I get the message "Network is unreachable" and I don't have a clue where to go from here.

The computer I am using is a IBM Intellistation M Pro and that has a on the mother board ethernet adapter. I am using Slackware 9.1

I tried dhcp and I tried static setting but without any success.

Here is the log....

Dec 11 20:57:27 HAL2010 syslogd 1.4.1: restart.
Dec 11 20:57:28 HAL2010 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Dec 11 20:57:28 HAL2010 kernel: BIOS-provided physical RAM map:
Dec 11 20:57:28 HAL2010 kernel: 128MB LOWMEM available.
Dec 11 20:57:28 HAL2010 kernel: IBM machine detected. Enabling interrupts during APM calls.
Dec 11 20:57:28 HAL2010 kernel: Initializing CPU#0
Dec 11 20:57:28 HAL2010 kernel: Memory: 126064k/131072k available (2115k kernel code, 4620k reserved, 692k data, 120k init, 0k highmem)
Dec 11 20:57:28 HAL2010 kernel: Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Dec 11 20:57:28 HAL2010 kernel: Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
Dec 11 20:57:28 HAL2010 kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Dec 11 20:57:28 HAL2010 kernel: Buffer cache hash table entries: 8192 (order: 3, 32768 bytes)
Dec 11 20:57:28 HAL2010 kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
Dec 11 20:57:28 HAL2010 kernel: CPU: L2 cache: 512K
Dec 11 20:57:28 HAL2010 kernel: Checking 'hlt' instruction... OK.
Dec 11 20:57:28 HAL2010 kernel: PCI: PCI BIOS revision 2.10 entry at 0xfd9c1, last bus=0
Dec 11 20:57:28 HAL2010 kernel: PCI: Using configuration type 1
Dec 11 20:57:28 HAL2010 kernel: PCI: Probing PCI hardware
Dec 11 20:57:28 HAL2010 kernel: Limiting direct PCI/PCI transfers.
Dec 11 20:57:28 HAL2010 kernel: Activating ISA DMA hang workarounds.
Dec 11 20:57:28 HAL2010 kernel: Linux NET4.0 for Linux 2.4
Dec 11 20:57:28 HAL2010 kernel: Based upon Swansea University Computer Society NET3.039
Dec 11 20:57:28 HAL2010 kernel: VFS: Disk quotas vdquot_6.5.1
Dec 11 20:57:28 HAL2010 kernel: Journalled Block Device driver loaded
Dec 11 20:57:28 HAL2010 kernel: vesafb: framebuffer at 0xff000000, mapped to 0xc880d000, size 3072k
Dec 11 20:57:28 HAL2010 kernel: vesafb: mode is 1024x768x16, linelength=2048, pages=0
Dec 11 20:57:28 HAL2010 kernel: vesafb: protected mode interface info at c000:7c3c
Dec 11 20:57:28 HAL2010 kernel: vesafb: scrolling: redraw
Dec 11 20:57:28 HAL2010 kernel: vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Dec 11 20:57:28 HAL2010 kernel: fb0: VESA VGA frame buffer device
Dec 11 20:57:28 HAL2010 kernel: Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
Dec 11 20:57:28 HAL2010 kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
Dec 11 20:57:28 HAL2010 kernel: Real Time Clock Driver v1.10e
Dec 11 20:57:28 HAL2010 kernel: Floppy drive(s): fd0 is 1.44M
Dec 11 20:57:28 HAL2010 kernel: FDC 0 is a National Semiconductor PC87306
Dec 11 20:57:28 HAL2010 kernel: loop: loaded (max 8 devices)
Dec 11 20:57:28 HAL2010 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
Dec 11 20:57:28 HAL2010 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Dec 11 20:57:28 HAL2010 kernel: PIIX3: IDE controller at PCI slot 00:07.1
Dec 11 20:57:28 HAL2010 kernel: PIIX3: chipset revision 0
Dec 11 20:57:28 HAL2010 kernel: PIIX3: not 100%% native mode: will probe irqs later
Dec 11 20:57:28 HAL2010 kernel: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio
Dec 11 20:57:28 HAL2010 kernel: ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
Dec 11 20:57:28 HAL2010 kernel: hdc: ATAPI 8X CD-ROM drive, 128kB Cache, DMA
Dec 11 20:57:28 HAL2010 kernel: Uniform CD-ROM driver Revision: 3.12
Dec 11 20:57:28 HAL2010 kernel: SCSI subsystem driver Revision: 1.00
Dec 11 20:57:28 HAL2010 kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
Dec 11 20:57:28 HAL2010 kernel: Detecting Adaptec I2O RAID controllers...
Dec 11 20:57:28 HAL2010 kernel: Red Hat/Adaptec aacraid driver (1.1.2 Sep 2 2003 17:32:27)
Dec 11 20:57:28 HAL2010 kernel: scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
Dec 11 20:57:28 HAL2010 kernel: Partition check:
Dec 11 20:57:28 HAL2010 kernel: sda: sda1 sda2
Dec 11 20:57:28 HAL2010 kernel: md: linear personality registered as nr 1
Dec 11 20:57:28 HAL2010 kernel: md: raid0 personality registered as nr 2
Dec 11 20:57:28 HAL2010 kernel: md: raid1 personality registered as nr 3
Dec 11 20:57:28 HAL2010 kernel: md: raid5 personality registered as nr 4
Dec 11 20:57:28 HAL2010 kernel: raid5: measuring checksumming speed
Dec 11 20:57:28 HAL2010 kernel: md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Dec 11 20:57:28 HAL2010 kernel: md: Autodetecting RAID arrays.
Dec 11 20:57:28 HAL2010 kernel: md: autorun ...
Dec 11 20:57:28 HAL2010 kernel: md: ... autorun DONE.
Dec 11 20:57:28 HAL2010 kernel: LVM version 1.0.5+(22/07/2002)
Dec 11 20:57:28 HAL2010 kernel: Initializing Cryptographic API
Dec 11 20:57:28 HAL2010 kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Dec 11 20:57:28 HAL2010 kernel: IP Protocols: ICMP, UDP, TCP
Dec 11 20:57:28 HAL2010 kernel: IP: routing cache hash table of 1024 buckets, 8Kbytes
Dec 11 20:57:28 HAL2010 kernel: TCP: Hash tables configured (established 8192 bind 16384)
Dec 11 20:57:28 HAL2010 kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Dec 11 20:57:28 HAL2010 kernel: Freeing unused kernel memory: 120k freed
Dec 11 20:57:28 HAL2010 kernel: Adding Swap: 1020116k swap-space (priority -1)
Dec 11 20:57:28 HAL2010 kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
Dec 11 20:57:28 HAL2010 kernel: agpgart: Maximum main memory to use for agp memory: 96M
Dec 11 20:57:28 HAL2010 kernel: scsi2 : SCSI host adapter emulation for IDE ATAPI devices
Dec 11 20:57:28 HAL2010 kernel: Linux Kernel Card Services 3.1.22
Dec 11 20:57:28 HAL2010 kernel: options: [pci] [cardbus] [pm]
Dec 11 20:57:28 HAL2010 kernel: isapnp: Scanning for PnP cards...
Dec 11 20:57:28 HAL2010 kernel: isapnp: Card 'CS4236B Audio'
Dec 11 20:57:28 HAL2010 kernel: isapnp: 1 Plug & Play card detected total
Dec 11 20:57:28 HAL2010 kernel: Intel PCIC probe: not found.
Dec 11 20:57:28 HAL2010 kernel: Databook TCIC-2 PCMCIA probe: not found.
Dec 11 20:57:28 HAL2010 kernel: ds: no socket drivers loaded!
Dec 11 20:57:28 HAL2010 kernel: usb.c: registered new driver usbdevfs
Dec 11 20:57:28 HAL2010 kernel: usb.c: registered new driver hub
Dec 11 20:57:28 HAL2010 kernel: uhci.c: USB Universal Host Controller Interface driver v1.1
Dec 11 20:57:28 HAL2010 kernel: uhci.c: USB UHCI at I/O 0xff80, IRQ 9
Dec 11 20:57:28 HAL2010 kernel: usb.c: new USB bus registered, assigned bus number 1
Dec 11 20:57:28 HAL2010 kernel: hub.c: USB hub found
Dec 11 20:57:28 HAL2010 kernel: hub.c: 2 ports detected
Dec 11 20:57:28 HAL2010 kernel: eth0: Intel Corp. 82557/8/9 [Ethernet Pro 100], 00:60:94:69:4B:27, IRQ 10.
Dec 11 20:57:28 HAL2010 kernel: Receiver lock-up bug exists -- enabling work-around.
Dec 11 20:57:28 HAL2010 kernel: Board assembly 000000-000, Physical connectors present: RJ45
Dec 11 20:57:28 HAL2010 kernel: Primary interface chip unknown-11 PHY #1.
Dec 11 20:57:28 HAL2010 kernel: General self-test: passed.
Dec 11 20:57:28 HAL2010 kernel: Serial sub-system self-test: passed.
Dec 11 20:57:28 HAL2010 kernel: Internal registers self-test: passed.
Dec 11 20:57:28 HAL2010 kernel: ROM checksum self-test: passed (0x49caa8d6).
Dec 11 20:57:28 HAL2010 kernel: Receiver lock-up workaround activated.
Dec 11 20:57:29 HAL2010 sshd[498]: Server listening on 0.0.0.0 port 22.


I am about ready to put Windows 95 back on the machine just to check out all the hardware and network connections. But that will take some time. I was hoping for a easy fix.

Thanks

Tom...

cetialphav 12-11-2003 10:35 PM

Can you post the output of these commands? That will provide a better picture of the state of your machine.

/sbin/ifconfig -a

netstat -rn

jemmrich 12-11-2003 11:31 PM

I had what sounds like the same problem and i was sent the following fix by email which worked no probs for my case.

My details:
Runing Libranet
Enthernet is built into the motherboard... I think this is whats causing the problem. Ive only hit this problem when installing on systems with a built in network port. Mines a SIS something... (cant remember of hand)

The email i got for the fix:
[-------- start of email --------]
Perhaps a different DHCP client will work better.
Could you download the file
http://ftp.debian.org/debian/pool/ma...pl4-9_i386.deb

and transfer it to /tmp in Libranet and run the following commands:
Code:

apt-get --purge remove pump
dpkg -i /tmp/dhcpcd_*.deb

Then run:
Code:

ifdown eth0
ifup eth0

To see if dhcpcd will work better than pump.
[-------- end of email --------]

I'm just getting into linux myself, so im not sure how this will work in your case, maybe someone will beable to provide more information on what this actually does/how to use it for your situation...

Good luck

chort 12-12-2003 02:29 AM

Errrmm, I doubt that apt-get will work on Slackware... Libranet is a Debian-based distro, so that's why it uses apt-get. I don't think Slack is based on any other Linux, to my knowledge.

Any way, the problem is that you are not giving yourself an IP that is on your network. You need to know what the IP/subnet is that your router is using, then you can assign your Linux box an IP on that network.

Tnichols 12-18-2003 03:05 PM

Ok, here is the output from the /sbin/ifconfig -a command:

eth0 Link encap:Ethernet HWaddr 00:60:94:69:4B:27
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:1180 (1.1 Kb)
Interrupt:10 Base address:0xe000

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: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)

and here is the output from the netstat -rn command:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

chort 12-18-2003 03:38 PM

It's still the same problem, you haven't assigned an IP to eth0. First you need to find out what the "LAN IPs" are for your router. Actually, do you even have a router, or is this plugged directly into a cable modem or DSL modem? If it's plugged into a modem, then you need to set the interface to DHCP. I'm not familiar with doing this since I always have statics.

Tnichols 12-18-2003 04:26 PM

when I select DHCP, i get nothing... I can not even ping my self...

When I assign a IP address, at least I can ping that address, but nothing else...

Yes, there are routers...

Tnichols 12-18-2003 04:57 PM

eth0 Link encap:Ethernet HWaddr 00:60:94:69:4B:27
inet addr:10.5.46.202 Bcast:10.5.47.255 Mask:255.255.254.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:5 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:504 (504.0 b)
Interrupt:10 Base address:0xe000

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:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2136 (2.0 Kb) TX bytes:2136 (2.0 Kb)

----------------------------------------------------

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.5.46.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.5.46.1 0.0.0.0 UG 0 0 0 eth0

chort 12-18-2003 05:15 PM

But how are you picking the IP??? If you're directly connected to Internet through your cable modem then you will need to get an IP from DHCP (unless your ISP gives you a static IP, but that's very rare). You didn't answer any of the questions that I asked above. No one is going to be able to help you if you can't describe how your network is setup.

Tnichols 12-18-2003 05:34 PM

The network is a very large network, with thousands of Windows PC's... Addresses are dynamicly assigned using DHCP. I used the same IP address as my windows pc and just pulled the lan cable from one to the other. So only one machine is hooked up at a time. I can see from my working windows PC that the subnet mask is 255.255.254.0 and the default gateway is 10.5.46.1 so I used them... I can at least ping my own machine, but nothing else.

cetialphav 12-18-2003 09:48 PM

I'm beginning to suspect either hardware or the ethernet drivers. There are two things in the ifconfig output that concern me. One is the overruns and the other is that there are 0 bytes received. On a large network like yours you should constantly see traffic; I certainly do at work, and that is just the various broadcast traffic.

It could also be the cable. Not that it is bad, because it works on the other machine. But I've seen times where a particular cable didn't seat properly in a particular network card. It will feel okay, but that combination just won't work.

Just curious, what ethernet chipset is used on that machine?

Do you see any errors in /var/log/messages related to this? (On that note, you can increase kernel logging by adding a line like this:

kern.* /var/log/kernel

to the /etc/syslog.conf file.)

chort 12-19-2003 01:27 AM

OK, now we are getting some where. It sounds like you aren't finding MAC addresses via ARP. Do you have another box on the local network (i.e. the same subnet as you) that you can ping, i.e. you're sure that you know the right IP and you're sure there isn't filtering? If you try to ping that box and you cannot, and you immediately do an
$ arp -a
if the IP you're trying to ping doesn't have a MAC addr in the arp output, then there are problems.

I agree with cetialphav, it sounds like you very well might have a bad NIC. Have you tried using another NIC? The MAC adress lookup I just did indicates the hardware vendor is IBM. Have you tried an Intel or a 3COM? Those tend to work very well.

Tnichols 12-19-2003 08:55 AM

Thanks Guys! Maybe it is hardware. I just used a computer that was siting around for months. My next steps are to partion the hard drive and install Windows 95/98 in the other partion. That way I can test the NIC card and cable, etc. That way we will elimiate the hardware as a problem. I will also see what IP address gets assigned by DHCP.

Also the NIC card is built into the mother board and it is a IBM PC. I could try to disable the built in card and install a different card if it comes to that, but lets see what the Windows 95/98 test shows.

Thanks for your help.

Tnichols 12-19-2003 09:02 AM

I will check the chip set, Is that on the card? or do i look in the bios? Speaking of Bios, I guess I will get the latest updates from IBM while I am at it. I will also check for more log messages...

chort 12-19-2003 12:00 PM

Chipset for NICs is usually a small, flat, black patch on top of the card. It usually has a number on it, such as 82559 (which is an Intel 82559). If it's integrated into the mother board, there should be (but maybe not) something similar to the ethernet port in the back.

You don't really need to even disable it to put another card in, just keep in mind the new card will probably be assigned eth1 (not eth0). It may be more simple to disable the on-board NIC, though in case some applications expect to use eth0.


All times are GMT -5. The time now is 07:56 PM.