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

    DHCP in CVS update not working again…

    Scheduled Pinned Locked Moved
    DHCP and DNS
    6
    11
    4.7k
    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.
    • D
      dlawley
      last edited by

      Did an update via CVS this morning, noticed that the dhcp had been updated again… but still not working for me.. back to earlier snapshot..

      My interface page states that the link is up but dhcp is down...  when I press renew I get this send to my syslog server.. in this case I tried to renew 3x.

      Missing some config??

      Fri Dec 29 07:14:35 2006: <30>Dec 29 07:11:53 dhclient: Internet Systems Consortium DHCP Client V3.0.5rc2
      Fri Dec 29 07:14:35 2006: <30>Dec 29 07:11:53 dhclient: Copyright 2004-2006 Internet Systems Consortium.
      Fri Dec 29 07:14:35 2006: <30>Dec 29 07:11:53 dhclient: All rights reserved.
      Fri Dec 29 07:14:35 2006: <30>Dec 29 07:11:53 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
      Fri Dec 29 07:14:35 2006: <27>Dec 29 07:11:53 dhclient: Usage: dhclient [-1Ddqrv] [-i polling-interval] [-nw] [-p <port>] [-s server]
      Fri Dec 29 07:14:35 2006: <27>Dec 29 07:11:53 dhclient:                [-cf config-file] [-lf lease-file] [-pf pid-file] [-e VAR=val]
      Fri Dec 29 07:14:35 2006: <27>Dec 29 07:11:53 dhclient:                [-sf script-file] [interface]
      Fri Dec 29 07:14:44 2006: <30>Dec 29 07:12:01 dhclient: Internet Systems Consortium DHCP Client V3.0.5rc2
      Fri Dec 29 07:14:44 2006: <30>Dec 29 07:12:01 dhclient: Copyright 2004-2006 Internet Systems Consortium.
      Fri Dec 29 07:14:44 2006: <30>Dec 29 07:12:01 dhclient: All rights reserved.
      Fri Dec 29 07:14:44 2006: <30>Dec 29 07:12:01 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
      Fri Dec 29 07:14:44 2006: <27>Dec 29 07:12:01 dhclient: Usage: dhclient [-1Ddqrv] [-i polling-interval] [-nw] [-p <port>] [-s server]
      Fri Dec 29 07:14:44 2006: <27>Dec 29 07:12:01 dhclient:                [-cf config-file] [-lf lease-file] [-pf pid-file] [-e VAR=val]
      Fri Dec 29 07:14:44 2006: <27>Dec 29 07:12:01 dhclient:                [-sf script-file] [interface]
      Fri Dec 29 07:14:48 2006: <30>Dec 29 07:12:05 dhclient: Internet Systems Consortium DHCP Client V3.0.5rc2
      Fri Dec 29 07:14:48 2006: <30>Dec 29 07:12:05 dhclient: Copyright 2004-2006 Internet Systems Consortium.
      Fri Dec 29 07:14:48 2006: <30>Dec 29 07:12:05 dhclient: All rights reserved.
      Fri Dec 29 07:14:48 2006: <30>Dec 29 07:12:05 dhclient: For info, please visit http://www.isc.org/sw/dhcp/
      Fri Dec 29 07:14:48 2006: <27>Dec 29 07:12:05 dhclient: Usage: dhclient [-1Ddqrv] [-i polling-interval] [-nw] [-p <port>] [-s server]
      Fri Dec 29 07:14:48 2006: <27>Dec 29 07:12:05 dhclient:                [-cf config-file] [-lf lease-file] [-pf pid-file] [-e VAR=val]
      Fri Dec 29 07:14:48 2006: <27>Dec 29 07:12:05 dhclient:                [-sf script-file] [interface]

      In the 12/22 snap that I went back to this is what I got.. which works but was not sure about the send_packet error

      Fri Dec 29 07:24:43 2006: <30>Dec 29 07:22:00 dhclient: Listening on BPF/fxp0/00:b0:d0:f0:18:77
      Fri Dec 29 07:24:43 2006: <30>Dec 29 07:22:00 dhclient: Sending on  BPF/fxp0/00:b0:d0:f0:18:77
      Fri Dec 29 07:24:43 2006: <30>Dec 29 07:22:00 dhclient: Sending on  Socket/fallback
      Fri Dec 29 07:24:48 2006: <30>Dec 29 07:22:06 dhclient: DHCPREQUEST on fxp0 to 24.xx.x.xxx port 67
      Fri Dec 29 07:24:48 2006: <27>Dec 29 07:22:06 dhclient: send_packet: Network is unreachable
      Fri Dec 29 07:24:48 2006: <27>Dec 29 07:22:06 dhclient: send_packet: please consult README file regarding broadcast address.
      Fri Dec 29 07:24:48 2006: <30>Dec 29 07:22:06 dhclient: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 6
      Fri Dec 29 07:24:48 2006: <30>Dec 29 07:22:06 dhclient: DHCPOFFER from 75.xxx.xx.x
      Fri Dec 29 07:24:48 2006: <30>Dec 29 07:22:06 dhclient: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
      Fri Dec 29 07:24:48 2006: <30>Dec 29 07:22:06 dhclient: DHCPACK from 75.xxx.xx.x
      Fri Dec 29 07:24:49 2006: <30>Dec 29 07:22:06 dhclient: bound to 75.xxx.xx.xxx – renewal in 20864 seconds.

      Anything else I can send along that might help??</port></port></port>

      1 Reply Last reply Reply Quote 0
      • H
        hoba
        last edited by

        Please see: http://forum.pfsense.org/index.php/topic,2645.msg19076.html#msg19076
        Using the ISC dhclient  was a failure. It can't treat multiple dhcp enabled interfaces correctly so we had to revert back to the previous dhclient that doesn't work with few ISPs. We are trying to get help from the dhclient maintainers and will ask anybody who is having issues to work together with them on solving/debugging the issue.

        In the meantime please stand by until we get in contact with them to forward their questions to you.

        1 Reply Last reply Reply Quote 0
        • D
          dlawley
          last edited by

          Great, .. if it helps, I'm on Roadrunner in the southeast part of USA… back to 1.0.1-SNAPSHOT-12-22-2006

          1 Reply Last reply Reply Quote 0
          • R
            rsw686
            last edited by

            @dlawley:

            Great, works for me… if it helps, I'm on Roadrunner in the southeast part of USA...

            Interesting as I have COX High Speet Internet, which was previously called Roadrunner with no issues. Been running the 11-25-2006 snapshot. I'm located in Northern Virginia

            1 Reply Last reply Reply Quote 0
            • S
              sai
              last edited by

              running 1.01, I had problems getting an ip address from the isp. when I connected a Linux machine to the isps modem, it picked up an ip address immediately.
              1.01 would not get anything from the dhcp server until I turned off both the pf machine and modem for about 15 minutes.

              This isp gave me  a lot of problems like this with mono as well, which I think, also used the ISC dhclient.

              1 Reply Last reply Reply Quote 0
              • D
                dlawley
                last edited by

                Don't want to confuse where the problem starts… currently running 1.0.1-SNAPSHOT-12-22-2006

                It works fine with this one, but they are working on another version of the client side that for some reason when I update from the CVS it says link up but dhcp down..  I'll just keep this snap handy and try the new client when they have one available..

                1 Reply Last reply Reply Quote 0
                • D
                  dlawley
                  last edited by

                  Just wondering if there is any further developments, I tried a CVS update yesterday (Jan 6th).  Tried moving, reassigning interfaces. Still unable to get IP on the WAN via DHCP.  Back to 12/22 snap.

                  1 Reply Last reply Reply Quote 0
                  • S
                    sullrich
                    last edited by

                    @dlawley:

                    Just wondering if there is any further developments, I tried a CVS update yesterday (Jan 6th).  Tried moving, reassigning interfaces. Still unable to get IP on the WAN via DHCP.  Back to 12/22 snap.

                    No, we are at a dead end and now need debugging hellp from a FreeBSD developer.

                    1 Reply Last reply Reply Quote 0
                    • S
                      SatireWolf
                      last edited by

                      Is there any progress on this issue? I'm trying to use dhcp to get an IP for my Verizon FiOS setup (the actiontec router they include SUCKS BAD… ie nothing on it works right). I'm currently unable to get an IP via DHCP and have even cloned the mac of the actiontec router to no avail. Using a 2/28 snapshot.

                      1 Reply Last reply Reply Quote 0
                      • S
                        sullrich
                        last edited by

                        All known problems have been fixed except for what looks to be Telia.

                        Upgrade to a more recent snapshot.

                        1 Reply Last reply Reply Quote 0
                        • S
                          SatireWolf
                          last edited by

                          I grabbed the snapshot dated from today and will update when I get home. 04-03-07 full update.

                          If it doesn't work I'll try a full install. But normally the full update snapshots work perfectly.

                          Thanks Sullrich. I'll make a detailed post back on how to get Verizon FiOS setup without any Actiontec non-sense here as soon as I get it working.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post