<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[PfSense 2.4.2 - Config override]]></title><description><![CDATA[<p dir="auto">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</p>
<p dir="auto">I see an error in the syslog showing</p>
<p dir="auto">rc.bootup:Error:cannot open cf/conf/Orange_ipv4.conf in DHCP_Config_File_Override() for reading</p>
<p dir="auto">I use the conf override to handle special parms for ORANGE FTTH so cant upgrade to 2.4.2 at the minute</p>
<p dir="auto">Apologies if I'm suddenly making a school boy error but as I say its working at 2.4.0 RC version</p>
<p dir="auto">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</p>
]]></description><link>https://forum.netgate.com/topic/121788/pfsense-2-4-2-config-override</link><generator>RSS for Node</generator><lastBuildDate>Sun, 12 Apr 2026 23:39:32 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/121788.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 21 Oct 2017 19:05:30 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to PfSense 2.4.2 - Config override on Mon, 23 Oct 2017 10:21:50 GMT]]></title><description><![CDATA[<p dir="auto">@nivek1612:</p>
<blockquote>
<p dir="auto">At 2.4.0 and earlier a vlan of 832 for example defined on interface igb0<br />
Resulted in an interface name of igb0_vlan832</p>
<p dir="auto">Now it a 2.4.1 and later pfSense creates igb0.832</p>
<p dir="auto">Caused me an additional bit of head scratching</p>
</blockquote>
<p dir="auto">Reading the changelog: https://doc.pfsense.org/index.php/2.4.1_New_Features_and_Changes helps in such cases.</p>
<blockquote>
<p dir="auto">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.</p>
</blockquote>
]]></description><link>https://forum.netgate.com/post/729914</link><guid isPermaLink="true">https://forum.netgate.com/post/729914</guid><dc:creator><![CDATA[Grimson]]></dc:creator><pubDate>Mon, 23 Oct 2017 10:21:50 GMT</pubDate></item><item><title><![CDATA[Reply to PfSense 2.4.2 - Config override on Sun, 22 Oct 2017 22:09:31 GMT]]></title><description><![CDATA[<p dir="auto">Well I did a fresh install and problem has gone</p>
<p dir="auto">Note to anyone using VLANs which is what I’m using</p>
<p dir="auto">At 2.4.0 and earlier a vlan of 832 for example defined on interface igb0<br />
Resulted in an interface name of igb0_vlan832</p>
<p dir="auto">Now it a 2.4.1 and later pfSense creates igb0.832</p>
<p dir="auto">Caused me an additional bit of head scratching</p>
<p dir="auto">https://github.com/pfsense/pfsense/commit/12bcf7e933d626c7b4ba5178b10dc6e463069f39</p>
]]></description><link>https://forum.netgate.com/post/729821</link><guid isPermaLink="true">https://forum.netgate.com/post/729821</guid><dc:creator><![CDATA[[[global:guest]]]]></dc:creator><pubDate>Sun, 22 Oct 2017 22:09:31 GMT</pubDate></item></channel></rss>