Re: Fedora breaks dhcpd, RH9 doesn't?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andy,
Something that jumps out at me is that you are using two different local IP ranges on eth0.


IE: dhcpd is passing out IPs on 192.198.0.X but your LAN-side NIC is on the 10.1.1.X range. I'm not sure what this will result in, but I know its not making life easy for your LAN.

I would try changing your LAN-side NIC to 192.168.0.1, this would also fix another issue I see with your configs: the "options routers" statement in dhcpd.conf needs to match the IP address of your LAN-side NIC.

If I were you, I'd move that IP over to 192.168.0.1 then test you LAN connection without using dhcp. Assign a client workstation a static IP address (outside of your dhcp pool, but still on the same subnet, IE 192.168.0.51), default gateway: 192.168.0.1, DNS if you want to. Try to ping your fedora box's LAN-side nic from the static workstation, then try the WAN NIC on your linux box (to test your IP-Masq (assuming that's what you're doing) ). Basically, I'd get everything working without dhcp first, then add the convenience of dhcp after it's working statically.

Hope that helps,
Nejaa


On Wed, 10 Dec 2003 12:32:12 +0200, <[email protected]> wrote:

Hi

Synopsis - install RH9, dhcpd works, gives out addresses.
Install or upgrade to Fedora Core 1, dhcp no longer gives addresses. Repeatable (two RH 9 installs, 2 Fedora installs, one RH9-FC1 update from CD's)


Note: I've even tried removing FC1's dhcpd, installing RH9 'version' - still bad.
Tried "turn off kudzu" 'trick' - same.


System: Compaq 600 Deskpro, 192 meg ram. Machine used as gateway to internet/ firewall/ webserver/ dhcp server.
Network cards: Eth0 is e100 (intel) connected via pppoe /vDSL. Network set to (as per instructions 10.1.1.1)
Eth1 is using 3c59x driver. Connected to internal network (which does / does not send addresses to 2 other machines via a hub)


Same configuration files used with both RH9 and FC1.

Config files:

Here's /etc/sysconf/dhcpd:
#########################
# Command line options here
DHCPDARGS=eth1
##########################

Here's /etc/dhcpd.conf
###########################
ddns-update-style ad-hoc;
ignore client-updates;

# home net
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;
option broadcast-address 192.168.0.255;
option ip-forwarding off;
option subnet-mask 255.255.255.0;
option domain-name-servers 194.157.175.2, 194.157.175.3;
range 192.168.0.10 192.168.0.50;
default-lease-time 86400;
max-lease-time 86400;
}
#########################
and dhcpd.conf.lock:
1335

Iifcfg-eth0:
#####################
[[email protected] root]# less /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
BROADCAST=10.1.1.255
IPADDR=10.1.1.1
NETMASK=255.255.255.0
NETWORK=10.1.1.0
ONBOOT=yes

Ifcfg-eth1:
####################
DEVICE=eth1
BOOTPROTO=static
BROADCAST=192.168.0.255
IPADDR=192.168.0.1
NETMASK=255.255.255.0
NETWORK=192.168.0.0
ONBOOT=yes

I've no idea what the dhcpd.conf.lock does - no mention of it in the (lengthy) documentation...

As I say, above files are same for both installations...
Any ideas greatfully received.
-Andy



--
fedora-list mailing list
[email protected]
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list



-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/




[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux