Linux Router/Firewall - Linux Client problem

I have been running a Linux Firewall/Router (192.168.1.1) for my WinXP
computer for a while now and decided to
change the client(192.168.1.4) to linux as well (mandrake). The strange
thing is that I'm not able to connect
Linux->Linux now. I get no ping reply from ether client to router or the
other way around. Tcpdump shows some arp traffic though. Both computers can
ping their own ip and loopback without problems.
Any pointers?

Fry wrote:

> Linux->Linux now. I get no ping reply from ether client to router or the
> other way around. Tcpdump shows some arp traffic though. Both computers can
> ping their own ip and loopback without problems.

Is there any ARP originating at the linux client when you try to ping it?
What do the routing tables look like?

> Any pointers?

Misconfigured NIC, bad routing tables?

-Timo

--
Timo Voipio | Helsinki, Finland | ICBM at: 60 11.800 N 024 52.760 E
GeekCode ver 3: GU>CC d s-: a--- C++ UL(+)$>+++$ P+>+++ L++(+) E- W++ N++
o? K? w O M- V- PS PE Y+ PGP+ t 5++ X R tv- b++(++++) DI+ D G e- h! r !y
Remove +newsharvested to e-mail me | Poista +newsharvested jos meilaat

> Is there any ARP originating at the linux client when you try to ping it?
> What do the routing tables look like?

No arp then.
The routing tables seem fine, they are a little hard to cut and paste since
i dual boot the client to win now.


> Misconfigured NIC, bad routing tables?

The NIC holds the ip fine, i tried to take it down and ifconfig it again
with assigned ip/nemask, checked the routing too. But now I'm stuck.

On Wed, 3 Sep 2003 20:56:51 +0200, Fry wrote:
>
>> Is there any ARP originating at the linux client when you try to ping it?
>> What do the routing tables look like?
>
> No arp then.
> The routing tables seem fine, they are a little hard to cut and paste since
> i dual boot the client to win now.


FYI
route -n > a.txt
mformat a: <--- format dos floppy diskette
mcopy a.txt a: <---- to place text on floppy

IFCONFIG
eth0 Link encap:Ethernet HWaddr 00:60:08:15:83:87
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:2 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:420 (420.0 b)
Interrupt:3 Base address:0xef00

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


TCPDUMP:
21:07:43.609521 arp who-has 192.168.1.1 tell Poo (Poo=client hostname)
21:07:44.601517 arp who-has 192.168.1.1 tell Poo
21:07:45.601511 arp who-has 192.168.1.1 tell Poo
21:07:46.631582 arp who-has 192.168.1.1 tell Poo
21:07:47.631515 arp who-has 192.168.1.1 tell Poo
21:07:48.631515 arp who-has 192.168.1.1 tell Poo

ROUTE
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
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

Isn't interrupt 3 usually used for the first serial port?


"Fry" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> IFCONFIG
> eth0 Link encap:Ethernet HWaddr 00:60:08:15:83:87
> inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7 errors:2 dropped:0 overruns:0 carrier:2
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:420 (420.0 b)
> Interrupt:3 Base address:0xef00
>
> 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:171 errors:0 dropped:0 overruns:0 frame:0
> TX packets:171 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:75190 (73.4 Kb) TX bytes:75190 (73.4 Kb)
>
>
> TCPDUMP:
> 21:07:43.609521 arp who-has 192.168.1.1 tell Poo (Poo=client hostname)
> 21:07:44.601517 arp who-has 192.168.1.1 tell Poo
> 21:07:45.601511 arp who-has 192.168.1.1 tell Poo
> 21:07:46.631582 arp who-has 192.168.1.1 tell Poo
> 21:07:47.631515 arp who-has 192.168.1.1 tell Poo
> 21:07:48.631515 arp who-has 192.168.1.1 tell Poo
>
> ROUTE
> 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
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
>
>
>
>

IRQ 3 is used for the eth card in XP as well.

Fry

"Michael Hart" <mixstat-(E-Mail Removed)> wrote in message
news:l3u5b.81350$(E-Mail Removed)...
> Isn't interrupt 3 usually used for the first serial port?
>
>
> "Fry" <(E-Mail Removed)> wrote in message
> news(E-Mail Removed)...
> > IFCONFIG
> > eth0 Link encap:Ethernet HWaddr 00:60:08:15:83:87
> > inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:7 errors:2 dropped:0 overruns:0 carrier:2
> > collisions:0 txqueuelen:100
> > RX bytes:0 (0.0 b) TX bytes:420 (420.0 b)
> > Interrupt:3 Base address:0xef00
> >
> > 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:171 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:171 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:75190 (73.4 Kb) TX bytes:75190 (73.4 Kb)
> >
> >
> > TCPDUMP:
> > 21:07:43.609521 arp who-has 192.168.1.1 tell Poo (Poo=client hostname)
> > 21:07:44.601517 arp who-has 192.168.1.1 tell Poo
> > 21:07:45.601511 arp who-has 192.168.1.1 tell Poo
> > 21:07:46.631582 arp who-has 192.168.1.1 tell Poo
> > 21:07:47.631515 arp who-has 192.168.1.1 tell Poo
> > 21:07:48.631515 arp who-has 192.168.1.1 tell Poo
> >
> > ROUTE
> > 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
> > 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> >
> >
> >
> >
>
>