sounds more like DNS issue but as a longshot you might try setting the offending interface from "auto-negotiate" to "no preference".

If you don't see any leases then they didn't get it from pfsense - you have different dhcp server running on the network?  Are the boxes static? Any lease that dhcp server on pfsense hands out would be in the lease table..  Might not currently be active when you look at it - but it would have to be there if given out. did you click the show all configured leases? at the bottom? You should see something like this then. [image: leases.png] [image: leases.png_thumb]

@jimp: The online indicator only tells you if that MAC address is in the firewall's ARP table. It 100% accurate to tell you if a system is actually turned on and using the IP locally. Ah, ok, that explains it.  The secondary system wouldn't see the other boxes unless the first system failed and all the CARP addresses moved over. How about the issue with the hostnames?

I assume this is all about kids?

Success! We detected your IP address as 198.81.129.107 and did not find an open DNS resolver running. That one is good too (-:

Dpends on how willing you are to hunt a little and if willing to wait a week or so. You can't have this one  ;) http://www.ebay.com/itm/171089132544?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649 You can have this one if you hurry http://www.ebay.com/itm/NetGear-GS108E-8-Ports-Switch-/121177951702?pt=US_Network_Switches&hash=item1c36c4cdd6 VLAN support for traffic separation Quality of Service (QoS) prioritizes traffic Auto denial-of-service (DoS) prevention Network monitoring and bandwidth control Troubleshoot connection issues via cable test This enhanced switch can only be configured with a PC. The configuration is not MAC compatible  (needs windows)

agree with u. Thank u very much. Its much simpler to add 3 separate entries :)

That commit has been reverted due to breaking working things, as already noted on another thread.

Most (like 99%) DHCP clients do provide a hostname. Only a few of them show up in the table once expired though. So, only a few of the hostnames provided are remembered. Not a big deal, just a strange detail.

SOLVED: Turns out the issue was on my Win2K8 R2 machine. I had placed both DHCP scopes under a superscope which is not required when using VLANs. I moved the two scopes out of the superscope and now I am obtaining the correct IP addresses from the DHCP server.

@wallabybob: @phil.davis: So I am not sure why it does not work for you. Perhaps because when pfSense WAN interface has private IP address it doesn't closely track the real public address, polling checkip.dyndns.org only once a day at 1am if I reall correctly. Good thought - I forgot to say that I edit the cron job /usr/bin/nice -n20 /etc/rc.dyndns.update so it runs/checks every 5 minutes. (Install Cron package so you can make persistent edits to cron jobs like this) That gives ~5 minute response time to changes of public IP on my ADSL front-end.

He has a crazy setup - did you get away from the 3G connection yet?  And get a real connection? Let me TV in again and will get it fixed up.  Send me the info, its a friday - hopefully pretty light at work today I should be able to find time.

Hi again, I think I have tracked down my misconfiguration. When I converted this network to VLANS the vSwitch in vmware lost it's "accept promiscuous packets" setting.  After going in and setting VLAN A interface (this is the one openvpn is assigned to) to accept promiscuous packets then the packets began to flow as I remembered before switching to this VLAN configuration. Apologies for the false alarm.

Yes? Configure two separate DHCP pools?

All fixed, thanks, there was some good tips here. I had configured the alix radio to have a clone interface and I left that disabled. problem was that the firewall still blocked that interface. You must either fully config with IP, DHCP, firewall rules etc or completely remove the clone. The randomness must have been the clone grabbing the packets with sometimes the main WIFI getting them also had to add a firewall rule to allow UDP 68/67 from 0000 to 255.255.255.255, strange as I didn't need to do that on the LAN. I don't think this is the original posters problem, problem sounded the same but in the end mine was specific to wifi, not the second interface

You'd best do this on a dedicated Linux or Windows server, assuming the DHCP relay functionality works fine.

What do you mean by "unable"? If it's anything like Workstation, you just choose the physical adapter and a VMnet to bridge in the standalone network configuration tool.