Professional Web Applications Themes

dhclient oddness? - FreeBSD

Right, I have this weird annoying issue with my modem which I have finally got around to looking in to. Basically, it's all good and works fine (obviously, otherwise I wouldn't be here!), except when I reboot the internet computer the IP will change, the connection DOESN'T drop, but the IP does change. I have just now narrowed this down to some sort of problem with dhcp I think. The modem has a dhcpd server built in, which sends out the internet IP address to the computers network card. It seems, whenever the dhcp client, dhclient in this case, gets ...

  1. #1

    Default dhclient oddness?

    Right, I have this weird annoying issue with my modem which I have
    finally got around to looking in to. Basically, it's all good and works
    fine (obviously, otherwise I wouldn't be here!), except when I reboot
    the internet computer the IP will change, the connection DOESN'T drop,
    but the IP does change. I have just now narrowed this down to some sort
    of problem with dhcp I think.

    The modem has a dhcpd server built in, which sends out the internet IP
    address to the computers network card. It seems, whenever the dhcp
    client, dhclient in this case, gets restarted it'll get the old ip
    address (the first chunk of the quote below, before the <freeze>), natd
    will update itself, but then the connection will just stall until
    dhclient does the next DHCPREQUEST thing (47 seconds in this case?) ..
    then the modem sends back a DHCPNAK and I get a different IP address.
    Any ideas why this might be happening?


    -------------
    Apr 5 17:45:01 bone dhclient: DHCPDISCOVER on fxp1 to 255.255.255.255
    port 67 interval 6
    Apr 5 17:45:01 bone dhclient: DHCPOFFER from 192.168.0.1
    Apr 5 17:45:01 bone dhclient: DHCPREQUEST on fxp1 to 255.255.255.255
    port 67
    Apr 5 17:45:01 bone dhclient: DHCPACK from 192.168.0.1
    Apr 5 17:45:01 bone dhclient: Old IP Address (fxp1): 81.179.214.216
    Apr 5 17:45:01 bone dhclient: New IP Address (fxp1): 81.179.214.216
    Apr 5 17:45:01 bone dhclient: New Subnet Mask (fxp1): 255.255.255.0
    Apr 5 17:45:01 bone dhclient: New Broadcast Address (fxp1): 255.255.255.255
    Apr 5 17:45:01 bone dhclient: New Routers: 81.179.214.216
    Apr 5 17:45:01 bone dhclient: bound to 81.179.214.216 -- renewal in 47
    seconds.
    Apr 5 17:45:08 bone natd[432]: Aliasing to 81.179.214.216, mtu 1500 bytes

    <big pause here>

    Apr 5 17:45:48 bone dhclient: DHCPREQUEST on fxp1 to 192.168.0.1 port 67
    Apr 5 17:45:48 bone dhclient: DHCPNAK from 192.168.0.1
    Apr 5 17:45:48 bone dhclient: DHCPDISCOVER on fxp1 to 255.255.255.255
    port 67 interval 7
    Apr 5 17:45:48 bone dhclient: DHCPOFFER from 192.168.0.1
    Apr 5 17:45:48 bone dhclient: DHCPREQUEST on fxp1 to 255.255.255.255
    port 67
    Apr 5 17:45:48 bone dhclient: DHCPACK from 192.168.0.1
    Apr 5 17:45:48 bone dhclient: Old IP Address (fxp1):
    Apr 5 17:45:48 bone dhclient: New IP Address (fxp1): 81.178.94.190
    Apr 5 17:45:48 bone dhclient: New Subnet Mask (fxp1): 255.255.255.0
    Apr 5 17:45:48 bone dhclient: New Broadcast Address (fxp1): 255.255.255.255
    Apr 5 17:45:48 bone dhclient: New Routers: 81.178.94.190
    Apr 5 17:45:48 bone dhclient: bound to 81.178.94.190 -- renewal in 53
    seconds.
    Mark Guest

  2. #2

    Default Re: dhclient oddness?

    Mark Cullen <pipex.com> writes:
     

    Your "modem" is clearly the source of the problem, and it seems
    unlikely that anything on the FreeBSD side could help, aside from
    maybe forcing a lease free before starting dhclient on startup.

    I'd try looking at the configuration for that "modem" device, or
    possibly for a firmware upgrade for it.
    Lowell Guest

  3. #3

    Default Re: dhclient oddness?

    Lowell Gilbert wrote: 
    >
    >
    > Your "modem" is clearly the source of the problem, and it seems
    > unlikely that anything on the FreeBSD side could help, aside from
    > maybe forcing a lease free before starting dhclient on startup.
    >
    > I'd try looking at the configuration for that "modem" device, or
    > possibly for a firmware upgrade for it.
    >[/ref]

    Hi,

    Could you explain what's going on to me? I mean, in simplified terms,
    what exactly is causing the modem to get a new IP address when dhclient
    restarts? I have contacted them about the issue and they seem to think
    it's an O/S problem (well, it's *obviously* not an issue with their
    modem now, is it? :-P).

    How would I go about forcing a 'lease free'? Delete dhclient.leases, or
    some option somewhere that I missed?

    As for configuration, there's no config for the DHCP server and there's
    never been a firmware upgrade for it (this is the only issue I have EVER
    had with it and I expect most users don't notice it).

    Thanks
    Mark Guest

  4. #4

    Default Re: dhclient oddness?

    Mark Cullen <pipex.com> writes:
     
    > > Your "modem" is clearly the source of the problem, and it seems
    > > unlikely that anything on the FreeBSD side could help, aside from
    > > maybe forcing a lease free before starting dhclient on startup.
    > > I'd try looking at the configuration for that "modem" device, or
    > > possibly for a firmware upgrade for it.
    > >[/ref]
    >
    > Could you explain what's going on to me? I mean, in simplified terms,
    > what exactly is causing the modem to get a new IP address when
    > dhclient restarts? I have contacted them about the issue and they
    > seem to think it's an O/S problem (well, it's *obviously* not an issue
    > with their modem now, is it? :-P).[/ref]

    Okay, now I'm confused. I thought your FreeBSD machine was the one
    being issued a new address, not the modem. [And that since the
    address was being issued *by* the modem, it was making the decision
    about which address to choose. I guess that means I was assuming your
    "modem" was doing NAT. Does the modem have an address at all?
     

    I'm pretty sure that dhclient(8) has an command-line option to do it.
     

    Since you've rebooted your computer anyway, why do you care? You've
    just lost all of your connections already.
    Lowell Guest

  5. #5

    Default Re: dhclient oddness?

    Lowell Gilbert wrote: 
    >>
    >>Could you explain what's going on to me? I mean, in simplified terms,
    >>what exactly is causing the modem to get a new IP address when
    >>dhclient restarts? I have contacted them about the issue and they
    >>seem to think it's an O/S problem (well, it's *obviously* not an issue
    >>with their modem now, is it? :-P).[/ref]
    >
    >
    > Okay, now I'm confused. I thought your FreeBSD machine was the one
    > being issued a new address, not the modem. [And that since the
    > address was being issued *by* the modem, it was making the decision
    > about which address to choose. I guess that means I was assuming your
    > "modem" was doing NAT. Does the modem have an address at all?
    >
    >[/ref]

    Ooops, sorry. The FreeBSD machine does have the IP address assigned to
    it's network card. I don't quite know how it works, but they seem to
    call it 'Live IP technology'. I think maybe most people know it as 'PPP
    Half-Bridge', maybe??

    The address is issued, to the FreeBSD network card, by the modem via
    DHCP. The FreeBSD machine does the NAT and everything. As far as I am
    aware the modem actually holds the IP, so it's kind of annoying that,
    just because dhclient gets restarted, the modem decides that the IP
    address has to change. Surely, since the modem's actually doing all the
    work and holding the connection, it should be able to give me back my
    old IP address?? Shouldn't it?
     
    >
    >
    > I'm pretty sure that dhclient(8) has an command-line option to do it.
    >[/ref]

    Ok, I will have a look and give it a try!
     
    >
    >
    > Since you've rebooted your computer anyway, why do you care? You've
    > just lost all of your connections already.
    >[/ref]

    Because I would like to try and keep the same IP as long as possible :P
    I've been given admin on a game server that goes by IP address and
    cannot afford my ISPs 'static IP' options. Furthermore, they stopped
    with the 'sticky IP addresses' apparently :-(

    --
    Internet Explorer? Try FireFox at http://www.mozilla.org/products/firefox/
    Outlook Express? Try ThunderBird at
    http://www.mozilla.org/products/thunderbird/
    Mark Guest

Similar Threads

  1. Dhclient
    By Ciro La Ferrara in forum Ubuntu
    Replies: 1
    Last Post: March 18th, 02:04 PM
  2. dhclient fails after kernel recompilation
    By Igor Pesando - Dep. Th. Phys. Turin University in forum Debian
    Replies: 2
    Last Post: August 5th, 03:40 PM
  3. configuring DHCLIENT-2.2.x
    By Lars Unin in forum Debian
    Replies: 9
    Last Post: July 23rd, 12:20 AM
  4. via-rhine & dhclient
    By Shyamal Prasad in forum Debian
    Replies: 4
    Last Post: July 2nd, 04:50 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139