I'm having same problem. Anyone figure this out?

yes, the switches in the network are vlan capable, there are over 40 vlans in the network i do believe.

Hello everyone,

Any news on this? Anyone can provide more information?

Thank you

There is no package for bind, so there would be no GUI to manage it.

You could install the FreeBSD package for bind and manage it via ssh if you really must have bind. Check the doc wiki linked in my sig, it has instructions for adding freebsd packages.

I figured out how to do this.  I will be posting something to the wiki once I get it documented.

Ah! Thanks.  :)
That should be no problem then.

Steve

It certainly looks as if your DHCP server on the LAN side is providing the address to your WAN interface but you haven't provided any conclusive evidence. So, to exclude other possibilities, please provide the output of the shell command```
ipconfig -a

Not many details :(  I infer from the vlan refs that there is a single NIC going to a vlan-capable switch?  If so, it almost seems like the switch is screwing up and leaking traffic across the vlan boundaries (at least the broadcasts).

What version of fSense are you using?

Issue 1: Have you checked the pfSense DHCP log. Perhaps dhcpd has died and not been restarted. Are there any other clues to the reported bad name in /var/dhcpd/var/db/dhcpd.leases?

Issue 2: Does this happen before the DHCP lease renewal problem or after?

What happens when you ping or traceroute your preferred name server (by IP address) from the pfSense shell?

Does pfSense have exclusive use of the interface its using as its WAN interface or does the VM host get involved? If the latter, what does the VM host do with attempts to access your preferred name server?

And is there a good reason not to be working with pfSense 1.2.3?

I opened a ticket for adding more options, but I'm not sure it's something that will get into 2.0 or if it will have to wait for 2.1:

http://redmine.pfsense.org/issues/663

slaps self
I have no clue how I overlooked that. I checked the packages for anything at all that would be useful.
Thanks!

@wallabybob:

Is there a DHCP client log on the phone?

Is there a "tcpdump" like utility on the phone?

I'll do some research and find out. It is running android so I'm thinking I should be able to access that info.

You can just give one of them a different name (add on a "2" or "-b" or something) and it should be fine.

Are these in two different subnets? If they're both on the same subnet, you probably don't really want two NICs on the same subnet with two different IPs.

Got it!

The problem had nothing to do with the pfSense box. Packets are whizzing around inside just fine.

With the LAN on one subnet (with SIP server) and the WLAN on another subnet, the problem is that the SIP registration ACK doesn't know how to get back to the WLAN wifi phone. A static route has to be added to the routing table on the SIP server box so that it knows the WLAN subnet can be found by going into the pfSense box through the LAN interface address.

When the LAN and WLAN were bridged, no additional SIP server route was needed.

It also helps to diagnose the problem with a Wireshark on the server box and not on the (LAN switch connected) browser box.

Thanks for your encouragement.

Bob G

You can set any option you want in 2.0 via the numbered options, so this is already solved there. There won't be any more updates to the 1.2.x line so if you want that option, you can either upgrade to 2.0 (not recommended for production environments yet) or or look at the relevant code in 2.0 and try to backport it to 1.2.x (might be feasible if you're familiar with PHP).

Anyone?

On the DHCP server settings, there is a checkbox for setting dynamic DNS updates. I believe you also need to fill in your DNS server in the DNS server field in the same DHCP server settings also, and then it will try to update that one.

I haven't tried this myself, but that seems to be the purpose of the setting.