Upgrade to 2.4.3 no access on LAN



  • Hello! I upgraded to 2.4.3, and after the update the DHCP server on the LAN interface is not working, and if I set static ip to my pc I can't access the webgui and the internet. I have multiple VLANs and that are working, only the LAN is not working. If I change the LAN ip to another it is working normally, but before the update it had no problems.


  • Netgate Administrator

    Check the DHCP and System logs when you try to start the DHCP server, what errors is it complaining about?

    If you edit and re-save the DHCP config that isn't working does it give any errors?

    What version did you upgrade from?

    Steve



  • Now I can't check it, because I'm not there where is the firewall, but before I changed the lan ip, I logged in from one of the vlans, and on the main page next to the lan interface the ip address was n/a. Everything else worked fine. I upgraded from 2.4.1. Sorry for my english.


  • Netgate Administrator

    Ah, well DHCP won't start on an interface that doesn't have an IP.

    That looks most like a subnet conflict but I can't see any reason that would have changed between 2.4.1 and 2.4.3.
    The System logs would likely have an error though.

    Steve



  • I think I found the problem. The wan gateway by the isp is also 10.0.0.1 which was my lan ip.


  • Netgate Administrator

    Yup, that would do it. That wouldn't have changed since 2.4.1 though. I imagine there was some other coincidental change.

    Steve



  • The firewall was powered on when I set the pppoe connection, and next day when I installed the update it restarted because the update, but after I set the wan, it wasn't restarted. So it could be the problem. How can I solve it, if I want to use the 10.0.0.1 ip?


  • Netgate Administrator

    If the ISP is giving you that gateway via the PPPoE connection there is nothing you can do. You can't use a subnet containing that on your internal network.

    It's a pretty poor choice from your ISP though that IP is not that unusual. My own ISP is currently using 172.16.11.149 which is at least less common.

    Steve



  • Okay, thanks for your help!