dchp on fedora core 13 with vlan only 1 vlan working.

[bornpilot]

Greetings,
I am using FC 13 and I just set up dhcp 4.1.1-P1 and dhcp will not hand out ip address to one of my two vlans.

System:
I have a 3com 4500 set up with two vlans--vlan 10 and vlan 20. I have dhcp relay configured so that on vlan 20 clients will request dhcp from my dhcp server on vlan 10 ip of 10.0.0.10.

vlan 10 = 10.0.0.0 255.255.254.0
vlan 20 = 10.0.2.0 255.255.254.0

in my dhcp.conf file I have two subnet configured one for vlan 10 and the other for vlan 20. The config is as follows:

log-facility local5;

option domain-name-servers 10.0.1.254;

shared-network campjoy {
subnet 10.0.0.0 netmask 255.255.254.0 {
  option routers 10.0.1.253;

  # Unknown clients get this pool.
  pool {
    authoritative;
    option domain-name "campjoy.local";
#    option domain-name-servers 10.0.1.254;
    max-lease-time 300;
    range 10.0.0.50 10.0.1.249;
    allow unknown-clients;
  }
}
subnet 10.0.2.0 netmask 255.255.254.0 {
  option routers 10.0.3.253;

 pool {
  authoritative;
#  option domain-name-servers 10.0.1.254;
  option domain-name "campjoy.local";
  max-lease-time 300;
  range 10.0.2.0 10.0.3.250;
  allow unknown-clients;
 }
}
}

With this configuration clients on vlan 10 have no problem getting the correct ip address. However clients on vlan 20 get self-assigned ip address.
From the message in my dhcpd log file I get this for the client that errors out:

Mar 29 21:29:29 deacon dhcpd: DHCPDISCOVER from 00:1d:72:77:4d:e3 (kendalbridger-PC) via 10.0.3.253
Mar 29 21:29:29 deacon dhcpd: DHCPOFFER on 10.0.0.50 to 00:1d:72:77:4d:e3 (kendalbridger-PC) via 10.0.3.253

The dhcp server is plugged into a untagged vlan 10 port as well as the clients that work, the client from the error above was plugged into a untagged vlan 20 port. Tagged ports that have a pvlan of 10 work also.

From the log file it seems as if the dhcp relay works I am a bit baffled on why this is not working, any help or suggestions would be great.

Sincerely,
Tim Turner

 

[bornpilot]

It must have been the lateness of the hour. I solved this issue. In my server nic settings the gateway was typed incorrectly so it was set to a non-existent gateway.