LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Simple Networking (https://www.linuxquestions.org/questions/linux-networking-3/simple-networking-228409/)

Pen 09-08-2004 10:16 PM

Simple Networking
 
I have been thru How-to's and such and still havent found anything to fix this little hiccup. I have a XP PC and a Fedora FC2 Server Each has its own internet connection and both have dual NIC (one for WAN other for LAN)

They wont talk to each other! ping from the Linux server results in:
Destination unreachable

And of course the ever informative:
Request timed out.
From the Windows XP PC.

Trying to use a 10.0.0.1 address in the Linux server and 10.0.0.2 on the PC

What I have tried:

Disabled firewall(s)
Checked route table
added script (found here in post)
iptables -A FORWARD -s 10.0.0.0 -j ACCEPT
iptables -A FORWARD -s 10.0.0.0 -j ACCEPT

no success..
Seems simple to set a static IP and be able to ping back and forth right??
What did I miss.. please tell me its simple!

EDIT: The 2 machines are connected via 10mb hub verified LAN Cables hardware ect!

angrybeaver 09-08-2004 11:00 PM

can you post up your routing table, as returned by the 'route -n' and 'route print' commands on your linux and XP boxes? 'destination unreachable' tells me that packets for the 10.0.0.0 network are trying to head out the default gateway, not a LAN interface.

you've confirmed your netmasks are correct on both servers?


[edit]
btw, this might be handy
[/edit]

Pen 09-08-2004 11:03 PM

Here is XP Route print

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 ba b0 84 a6 ...... Realtek RTL8139 Family PCI Fast Ethernet NIC
acket Scheduler Miniport
0x3 ...00 03 47 a2 25 7a ...... Intel(R) PRO/100 VM Network Connection - Pack
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 69.242.176.1 69.242.177.186 7
10.0.0.0 255.0.0.0 10.0.0.2 10.0.0.2 1
10.0.0.2 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.0.0.2 10.0.0.2 1
69.242.176.0 255.255.248.0 69.242.177.186 69.242.177.186 7
69.242.177.186 255.255.255.255 127.0.0.1 127.0.0.1 7
69.255.255.255 255.255.255.255 69.242.177.186 69.242.177.186 7
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.0.0.2 10.0.0.2 1
224.0.0.0 240.0.0.0 69.242.177.186 69.242.177.186 7
255.255.255.255 255.255.255.255 10.0.0.2 10.0.0.2 1
255.255.255.255 255.255.255.255 69.242.177.186 69.242.177.186 1
Default Gateway: 69.242.176.1
===========================================================================
Persistent Routes:
None

Linux in a sec

Pen 09-08-2004 11:05 PM

Ok short and simple but missing info now that Im looking at it. Now where do I add the destination routes?

Linux Route Table

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
69.242.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
10.0.0.0 0.0.0.0 255.0.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 69.242.176.1 0.0.0.0 UG 0 0 0 eth0

Pen 09-09-2004 12:19 AM

ok thought to post the ifconfig result before I head off to bed for the night. Any ideas would be great!

eth0 Link encap:Ethernet HWaddr 00:10:5A:E3:A0:A7
inet addr:69.242.183.*** Bcast:69.242.183.255 Mask:255.255.248.0
inet6 addr: fe80::210:5aff:****:****/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1967211 errors:0 dropped:0 overruns:0 frame:0
TX packets:1868 errors:0 dropped:0 overruns:0 carrier:3
collisions:13 txqueuelen:1000
RX bytes:144699946 (137.9 Mb) TX bytes:268892 (262.5 Kb)
Interrupt:11 Base address:0xd400

eth1 Link encap:Ethernet HWaddr 00:60:08:A4:E0:3C
inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::260:8ff:fea4:e03c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:1 frame:0
TX packets:0 errors:8 dropped:0 overruns:14 carrier:14
collisions:0 txqueuelen:1000
RX bytes:45517 (44.4 Kb) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0xd800

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

One thing I have noticed is all connections have the inet6 IP address in there? I can access the internet via eth0 but I dont know whats up from there.

angrybeaver 09-09-2004 05:50 AM

weird problem :(

routes all look okay ...

On your linux box :

You could try installing 'tcpdump', run it against your eth1 interface
while sending some pings to 10.0.0.2.

Code:

'tcpdump -n -i eth1 icmp'
it will at least tell you if packets are leaving the right interface, and maybe some other helpful stuff (like arps or NetBIOS traffic etc).

On your windows box (with tcpdump still running), try sending pings to 10.0.0.1 and see if you can see the packets coming in on the eth1 interface on your linux box.

:shrug:

Pen 09-09-2004 08:26 PM

0 packets captured
0 packets received by filter
0 packets dropped by kernel


this is after 32 requests tried pinging 10.0.0.2

Hmm ok why isnt fedora working!

thinking about trying a different NIC I have seen a few bug reports on 3Com cards (3c90x) that might be buggin me too!?

Ill let ya know

angrybeaver 09-09-2004 09:27 PM

not sure it's anything to do with your card ...

eth1 Link encap:Ethernet HWaddr 00:60:08:A4:E0:3C
inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::260:8ff:fea4:e03c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:1 frame:0
TX packets:0 errors:8 dropped:0 overruns:14 carrier:14
collisions:0 txqueuelen:1000
RX bytes:45517 (44.4 Kb) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0xd800

plenty of RX bytes but nothing transmitted - plus a destination host unreachable message.

did you run tcpdump on your public interface while sending those pings also? something has to be returning that ICMP response - it may be your upstream router. If that's the case then there is something a little strange with your routing. You could also try a more specific route for your windows machine out the eth1 interface :

Code:

/sbin/route add -host 10.0.0.2 dev eth1
though it doesn't really solve the problem, if it works it will give you a bit more time to sort it out permanently.


All times are GMT -5. The time now is 02:50 AM.