Click to See Complete Forum and Search --> : cannot ping network pc


eriksays
06-25-2004, 11:27 AM
i'm trying to setup a basic crossover network from my fedora core 1 to xp pro via crossover cable and i'm unable to ping my xp pro machine. in fact, xp believes it has an unplugged network cable.

to enable packet forwarding, in /etc/sysctl.conf , i changed this line to read:
net.ipv4.ip_forward=1

my /etc/hosts reads as:
server localhost.localdomain localhost
192.168.0.2 desktop

i configured eth1 (internal nic going to pc) to statically assign ip of 192.168.0.1, subnet 255.255.255.0, gateway blank

on the pc, is assigned to it's nic 192.168.0.2 , subnet 255.255.255.0, gateway 192.168.0.1 and the dns is the dns i found in /etc/resolve.conf

contents of ifconfig:
eth0 Link encap:Ethernet HWaddr 00:50:BF:50:A3:FE
inet addr:67.8.179.73 Bcast:255.255.255.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70495 errors:0 dropped:0 overruns:0 frame:0
TX packets:5078 errors:2 dropped:0 overruns:0 carrier:4
collisions:287 txqueuelen:1000
RX bytes:10422203 (9.9 Mb) TX bytes:925645 (903.9 Kb)
Interrupt:11 Base address:0x7000

eth1 Link encap:Ethernet HWaddr 00:30:1B:16:76:27
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:2280 (2.2 Kb)
Interrupt:5

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:3983 errors:0 dropped:0 overruns:0 frame:0
TX packets:3983 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3262405 (3.1 Mb) TX bytes:3262405 (3.1 Mb)


contents of route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
67.8.176.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 67.8.176.1 0.0.0.0 UG 0 0 0 eth0


any suggestions at this point?

thanks

happybunny
06-25-2004, 11:56 AM
couple things :

ethtool eth1

traceroute 192.168.0.2

R u sure it is a crossover cable?

bradfordgd
06-25-2004, 12:06 PM
What do you get from ipconfig in a command prompt on the PC? If the PC thinks it's unplugged and the NIC is down, you won't be able to ping it from the Linux host.

eriksays
06-26-2004, 07:22 PM
okay, that problem is fixed. funny story, it turns out "patch" cable is not the same thing as "crossover" cable. ha!

okay, new problem: everything was working great, cable modem -> fedora core 1 -> windows xp all able to get online and do their thing.

linux gets rebooted and windows can't go online?

looked at all the settings, they're the same as before.

more suggestions?

eriksays
06-26-2004, 08:06 PM
okay, new wrinkle...

I have two nics on my xp. i switched which card i was using and got my windows connection back; howver, i reboot my linux box and windows loses connectivity and is unable to get it back.

thoughts?

linnov
06-26-2004, 08:20 PM
check the routing table on the xp box its prolly using linux as the gateway

eriksays
06-26-2004, 08:29 PM
you mean the tcp/ip properties?

it's as follows:

assign ip address

ip: 192.168.0.2
subnet: 255.255.255.0
gw: 192.168.0.1

the 192.168.0.1 points to the linux nic card. i thought that was how i set it up?

linnov
06-26-2004, 08:45 PM
I'm guessing linux is not bringing up eth1 on reboot or the route is not getting set right

eriksays
06-27-2004, 12:03 AM
issue resolved.

turns out firestarter wasn't set to begin at startup