Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    DHCP on WAN Interface - Unable to get address - no buffer space available?

    Problems Installing or Upgrading pfSense Software
    3
    4
    4.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      victorhooi
      last edited by

      Hi,

      I'm currently trying to get the WAN interface setup on pfSense 2.0.1.

      At first, I tried using bridge mode for the modem and PPPoE authentication on pfSense - that was an utter fail…lol (http://forum.pfsense.org/index.php/topic,51648.0.html).

      Next, I'm getting the modem to do the PPPoE, and running as a DHCP server.

      I then connect this to the WAN interface on pfSense, and then set that interface to DHCP.

      According to the Interface Status, the interface is up, and status is up, however, the IP address field is blank:

      And of course, I can't actually browse the internet from a computer connected to a LAN interface.

      In the logfiles, I see:

      Jul 21 18:03:05
dhclient[4006]: No DHCPOFFERS received.
Jul 21 18:03:05
dhclient[4006]: No working leases in persistent database - sleeping.
Jul 21 18:03:05
dhclient[1521]: No working leases in persistent database - sleeping.
Jul 21 18:03:05
dhclient: FAIL
Jul 21 18:03:05
dhclient: FAIL
Jul 21 18:03:06
dhclient[40866]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 1
Jul 21 18:03:06
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 1
Jul 21 18:03:06
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:06
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:06
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:06
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:07
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 1
Jul 21 18:03:07
dhclient[40866]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 1
Jul 21 18:03:07
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:07
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:07
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:07
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:08
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Jul 21 18:03:08
dhclient[40866]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Jul 21 18:03:08
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:08
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:08
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:08
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:10
dhclient[40866]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 5
Jul 21 18:03:10
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Jul 21 18:03:10
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:10
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:10
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:10
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:12
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 4
Jul 21 18:03:12
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:12
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:15
dhclient[40866]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 7
Jul 21 18:03:15
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:15
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:16
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 9
Jul 21 18:03:16
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:16
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:22
dhclient[40866]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 13
Jul 21 18:03:22
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:22
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:25
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 11
Jul 21 18:03:25
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:25
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:35
dhclient[40866]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 10
Jul 21 18:03:35
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:35
dhclient[40866]: send_packet: No buffer space available
Jul 21 18:03:36
dhclient[40890]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 15
Jul 21 18:03:36
dhclient[40890]: send_packet: No buffer space available
Jul 21 18:03:36
dhclient[40890]: send_packet: No buffer space available

      I'm not sure quite what's going on here - a quick search online didn't seem to turn up any solutions to this no buffer space available error.

      Any ideas, guys? =)

      Cheers,
      Victor

      1 Reply Last reply Reply Quote 0
      • L
        Lee Sharp
        last edited by

        How is it auto-negotiating?  Try setting it for 100mb half duplex and see if it works.

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          @victorhooi:

          In the logfiles, I see:

          Jul 21 18:03:05
dhclient[4006]: No DHCPOFFERS received

pfSense didn't receive a reply to its DHCP request. Perhaps your WAN port is broken, perhaps the cable is bad, perhaps you didn't reenable DHCP server on your modem. perhaps the modem port is broken etc etc.

If your ports have indicator lights I would check both ports indicate "good connection", verify the modem has DHCP server enabled, check the modem log to see if it saw DHCP requests etc.

I wouldn't read too much into pfSense reporting an interface "UP". On one of my pfSense boxes the PPP interface is reported as "UP" even though it is not connected to anything and so can't be "UP" in the sense of being able to exchange data.
          1 Reply Last reply Reply Quote 0
          • V
            victorhooi
            last edited by

            heya,

            The DHCP client in this case is a Billion 5200 ADSL2+ modem.

            In this case, I restarted pfSense, and it seemed to work, sort of.

            Sometimes it'd work fine.

            Otherwise, if I I started it up, and then plug in the DHCP-serving modem, the WebConfigurator would sometimes become unresponsive - and even the VGA console on the server wouldn't respond to keystrokes. Since I couldn't get in via the web interface, console, or SSH, I didn't really have a way to retrieve /var/log/system.log  ???. However, the pfSense server would still respond to pings.

            Anyhow, I've ended up trying out pfSense 2.1-BETA0, and that seems to work ok with DHCP.

            Cheers,
            Victor

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.