Network HELP...I'm Confused...

[Cr0n_J0b]

I thought this would be easy....I'm running Fedora Core 2 on my firewall box.

The bos sits between my Cablemodem and my internal lan

eth0 -- external interface 68.x.x.x to cable
eth1 -- internal interface 192.168.1.1 to 192.x network
eth2 -- internal interface 192.168.1.3, not really used right now, but I'll find something for it.

the problem:

from the linux box I can't ping any systems on the internal network and no one can ping it.

I'm planning to use it to NAT the internal network and wall it off, but I can't even move to that until i fix the network issues.

It would seem that the server isn't sending ping requests to 192.168.x.x to the right interface...

I don't really know where to start with this one.

[ghenry]

do a

/sbin/route -n

and post your results.

[Jman]

Check out the -I interface option to ping: man ping.

Any luck with eth0 to the Internet?

[ghenry]

Any results yet?

[Cr0n_J0b]

I tried reloading Core2, thinking is was somethign in the setup...no luck...here is the route table and Ifconfig. I can't figure out where the 169 network is from...192.x.x.1 and 192.x.x.3 are on the same switch and subnet....internal...eth0 is the ext If to the cable modem... Thanks in advance

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
68.231.208.0 * 255.255.252.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ip68-231-208-1. 0.0.0.0 UG 0 0 0 eth0

eth0 Link encap:Ethernet HWaddr 00:0A:E6:E9:DC:B5
inet addr:68.231.208.189 Bcast:68.231.211.255 Mask:255.255.252.0
inet6 addr: fe80::20a:e6ff:fee9:dcb5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19309 errors:0 dropped:0 overruns:0 frame:0
TX packets:549 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1701219 (1.6 Mb) TX bytes:118831 (116.0 Kb)
Interrupt:10 Base address:0xe00

eth1 Link encap:Ethernet HWaddr 00:60:97:C2:76:4E
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::260:97ff:fec2:764e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:1 carrier:1
collisions:0 txqueuelen:1000
RX bytes:32211 (31.4 Kb) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xec00

eth2 Link encap:Ethernet HWaddr 00:A0:24:D8:5D:E6
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2a0:24ff:fed8:5de6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:12 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:2 carrier:2
collisions:0 txqueuelen:1000
RX bytes:32211 (31.4 Kb) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xe800

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

[carbo18]

you don't seem to have eth1 listed in your routing... did you copy past or is this a typo?

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
68.231.208.0 * 255.255.252.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ip68-231-208-1. 0.0.0.0 UG 0 0 0 eth0

Shouldn't it be

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
68.231.208.0 * 255.255.252.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ip68-231-208-1. 0.0.0.0 UG 0 0 0 eth0

As for 169.254.0.0 it is present in my config as well, it is for dhcp.

[Cr0n_J0b]

you don't seem to have eth1 listed in your routing... did you copy past or is this a typo?

I fixed the eth1 issue...though even with eth2 on the 192.x.x.0 net I should be able to ping systems on that network...

My route table now looks like this:

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
68.231.208.0 * 255.255.252.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ip68-231-208-1. 0.0.0.0 UG 0 0 0 eth0

But I still can't ping anything on the inside...I have checked the cables and the switch...all show link and activity, but when I ping the internal net I get "destination host unreachable"

[carbo18]

I've never ran two network card on the same subnet, on the same PC... but couldn't this be your issue?

Try changing eth2 to 192.168.2.1 temporairly(if you haven't already), since you are not using it anyway... for now. And see if you still have networking issues. If you don't then you probably would need to bridge the two cards some how, since you want them on the same subnet...

Honestly I had originally thought of building something like what you are doing, but I found that buying a router was way simpler and is cheap. You can buy a DLINK 4port router for 50$Can about 30$US, which does NAT, DMZ, DHCP... Most routers run embeded Linux as well.

[crackers]

Most routers run embeded Linux as well.
Actually, Linksys routers run Linux - most others use a proprietary system.

[Cr0n_J0b]

Well, I tried removing one of the cards, so I only have the internal eth0 on the Motherboard and the 3Com card in the PCI slot. Still nothing...This cannot be that difficult...I must have overlooked something.

[Cr0n_J0b]

Well, after a good deal of troubleshooting I finally got this to work...Here is what I know..

I had two 3Com 3C905-TX cards in PCI slots 2 and 4 IRQ 10 and 11 and an onboard VIA port at IRQ10

I replaced one of the 3Com cards with a Kingston card...DEC chip and ...lo...everybody was happy again...

all I can think is that it was an ethernet conflict or the two 3com cards didn't like each other...

BTW, I have my BIOS set to plug and play aware...I assumed that Core2 would be plug aware...

Thanks for all the advise...

Some day Linux will be truely easy...I can't wait for that day to come..

[ghenry]

I had trouble with my 3c905 too. I ditched it and got an Intel e100 one.

[Cr0n_J0b]

Wow...I'm back to having trouble...This sucks...

Everything was running fine, but now, for some reason, I keep losing routes...

192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
68.231.208.0 * 255.255.252.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ip68-231-208-1. 0.0.0.0 UG 0 0 0 eth0

this is how the system looks now...

I do "route add -net 192.168.1.0 netmask 255.255.255.0 dev eth1
route del -net 192.168.1.0 netmask 255.255.255.0 dev eth2

and it looks like this...


Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
68.231.208.0 * 255.255.252.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth2
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default ip68-231-208-1. 0.0.0.0 UG 0 0 0 eth0

then I reboot and it goes back?!?!?!

If I ifdown and ifup eth1 or 2 it does the same thing...erases the others route and adds a duplicate route...

I can't stand this... :mad:

[Cr0n_J0b]

Well, I've tried everything to revive my internal net route and I still can't get anything to go...I'm about ready to reload FC2 or back rev to RH8 or FC1

[Cr0n_J0b]

This is my final reply before closing this thread...

I worked and worked, swapped cards and reinstalled and finally have all the cards working...

My only conclusion is that there is something wrong with the networking code in the latest version of FC2...I have read lots of posts and they are tend to be the same...my ethernet ports have died since I upgraded...

[ghenry]

Did you go back to FC1 then?

[Cr0n_J0b]

Nope,

I'm still on FC2 with the latest...upgraded kernel...2.6.6 something...

I think the issue is with how the drivers are managing IRQs...swaping the cards around seems to have fixed it for now