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

    PfSense 2.4.2 - Config override

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    3 Posts 2 Posters 1.2k Views
    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.
    • ?
      Guest
      last edited by

      Since upgrading to the latest 2.4.2 snapshot from 2.4.0 RC I can no longer use a config override for dhcp on the WAN interface page

      I see an error in the syslog showing

      rc.bootup:Error:cannot open cf/conf/Orange_ipv4.conf in DHCP_Config_File_Override() for reading

      I use the conf override to handle special parms for ORANGE FTTH so cant upgrade to 2.4.2 at the minute

      Apologies if I'm suddenly making a school boy error but as I say its working at 2.4.0 RC version

      I upgraded to take advantage of the bug fix in VLAN priority tags also needed for ORANGE FTTH :-) At least that bug has a work around with a Netgear switch

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by

        Well I did a fresh install and problem has gone

        Note to anyone using VLANs which is what I’m using

        At 2.4.0 and earlier a vlan of 832 for example defined on interface igb0
        Resulted in an interface name of igb0_vlan832

        Now it a 2.4.1 and later pfSense creates igb0.832

        Caused me an additional bit of head scratching

        https://github.com/pfsense/pfsense/commit/12bcf7e933d626c7b4ba5178b10dc6e463069f39

        1 Reply Last reply Reply Quote 0
        • GrimsonG
          Grimson Banned
          last edited by

          @nivek1612:

          At 2.4.0 and earlier a vlan of 832 for example defined on interface igb0
          Resulted in an interface name of igb0_vlan832

          Now it a 2.4.1 and later pfSense creates igb0.832

          Caused me an additional bit of head scratching

          Reading the changelog: https://doc.pfsense.org/index.php/2.4.1_New_Features_and_Changes helps in such cases.

          Changed the VLAN interface names to use the 'dotted' format of FreeBSD, which is shorter and helps to keep the interface name smaller than the limit (16) This fixes the 4 digit VLAN issues when the NIC name is 6 bytes long.

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