No gateway and DNS via DHCP, only IP-Address gets delivered



  • Hi there,

    It is the first time I am experimenting with pfSense.

    I have one thing I do not understand and I cannot solve after various tries.

    The DHCP server on the LAN interface should provide IP addresses, gateway, DNS, etc. But the only one client in the LAN only gets an IP address. I cannot make pfSense setting also the gateway and DNS servers via DHCP. The client is a Debian 6, fresh install.

    Can anyone give me a hint, what I am doing wrong?

    Thank you very much.



  • @Gary:

    Can anyone give me a hint, what I am doing wrong?

    Not yet. I have a number of Ubuntu systems that successfully get DNS and gateway from pfSense through DHCP. On pfSense I have DNS forwarder enabled and DHCP clients receive the IP address of their interface on pfSense as the DNS and gateway.

    @Gary:

    The DHCP server on the LAN interface should provide IP addresses, gateway, DNS, etc. But the only one client in the LAN only gets an IP address.

    Have you determined (perhaps by packet capture) that pfSense DHCP doesn't send gateway and DNS?

    Perhaps the LAN client ignores DNS and gateway in DHCP. Maybe you have DNS and gateway already configured on the client and the client consequently ignores what it is given in DHCP.

    What does the client system think is the DNS IP address? Gateway IP address? Do you recognise the IP addresses?

    Does the client get its IP address from pfSense? Do you see the DHCP request in the pfSense log (Status -> System Logs, click on DHCP tab)?

    What version of pfSense are you using?

    Do you have a firewall rule blocking DHCP on the pfSense LAN interface?



  • @wallabybob:

    @Gary:

    The DHCP server on the LAN interface should provide IP addresses, gateway, DNS, etc. But the only one client in the LAN only gets an IP address.

    Have you determined (perhaps by packet capture) that pfSense DHCP doesn't send gateway and DNS?

    No, not yet. I will do this next.

    Perhaps the LAN client ignores DNS and gateway in DHCP. Maybe you have DNS and gateway already configured on the client and the client consequently ignores what it is given in DHCP.

    I have not configured DNS or gateway manually static on the client. But maybe there is still a reason the client ignores this information provided by pfSense.

    What does the client system think is the DNS IP address? Gateway IP address? Do you recognise the IP addresses?

    The client has no DNS ip addresses or gateway IP. The client is blind and deaf so far.

    Does the client get its IP address from pfSense? Do you see the DHCP request in the pfSense log (Status -> System Logs, click on DHCP tab)?

    Yes, the client gets it IP address from pfSense, i configured a static one via MAC match.

    What version of pfSense are you using?

    2.0.1 amd64

    Do you have a firewall rule blocking DHCP on the pfSense LAN interface?

    I have no firewall rules created yet.



  • Here is a syslog extract from one of my Ubuntu 12.04 systems showing dhclient reporting what it received from the pfSense DHCP server on 192.168.51.211:

    Jul 30 16:25:25 kogan NetworkManager[831]: <info>Activation (wlan4) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Jul 30 16:25:25 kogan NetworkManager[831]: <info>dhclient started with pid 20015
    Jul 30 16:25:25 kogan NetworkManager[831]: <info>Activation (wlan4) Beginning IP6 addrconf.
    Jul 30 16:25:26 kogan NetworkManager[831]: <info>Activation (wlan4) Stage 3 of 5 (IP Configure Start) complete.
    Jul 30 16:25:26 kogan dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R4
    Jul 30 16:25:26 kogan dhclient: Copyright 2004-2011 Internet Systems Consortium.
    Jul 30 16:25:26 kogan dhclient: All rights reserved.
    Jul 30 16:25:26 kogan dhclient: For info, please visit https://www.isc.org/software/dhcp/
    Jul 30 16:25:26 kogan dhclient:
    Jul 30 16:25:26 kogan NetworkManager[831]: <info>(wlan4): DHCPv4 state changed nbi -> preinit
    Jul 30 16:25:26 kogan dhclient: Listening on LPF/wlan4/00:a1:b0:64:3b:83
    Jul 30 16:25:26 kogan dhclient: Sending on  LPF/wlan4/00:a1:b0:64:3b:83
    Jul 30 16:25:26 kogan dhclient: Sending on  Socket/fallback
    Jul 30 16:25:26 kogan dhclient: DHCPDISCOVER on wlan4 to 255.255.255.255 port 67 interval 3
    Jul 30 16:25:27 kogan dhclient: DHCPREQUEST of 192.168.51.217 on wlan4 to 255.255.255.255 port 67
    Jul 30 16:25:27 kogan dhclient: DHCPOFFER of 192.168.51.217 from 192.168.51.211
    Jul 30 16:25:27 kogan avahi-daemon[740]: Joining mDNS multicast group on interface wlan4.IPv6 with address fe80::2a1:b0ff:fe64:3b83.
    Jul 30 16:25:27 kogan avahi-daemon[740]: New relevant interface wlan4.IPv6 for mDNS.
    Jul 30 16:25:27 kogan avahi-daemon[740]: Registering new address record for fe80::2a1:b0ff:fe64:3b83 on wlan4.*.
    Jul 30 16:25:27 kogan dhclient: DHCPACK of 192.168.51.217 from 192.168.51.211
    Jul 30 16:25:27 kogan dhclient: bound to 192.168.51.217 – renewal in 3072 seconds.
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>(wlan4): DHCPv4 state changed preinit -> bound
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>address 192.168.51.217
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>prefix 25 (255.255.255.128)
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>gateway 192.168.51.211
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>nameserver '192.168.51.211'
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>domain name 'test.example.org'
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>Activation (wlan4) Stage 5 of 5 (IPv4 Configure Commit) scheduled…
    Jul 30 16:25:27 kogan NetworkManager[831]: <info>Activation (wlan4) Stage 5 of 5 (IPv4 Commit) started…
    Jul 30 16:25:27 kogan avahi-daemon[740]: Joining mDNS multicast group on interface wlan4.IPv4 with address 192.168.51.217.
    Jul 30 16:25:27 kogan avahi-daemon[740]: New relevant interface wlan4.IPv4 for mDNS.
    Jul 30 16:25:27 kogan avahi-daemon[740]: Registering new address record for 192.168.51.217 on wlan4.IPv4.
    Jul 30 16:25:28 kogan NetworkManager[831]: <info>(wlan4): writing resolv.conf to /sbin/resolvconf
    Jul 30 16:25:28 kogan postfix/master[1343]: reload – version 2.9.1, configuration /etc/postfix
    Jul 30 16:25:28 kogan NetworkManager[831]: <info>(wlan4): device state change: ip-config -> activated (reason 'none') [70 100 0]
    Jul 30 16:25:29 kogan dnsmasq[1012]: reading /var/run/dnsmasq/resolv.conf</info></info></info></info></info></info></info></info></info></info></info></info></info></info></info>

    Is there similar output in a /var/log/syslog file on your Linux system?



  • Hey Guys,

    I really made a very, very stupid mistake :(. Seems like everything happened because I gave my client via static DHCP the same IP as the LAN interface of the pfSense machine. I just did not use my eyes nor my brain.

    Thanks for your support!


Locked