Discussion:
isc-dhcpd refuses access?
(too old to reply)
Zaphod Beeblebrox
2018-11-16 20:37:16 UTC
Permalink
So... my home router has a trunked relationship to the home switch.

BGE0.31 is the guest network and has 172.17.31.1/24.

BGE0.221 is the home network and has 192.168.221.1/24.

Now on the switch, the "access" (untagged) VLAN is 1. This works: BGE0 is
192.168.110.1 and the switch's management is 192.168.110.253.

Recently, I've been playing with a new switch, and only wants to talk on
vlan1. I can see it's DHCP requests on the untagged port, so I modified my
isc-dhcpd configuration to include a subnet and range for 192.168.110.0/24.

Oddly, however, when restarted, dhcpd says it is listening on bge0.31 and
bge0.221, but ignores bge0. Help?
Patrick M. Hausen
2018-11-16 21:26:48 UTC
Permalink
Hi!
Post by Zaphod Beeblebrox
Oddly, however, when restarted, dhcpd says it is listening on bge0.31 and
bge0.221, but ignores bge0. Help?
Did you set „dhcpd_ifaces“ and if yes, to which value?
If not, have you tried setting it?

rc.conf …

Kind regards,
Patrick
--
punkt.de GmbH Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe ***@punkt.de http://punkt.de
AG Mannheim 108285 Gf: Juergen Egeling
Freddie Cash
2018-11-16 21:51:43 UTC
Permalink
Post by Zaphod Beeblebrox
So... my home router has a trunked relationship to the home switch.
BGE0.31 is the guest network and has 172.17.31.1/24.
BGE0.221 is the home network and has 192.168.221.1/24.
Now on the switch, the "access" (untagged) VLAN is 1. This works: BGE0 is
192.168.110.1 and the switch's management is 192.168.110.253.
Recently, I've been playing with a new switch, and only wants to talk on
vlan1. I can see it's DHCP requests on the untagged port, so I modified my
isc-dhcpd configuration to include a subnet and range for 192.168.110.0/24
.
Oddly, however, when restarted, dhcpd says it is listening on bge0.31 and
bge0.221, but ignores bge0. Help?
While FreeBSD is generally better than most at supporting hybrid interfaces
(tagged and untagged vlans on the same NIC), you really shouldn't do that.
Configure it either as an access port (untagged vlan only) or a trunk port
(tagged vlans only).

Simplest solution is to make vlan 1 tagged as well on the port that
connects to the FreeBSD box, move the IP setup to bge0.1 instead of bge0,
and configure dhcpd to listen on bge0.1 as well as the others.
--
Freddie Cash
***@gmail.com
Patrick M. Hausen
2018-11-18 20:02:32 UTC
Permalink
Hi!
Post by Freddie Cash
While FreeBSD is generally better than most at supporting hybrid interfaces
(tagged and untagged vlans on the same NIC), you really shouldn't do that.
Configure it either as an access port (untagged vlan only) or a trunk port
(tagged vlans only).
While I generally agree with you here - if your peer is of Cisco brand, there will
always be an untagged VLAN on that trunk port. You can configure which
one but you cannot get rid of it.

Patrick
--
punkt.de GmbH Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe ***@punkt.de http://punkt.de
AG Mannheim 108285 Gf: Juergen Egeling
Loading...