https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-12-27T15:44:44ZpfSense bugtrackerpfSense - Bug #7042: DHCP client configures wrong address in some circumstances (setfirst support missing from ifconfig)https://redmine.pfsense.org/issues/7042?journal_id=301532016-12-27T15:44:44ZJim Pingle
<ul></ul><p>Simplest way to reproduce this is to use a DNS Resolver override for "setfirst" and the firewall's domain, set to an obviously wrong address. Then all you have to do is unplug/replug the WAN cable, or reboot, and check the console menu or ifconfig output. It's easier to hit on SG-1000 for some reason, perhaps due to its lower speed.</p> pfSense - Bug #7042: DHCP client configures wrong address in some circumstances (setfirst support missing from ifconfig)https://redmine.pfsense.org/issues/7042?journal_id=301542016-12-27T16:04:13ZJim Pingle
<ul><li><strong>Assignee</strong> set to <i>Luiz Souza</i></li></ul> pfSense - Bug #7042: DHCP client configures wrong address in some circumstances (setfirst support missing from ifconfig)https://redmine.pfsense.org/issues/7042?journal_id=301952016-12-29T16:59:55ZLuiz Souzaluiz@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul> pfSense - Bug #7042: DHCP client configures wrong address in some circumstances (setfirst support missing from ifconfig)https://redmine.pfsense.org/issues/7042?journal_id=305892017-01-13T09:18:01ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Seems to be solid all-around.</p>