On Mon, 23 Nov 2015 15:44:42 -0800
Dave Warren wrote:
> > Delete all leases from Status -> DHCP leases, restart dhcp service
> > and retry ...
>
> That's not necessary and would be incorrect behaviour if it were
> happening. I just confirmed here with my pfSense
On Wed, 25 Nov 2015 07:58:38 +0100
Marco wrote:
> Thanks for the thorough answer. It seems it's not pfSense that is at
> fault, but the client itself. I'll fire up wireshark and check
> what's being transmitted to confirm.
Indeed, the correct domain is passed to the client.
On 2015-11-22 22:51, Nicola Ferrari (#554252) wrote:
Hi, marco?
Did you remove old dhcp leases on pfsense?
If you renew dhcp request on an already present client (in dhcp
leases), the client will use the old lease (and all its options), so
you'll not see your new configurations reflected.
Hi, marco?
Did you remove old dhcp leases on pfsense?
If you renew dhcp request on an already present client (in dhcp leases),
the client will use the old lease (and all its options), so you'll not
see your new configurations reflected.
Delete all leases from Status -> DHCP leases, restart
On Fri, 20 Nov 2015 13:15:58 -0500
Moshe Katz wrote:
> As far as I can tell, if you set a domain name manually in "System:
> General Setup", pfSense will ignore any domain name that comes back
> with the DHCP request.
I have set the domain name there. It seems redundant, but
On Fri, 20 Nov 2015 15:23:20 -0700
WebDawg wrote:
> Where does it appear?
E.g. on the WLAN connected hosts. The pfSense box itself has the
correct domain name.
> You can specify domain names on each interface served by the
> pfSense DHCP server...
I have set the domain name
We receive the interface network configuration on the WAN via DHCP.
This works, however somehow our ISP or the modem pushes a domain
name to the pfSense box which is undesirable.
I assume that the DHCP client requests the domain name. I have set
our domain name in
System → General Setup →
As far as I can tell, if you set a domain name manually in "System: General
Setup", pfSense will ignore any domain name that comes back with the DHCP
request.
I have not exhaustively tested that or seen it documented anywhere, but it
seems to be the case on the one of my pfSense boxes that
On Fri, Nov 20, 2015 at 2:05 AM, Marco wrote:
> We receive the interface network configuration on the WAN via DHCP.
> This works, however somehow our ISP or the modem pushes a domain
> name to the pfSense box which is undesirable.
>
> I assume that the DHCP client requests the