Re: Debian Install help

On Sat, 20 Oct 2007 18:00:17 +0200, Andrew Sackville-West wrote:

On Sat, Oct 20, 2007 at 02:39:20PM -0000, Ed wrote:


Interesting. From the affected machine, I can NOT ping 192.168.1.1 but
from affected machine, I CAN ping other machines on my local lan. I
can

can your *other* machines ping to 192.168.1.1?

I think maybe you've got some architecture issues in your network. Maybe
you are somehow misusing an uplink port on a switch or something like
that?

not ping anything on the internet from the affected machine, but can
from any other machine on my home lan. The output of 'route' looks
essentially the same on the affected machine as it does on working

essentially the same means different, so how about providing us a
working and non working route?

machines. So, I think it is definietely some kind of problem with my
router/old machine. (This old machine 'used' to work with win95 and
also redhad 7.0 through the same router and dsl modem and same network
card years ago.)

what are you using for a router? maybe you've somehow cnofigured a
firewall such that this machine is not allowed out? Is your whole lan on
dhcp? if so, are any of the "statically" defined? is your
router/firewall limiting which parts of the address range are allowed
out? do you have separate dhcp ranges with different rules? can you try
giving the install machine a fixed ip for the install process? can you
plug the machine directly into the router just for the install and if so
does that help? (that would have the effect of removing all other
variables and help pinpoint the error). Maybe you've got a borked dhcp
system and its assigning the same address to multiple machines? etc etc
etc

there are many possible causes or work around for this issue. Hopefully,
I've spurred you to find something


A

Hi Andrew,
You ask great questions - THANKS
Here are some answers.

On the machine that does NOT reach the Internet, here is the output from
route command.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 * 255.255.255.0 U 0 0 0
eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0
eth0

Here is the output from ifconfig command.

eth0 Link encap:Ethernet HWaddr 00:20:78:1E:66:90
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:96 errors:0 dropped:0 overruns:0 frame:0
TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10462 (10.2 KiB) TX bytes:5752 (5.6 KiB)
Interrupt:10 Base address:0x6200

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:45 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4352 (4.2 KiB) TX bytes:4352 (4.2 KiB)

On a machine that DOES work, here is the output from route command.

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 * 255.255.255.0 U 0 0 0
eth0
169.254.0.0 * 255.255.0.0 U 0 0 0
eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0
eth0

And on machine that DOES work, here is output from ifcongig

eth0 Link encap:Ethernet HWaddr 00:E0:18:24:89:1A
inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:18ff:fe24:891a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1158648 errors:1 dropped:0 overruns:0 frame:0
TX packets:729749 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1555494197 (1.4 GiB) TX bytes:69461364 (66.2 MiB)
Interrupt:5 Base address:0x6000

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:2454 errors:0 dropped:0 overruns:0 frame:0
TX packets:2454 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9376692 (8.9 MiB) TX bytes:9376692 (8.9 MiB)

From the bad machine, I can ping the good machine and vice versa. From
the good machine, I can ping the router at 192.168.1.1 but from the bad
machine, I can NOT ping the router - I get Destination Unreachable.

From the good maching, I can ping linux.csua.berkeley.edu which is at
169.229.49.36, but from the bad machine, I can not ping 169.229.49.36,
again getting Destination Host Unreachable.

All my machines are running DHCP - some are laptops running windows, and
some are desktops running linux fedora.

I do not know the significance of the one additional line in the route
output from the good machine, or how to add such a line to the bad
machine.

Thanks again for sticking with me on this so far. I think we/you are
close to a solution.

Ed


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: Simple Route Question
    ... router in its default 192.168.1.1 address from my workstation. ... you now have a route from this host *to* the ... router, via eth0. ... that the *only* DHCP server on that LAN segment is that ...
    (comp.os.linux.networking)
  • Re: traceroute & ping
    ... If you ping support -R [Record Route] you can see what interfaces ... the packets are returning on. ... But I'd be concernced about your router at this point since ...
    (comp.unix.sco.misc)
  • Re: Network connection
    ... Can you ping or access anything on the local LAN such ... > Can ping router & other PC in Windows. ... > current lease for eth0: ... of 1 configured routes for interface eth0 up ...
    (uk.comp.os.linux)
  • Re: Newbie - access internet via LAN and router
    ... >I have a home LAN with a router configured to address 192.168.1.1. ... >Linux PC is set to the fixed IP address of 192.168.1.55. ... >successfully ping the router from the Linux PC. ... If theres no default route, ...
    (uk.comp.os.linux)
  • Re: Ip Public Configuration
    ... your DSL router and you can't set up a web server unless you can manage to ... configure port forwarding on the router. ... at 172.30.40.121 is expected to have a route for 202.130.5.8, ... this could be a problem if the ping is ...
    (microsoft.public.windows.server.dns)