Hello
I'm running a new install of ClearOS 7.2.0 Community.
I have a really basic hostapd configuration, I'm able to join the wireless network from my laptop - but I never get a DHCP lease on wireless.
Here's what DHCP packets I see when connecting first to the LAN ethernet port, then to wireless
This suggests to me that hostapd is set up alright, but that the DHCP server isn't listening, or else isn't able to respond, on the bridge interface.
In the GUI, the DHCP server looks to be set up the same for the bridge interface br0 and the ethernet interface ens1 (all default, I didn't change anything), and /etc/dnsmasq.d/dhcp.conf is:
My hostapd.conf looks like:
/etc/sysconfig/network-scripts/ifcfg-br0 is
Thanks very much for any advice you can offer
I'm running a new install of ClearOS 7.2.0 Community.
I have a really basic hostapd configuration, I'm able to join the wireless network from my laptop - but I never get a DHCP lease on wireless.
Here's what DHCP packets I see when connecting first to the LAN ethernet port, then to wireless
[root@clarity ~]# tcpdump -i ens1 "port 67 or port 68"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens1, link-type EN10MB (Ethernet), capture size 65535 bytes
21:46:13.772854 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 44:8a:5b:40:8b:ee (oui Unknown), length 300
21:46:13.779532 IP clarity.local.lan.bootps > excess.local.lan.bootpc: BOOTP/DHCP, Reply, length 311
^C
2 packets captured
2 packets received by filter
0 packets dropped by kernel
[root@clarity ~]# tcpdump -i br0 "port 67 or port 68"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes
21:46:57.422586 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 54:27:1e:02:f8:22 (oui Unknown), length 300
21:47:00.614928 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 54:27:1e:02:f8:22 (oui Unknown), length 300
21:47:08.444625 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 54:27:1e:02:f8:22 (oui Unknown), length 300
21:47:11.031984 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 54:27:1e:02:f8:22 (oui Unknown), length 300
21:47:16.700439 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 54:27:1e:02:f8:22 (oui Unknown), length 300
^C
5 packets captured
5 packets received by filter
0 packets dropped by kernel
This suggests to me that hostapd is set up alright, but that the DHCP server isn't listening, or else isn't able to respond, on the bridge interface.
In the GUI, the DHCP server looks to be set up the same for the bridge interface br0 and the ethernet interface ens1 (all default, I didn't change anything), and /etc/dnsmasq.d/dhcp.conf is:
[dhcp-option=br0,1,255.255.255.0
dhcp-option=br0,28,192.168.8.255
dhcp-option=br0,3,192.168.8.1
dhcp-option=br0,6,192.168.8.1
dhcp-option=ens1,1,255.255.255.0
dhcp-option=ens1,28,192.168.7.255
dhcp-option=ens1,3,192.168.7.1
dhcp-option=ens1,6,192.168.7.1
dhcp-range=br0,192.168.8.100,192.168.8.254,24h
dhcp-range=ens1,192.168.7.100,192.168.7.254,24h
read-ethers
My hostapd.conf looks like:
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel
# Some usable default settings...
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
# Uncomment these for base WPA & WPA2 support with a pre-shared key
wpa=2
wpa_key_mgmt=WPA-PSK
#wpa_pairwise=TKIP
rsn_pairwise=CCMP
bridge=br0
# DO NOT FORGET TO SET A WPA PASSPHRASE!!
wpa_passphrase=(a passphrase)
# Most modern wireless drivers in the kernel need driver=nl80211
driver=nl80211
# Customize these for your local configuration...
interface=wlp0s29f7u6
hw_mode=g
channel=6
ssid=(an ssid)
/etc/sysconfig/network-scripts/ifcfg-br0 is
DEVICE="br0"
BOOTPROTO="static"
ONBOOT="yes"
TYPE="Bridge"
IPADDR="192.168.8.1"
NETMASK="255.255.255.0"
Thanks very much for any advice you can offer
In DHCP Server
Share this post:
Responses (2)
-
Accepted Answer
I guess I just had to sleep on it.
The GUI showed the bridge interface as being considered "LAN" - so I didn't consider it might not have gotten through to the firewall to do so.
I edited /etc/clearos/network.conf, adding 'br0' to the LANIF variable, restarted the firewall, and now WiFi works including DHCP. -
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »