View Full Version : Fedora 9 DHCP Server/Routing
FastGM3
2008-05-27, 02:58 PM CDT
Using Fedora 9, I have two network cards, one gets an IP from my Linksys router/switch that has DHCP enabled using 192.168.1.X subnet. The other NIC in my Fedora box serves as a DHCP server, to an audio device, using 192.168.0.x subnet.
The audio device gets an address no problem from my fedora box and from my fedora box I can web into this audio device. However I can't ping or access the 192.168.1.X subnet from the audio device.
I assume I need to create a route from the 192.168.0.X subnet to the 192.168.1.X address. Unfortunately due to my lack of experience I'm not sure what the best way to do this is, or what the proper config would be on my fedora box.
Obviously I could hook the audio device up to my Linksys box to get an address on the same subnet as my fedora box and access the fedora box that way. However do to location and cost I want the audio device hooked directly up to the Fedora box.
Any examples, suggestions or help would be gratefully appreciated.
stevea
2008-05-27, 06:06 PM CDT
You should really describe you networks rather than making everyone guess.
I *ASSUME* there are two LANs.
If you want to connect two LANs you need router funcionality.
Try system->admin->firewall (yes there is router/masquerading features ther eon F8 & F9).
Alternatively I'd think you can use a $20 switch and put everything on one LAN.
FastGM3
2008-05-27, 08:49 PM CDT
Sorry, I thought the description of my LAN's was clear. There are 2 LANS, I would like to route them using my Fedora 9 box.
one Lan uses 192.168.1.x the othe LAN is created using the Fedora 9 DHCP server it is 192.168.0.x
Fedora box gets internet access using NIC 1 connected to 192.168.1.x via my Linksys box. NIC 2 is DHCP server serving 192.168.0.x addresses. I'll try to figure out the router/masquerade in the Firewall on F9 however this is the issue I don't know how to properly configure the route entries.
I realize I could use a switch and a single network, however without going into details of why I want to use this method, I just prefer the help with my routing configuration.
Thanks for the reply, sorry for the confusion, hope I didn't add to it.
tunerX
2008-05-27, 08:58 PM CDT
Put a static route on the linksys router that points to the fedora box as the gateway for the 192.168.0.0/24 subnet.
The Audio box probably has its default route or default gateway as the fedora box so it is good.
Linux will route between them as long as ipchains allow it.
ipchains -I forward -j ACCEPT -s 192.168.1.0/24 -d 192.168.0.0/24 -b
FastGM3
2008-05-27, 09:59 PM CDT
Well my problems have exploded. I had firewall disabled, after reading stevea's post I attempted to enable masquerading. Setting up trust between both NICs on my Fedora box. After which my dhcp server stopped working, and my other NIC which had been working on the internet also stopped. I checked to make sure they were active and they were both active, So I disabled the firewall, and still no internet on one NIC and I'm not getting a dhcp address from my F9 dhcp server on the other NIC.
So I restarted the computer, after which I notice neither of my NICs come up active on startup, even though in networking configuration the boxes for each NIC are checked to make active on startup.
TurnerX when I run ipchains from the command line as root I get bad command.
So is there a way to blow out any firewall settings that may still be enabled even though the gui says firewall is disabled?
Also how can I fix the NIC's to where they come up active on startup even though GUI configuration says they should?
And how can I run the ipchains command?
IS F9 this buggy, should I revert to F8 or just shoot myself :-) heck I'd feel relief just to go back to having internet and dhcp working again. The routing issue at this point is the least of my worries.
tunerX
2008-05-27, 10:29 PM CDT
yum install firestarter
More options than the basic gnome firewall config dialog. All of your ipchains CLI entries will be GUI based.
I haven't had a problem with the nics not coming up if I use the gnome network tool.
vBulletin® v3.7.3, Copyright ©2000-2009, Jelsoft Enterprises Ltd.