Everyone,
I talked a small automotive shop into replacing their aging pfSense
computer with a GA-J1900N-D3V. They purchased an all-in-one unit from
mini-box.com
http://www.mini-box.com/SYS-M350-Gigabyte-J1900N-D3V-picoPSU-90-60W
http://www.gigabyte.com/products/product-page.aspx?pid=4918#ov
I got it loaded up, restored their 2.2.3 config from the old system and
took it over after work the following day. I ended up spending over an
hour trying to get that little system to pick up a DHCP address for
their Comcast router.
I finally gave up and put the old system back in.
Working on it today, I've tracked it down to pfSense not being able to
spoof their MAC address. When trying to spoof any address, I get the
below (ISC DHCP logs)
Jul 11 11:03:30 dhcpd dhcpd: DHCPDISCOVER from 00:e0:7d:c5:18:7f
(pfsense) via eth0
Jul 11 11:03:30 dhcpd dhcpd: DHCPOFFER on 192.168.145.103 to
00:e0:7d:c5:18:7f (pfsense) via eth0
Jul 11 11:03:30 dhcpd dhcpd: DHCPDISCOVER from 00:e0:7d:c5:18:7f
(pfsense) via eth0
Jul 11 11:03:30 dhcpd dhcpd: DHCPOFFER on 192.168.145.250 to
00:e0:7d:c5:18:7f (pfsense) via eth0
Jul 11 11:03:34 dhcpd dhcpd: DHCPDISCOVER from 00:e0:7d:c5:18:7f
(pfsense) via eth0
Jul 11 11:03:34 dhcpd dhcpd: DHCPOFFER on 192.168.145.103 to
00:e0:7d:c5:18:7f (pfsense) via eth0
Jul 11 11:03:34 dhcpd dhcpd: DHCPDISCOVER from 00:e0:7d:c5:18:7f
(pfsense) via eth0
And it just continues until pfsense gives up. Removing the spoofed mac
and rebooting, pfsense immediately acknowledges the address being offered.
It isn't a requirement that I spoof the address, but thought I'd post
this to see if maybe I should post a bug report. I've also tried
pfsense nightly 2.2.4 build with the same results.
Doug
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
