|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
dhcpd not working as I would expect
Code:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33204 groups: lo inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:50:da:b2:37:1c groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::250:daff:feb2:371c%xl0 prefixlen 64 scopeid 0x1 inet x.x.x.x netmask 0xffffffe0 broadcast x.x.x.x xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:01:03:de:32:84 description: Wired media: Ethernet 100baseTX full-duplex (100baseTX half-duplex) status: active inet 10.100.0.226 netmask 0xffff0000 broadcast 10.100.255.255 inet6 fe80::201:3ff:fede:3284%xl1 prefixlen 64 scopeid 0x2 xl2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:50:da:5b:71:54 description: Wireless media: Ethernet 100baseTX full-duplex (100baseTX half-duplex) status: active inet 172.16.0.226 netmask 0xfffff000 broadcast 172.16.15.255 inet6 fe80::250:daff:fe5b:7154%xl2 prefixlen 64 scopeid 0x3 vr0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:11:2f:7b:c1:41 media: Ethernet autoselect (none) status: no carrier enc0: flags=0<> mtu 1536 pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33204 groups: pflog Code:
# grep -v "#" /etc/dhcpd.conf authoritative; shared-network WIRED { default-lease-time 86400; option domain-name "freak.dub"; option nis-domain "freak.dub"; option domain-name-servers 172.16.0.226, x.x.x.2, x.x.x.3, x.x.x.20, x.x.x.25, x.x..30; option broadcast-address 172.16.0.255; option routers 172.16.0.226; option ntp-servers 172.16.0.226; subnet 172.16.0.0 netmask 255.255.255.0 { range 172.16.0.25 172.16.0.35; } host vdubmac { hardware ethernet 00:25:00:4d:24:df; fixed-address 172.16.0.222; } } shared-network WIRELESS { option domain-name "wifi.freak.dub"; option domain-name-servers 172.16.0.226, x.x.x.2, x.x.x.3, x.x.x.20, x.x.x.25, x.x.x.30; subnet 172.16.0.0 netmask 255.255.255.0 { option routers 172.16.0.226; option domain-name-servers 172.16.0.226; option ntp-servers 172.16.0.226; range 172.16.0.25 172.16.0.35; } } Can anybody tell me why it's not handing out the WIRELESS settings to a client getting it's IP via the WIRELESS interface? oh yes... Code:
# uname -a OpenBSD zeus.freak.dub 4.4 GENERIC#1021 i386
__________________
anything done in the GUI is done more efficiently in cli Last edited by vdubjunkie; 1st July 2010 at 03:21 AM. Reason: additional useful information |
|
|||
previous version of dhcpd.conf
I'm sorry I may not have been clear. The 172.16 IPs used in the WIRED section were put that way in order to make the system work. This was how I proved that the WIRELESS IP being handed out was getting it's values from that section. Here is the previous version which I have conveniently saved as always..
Code:
# cat dhcpd.conf.orig authoritative; shared-network WIRED { default-lease-time 86400; #max-lease-time 172800; option domain-name "freak.dub"; option nis-domain "freak.dub"; option time-offset -6; #CST option domain-name-servers 10.100.0.226, x.x.x.2, x.x.x.3, x.x.x.20, x.x.x.25, x.x.x.30; option broadcast-address 10.100.0.255; option routers 10.100.0.226; option ntp-servers 10.100.0.226; subnet 10.100.0.0 netmask 255.255.255.0 { range 10.100.0.25 10.100.0.35; } host vdubmac { #next-server ns1.freak.dub; hardware ethernet 00:25:00:4d:24:df; fixed-address 10.100.0.222; } } shared-network WIRELESS { option domain-name "wifi.freak.dub"; option domain-name-servers 172.16.0.226, x.x.x.2, x.x.x.3, x.x.x.20, x.x.x.25, x.x.x.30; subnet 172.16.0.0 netmask 255.255.255.0 { option routers 172.16.0.226; option domain-name-servers 172.16.0.226; option ntp-servers 172.16.0.226; range 172.16.0.25 172.16.0.35; } }
__________________
anything done in the GUI is done more efficiently in cli |
|
||||
From the dhcpd.conf(5) man page:
Quote:
Last edited by jggimi; 2nd July 2010 at 06:20 PM. |
|
|||
I agree competely with that last statement of jggimi, it is highly recommended NOT to share the same subnet with ANY interface (under certain extreme situations?) especially a wireless one.
__________________
The more you learn, the more you realize how little you know .... |
|
|||
Indeed
Thanks so much. Most examples I've found use that shared-network pragma. Understanding the difference was clear and simple once you pointed me in the right direction, and naturally this has solved my problem.
__________________
anything done in the GUI is done more efficiently in cli |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
dhcpd, dhcrelay, and ipsec VPN | dontek | OpenBSD General | 2 | 22nd May 2010 08:52 PM |
dhcpd, vista and wlan | hamba | FreeBSD Ports and Packages | 5 | 8th September 2009 04:34 PM |
dhcpd and dns | sputnik | OpenBSD General | 8 | 8th May 2009 02:50 PM |
dhcpd and multiple subnets | vdubjunkie | OpenBSD General | 5 | 11th March 2009 11:02 PM |
dhcpd within ezjail? | zelut | FreeBSD General | 7 | 10th February 2009 10:31 PM |