Opt1 with DHCP behaving strangely



  • I have installed pfSense-2.0-BETA4-20101202-0819.iso.gz twice but the problem persists.
    If I setup Opt1 to use DHCP and then connect to a network all is OK.
    Then I physically disconnect and connect to another network, different subnet, it does not get the new settings.
    GUI interfaces page, release, renew etc does not work.
    Reboot while connected to the new subnet never gets past Opt1 configuration, waits forever.
    Disconnect from new subnet and reconnect to original subnet and it will boot OK.
    The only way I have been able to change subnets is to delete the interface and recreate it while connected to the new subnet.
    Manual configuration with static ip seems to have the same problems.



  • @gazmac52:

    Manual configuration with static ip seems to have the same problems.

    Your previously described problem seems to be related to dhcp client unable to get a new IP address. Since dhcp client shouldn't be involved on an interface with a static IP I can't see how you could be having the same problem as when the interface uses dhcp client.

    @gazmac52:

    Reboot while connected to the new subnet never gets past Opt1 configuration, waits forever.

    I'm not using the same snapshot build as you are but on my system, WAN used DHCP to get IP address and startup stalled when WAN was disconnected but it gave up after a while (maybe a couple of minutes). It certainly didn't wait "forever".

    To get a better understanding of what is happening I suggest you get a packet trace on your OPT1 interface just after you connect it to another network. You might see a few attempts to get an IP address from the previously used DHCP server but then it should broadcast a DHCP request and a DHCP server (if active) should respond.

    Concurrently while the packet trace is running I suggest you check that there is a dhclient process running (shell command # ps ax | grep dhclient ). Perhaps something is causing dhclient to die. It would also be worth looking in the system log (web GUI: Status -> System Logs, click on the System tab) for relevant dhclient messages.



  • My apologies for not being more accurate. Static problems are obviously very different, I should have been more explicit.
    That is another issue that I will raise later.
    As to waiting forever, half hour or more is forever for an issue of this type. I left it trying to get dhcp service and went home.
    If I connect a computer to either network it successfully gets configured by dhcp almost instantly.
    I will investigate more on Monday as per your suggestions.
    Thanks


Log in to reply