Re: hostapd
On Thu, Apr 04, 2024 at 11:28:41AM +0100, Patrick Welche wrote: > 10:15:22.135344 IP (tos 0x0, ttl 64, id 12912, offset 0, flags [DF], proto > TCP (6), length 60) > 192.168.100.3.60610 > 192.168.100.62.80: Flags [S], cksum 0x783f > (correct), seq 50981267, win 65535, options [mss 1460,sackOK,TS val 2022496 > ecr 0,nop,wscale 6], length 0 > I assume > > hostapd: urtwn0: interface state UNINITIALIZED->ENABLED > hostapd: urtwn0: AP-ENABLED > > rules out a monitor mode? or ? The dhcpd response was fine... dhcpd uses BPF to receive and transmit DHCP packets. So the symptoms would point to an issue in the ARP or IP layer. -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: hostapd
On Wed, Apr 03, 2024 at 08:53:47AM -, Michael van Elst wrote: > pr...@welche.eu (Patrick Welche) writes: > > >The system httpd via inetd doesn't receive a web page request from the > >device. > >tcpdump shows the device requesting it, but no response. > > If httpd wouldn't run, the request would be answered with > a TCP RST. > > If httpd does run, the request (SYN) is answered with a > TCP SYN/ACK. > > Can you say what exactly is "no response" here? I really mean nothing at all! # tcpdump -nvi urtwn0 port 80 tcpdump: listening on urtwn0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:15:20.886823 IP (tos 0x0, ttl 64, id 41996, offset 0, flags [DF], proto TCP (6), length 60) 192.168.100.3.60609 > 192.168.100.62.80: Flags [S], cksum 0x8457 (correct), seq 1628667887, win 65535, options [mss 1460,sackOK,TS val 2022371 ecr 0,nop,wscale 6], length 0 10:15:21.144835 IP (tos 0x0, ttl 64, id 12911, offset 0, flags [DF], proto TCP (6), length 60) 192.168.100.3.60610 > 192.168.100.62.80: Flags [S], cksum 0x78a3 (correct), seq 50981267, win 65535, options [mss 1460,sackOK,TS val 2022396 ecr 0,nop,wscale 6], length 0 10:15:21.887188 IP (tos 0x0, ttl 64, id 41997, offset 0, flags [DF], proto TCP (6), length 60) 192.168.100.3.60609 > 192.168.100.62.80: Flags [S], cksum 0x83f3 (correct), seq 1628667887, win 65535, options [mss 1460,sackOK,TS val 2022471 ecr 0,nop,wscale 6], length 0 10:15:22.135344 IP (tos 0x0, ttl 64, id 12912, offset 0, flags [DF], proto TCP (6), length 60) 192.168.100.3.60610 > 192.168.100.62.80: Flags [S], cksum 0x783f (correct), seq 50981267, win 65535, options [mss 1460,sackOK,TS val 2022496 ecr 0,nop,wscale 6], length 0 ... > >on the server, telnet localhost 80, GET /, works > > Did you configure (in /etc/inetd.conf) http for tcp or tcp6 ? > A 'telnet localhost 80' would see either, but a pure IPv4 client > only sees the 'tcp' one. For tcp: httpstream tcp nowait:600 _httpd /usr/libexec/httpd httpd -dnX /var/www I tried nginx with the same result. I assume hostapd: urtwn0: interface state UNINITIALIZED->ENABLED hostapd: urtwn0: AP-ENABLED rules out a monitor mode? or ? The dhcpd response was fine... Cheers, Patrick
Re: hostapd
pr...@welche.eu (Patrick Welche) writes: >The system httpd via inetd doesn't receive a web page request from the >device. >tcpdump shows the device requesting it, but no response. If httpd wouldn't run, the request would be answered with a TCP RST. If httpd does run, the request (SYN) is answered with a TCP SYN/ACK. Can you say what exactly is "no response" here? >on the server, telnet localhost 80, GET /, works Did you configure (in /etc/inetd.conf) http for tcp or tcp6 ? A 'telnet localhost 80' would see either, but a pure IPv4 client only sees the 'tcp' one. Greetings,
hostapd
Just tried hostapd for the first time yesterday, with urtwn0. I can see a device successfully authenticate via hostapd. The device successfully obtains a dhcp lease, so the connection must be working. The system httpd via inetd doesn't receive a web page request from the device. tcpdump shows the device requesting it, but no response. hostapd, dhcpd and inetd are all running on the same "server". on the server, telnet localhost 80, GET /, works, so inetd is OK routing looks OK arp sees the device npf etc is not running host.deny etc is empty / same when not using libwrap for httpd set ip.forwarding=1 just in case Any suggestions on what I am missing? Cheers, Patrick
Re: problem getting hostapd and bridging to work
Just to provide a heads up to others thinking of using the rpi model B as an access point gateway: DON'T The bottom line is that the built-in ethernet usmsc(4) on this board does not seem to support bridging - I find this utterly mindboggling so I think it's worth outlining what I did to come to this conclusion. I tried the original set up but used a Dlink DWL-6122 supported by the rum(4) driver which does hostap. I still couldn't get the bridge to pass packets and so I added a usb-ethernet adaptor cdce(4) to the bridge and hooked a laptop to it. No packets were seen to pass. To check that it wasn't duff I put the above adaptor in my amd64 desktop system, configured a bridge and added it and the re(4) interface (which connects to the router). Everything just worked as expected... I then tested the Dlink usb-wifi dongle in the desktop, adding that to the bridge rather than to ethernet dongle and configured hostapd. It worked OK and I could connect over wireless to the 'new' access point with a mobile phone. Subsequent attempts using the Dlink wifi dongle with the rpi B produced a load of error messages so I wonder if the usb hardware is flaky. If I get a chance next month I will try with another rpi model B to decide one way or the other, but for now would not recommend them... Dave
Re: problem getting hostapd and bridging to work
On Tue, 2023-07-18 at 21:08 -0500, David Young wrote: > On Tue, Jul 18, 2023 at 06:56:43PM +0100, Dave Tyson wrote: > > /etc/ifconfig.run0 > > apbridge > > up > > run(4) may not support `hostap` mode? > > David > Thanks for the heads up. Yes the run(4) doesn't support hostap mode so that explains the issue. The DWL-6122 supported by rum(4) does support hostap mode but the man page suggests its use is discouraged. However a openbsd user says it works fine - so I will give it a go. Dave
Re: problem getting hostapd and bridging to work
On Tue, Jul 18, 2023 at 06:56:43PM +0100, Dave Tyson wrote: > /etc/ifconfig.run0 > apbridge > up run(4) may not support `hostap` mode? David -- David Young dyo...@pobox.comUrbana, IL(217) 721-9981
problem getting hostapd and bridging to work
I have been trying to set up a simple wireless access point using rpi model B under NetBSD 10.0-BETA and seem to be failing miserably. Can someone hit me with a cluebat :-) Basically I have ethernet coming into the rpi usmsc0 10/100 interface and a USB D-Link DWA-140 to provide the wireless access point. The two interfaces are bridged and hostapd is used to do WPA authentication. The dhcp server sits on the router at the end of the cat5. /etc/ifconfig.bridge0 create up ! brconfig bridge0 add usmsc0 add run0 /etc/ifconfig.usmsc0 up inet 192.168.0.254 netmask 0xff00 media autoselect /etc/ifconfig.run0 apbridge up /etc/hostapd.conf country_code=GB logger_syslog=-1 logger_syslog_level=1 debug=4 interface=run0 ssid=Penkett2 hw_mode=g macaddr_acl=0 auth_algs=1 wpa=2 wpa_passphrase=secret-pass wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP default router is set to 192.168.0.1 and resolver to 8.8.8.8 - these are only set so I can transfer files. Everything comes up OK, I have hostapd running with as much debug as I can get. A mobile phone connects and authenticates OK, but then fails to get an IP address. Something seems to be not working on the bridge. The messages file shows: Jul 18 17:04:38 ap1 hostapd: Configuration file: /etc/hostapd.conf Jul 18 17:04:40 ap1 hostapd: run0: interface state UNINITIALIZED- >COUNTRY_UPDATE Jul 18 17:04:45 ap1 hostapd: Using interface run0 with hwaddr 9c:d6:43:6a:f0:76 and ssid "Penkett2" Jul 18 17:04:52 ap1 hostapd: run0: interface state COUNTRY_UPDATE- >ENABLED Jul 18 17:04:52 ap1 hostapd: run0: AP-ENABLED Jul 18 17:08:02 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11: associated Jul 18 17:08:02 ap1 hostapd: run0: AP-STA-CONNECTED d6:16:5e:b2:ae:67 Jul 18 17:08:02 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 RADIUS: starting accounting session A563B597F63F8398 Jul 18 17:08:02 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 WPA: pairwise key handshake completed (RSN) Jul 18 17:08:20 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11: disassociated Jul 18 17:08:20 ap1 hostapd: run0: AP-STA-DISCONNECTED d6:16:5e:b2:ae:67 Jul 18 17:08:20 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory Jul 18 17:08:20 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory Jul 18 17:08:21 ap1 hostapd: ioctl[SIOCS80211, op=21, val=0, arg_len=42]: Invalid argument Jul 18 17:11:34 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11: associated Jul 18 17:11:35 ap1 hostapd: run0: AP-STA-CONNECTED d6:16:5e:b2:ae:67 Jul 18 17:11:35 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 RADIUS: starting accounting session F9049BBD13382057 Jul 18 17:11:35 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 WPA: pairwise key handshake completed (RSN) Jul 18 17:11:53 ap1 hostapd: run0: STA d6:16:5e:b2:ae:67 IEEE 802.11: disassociated Jul 18 17:11:53 ap1 hostapd: run0: AP-STA-DISCONNECTED d6:16:5e:b2:ae:67 Jul 18 17:11:53 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory Jul 18 17:11:53 ap1 hostapd: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory Jul 18 17:11:53 ap1 hostapd: ioctl[SIOCS80211, op=21, val=0, arg_len=42]: Invalid argument tcpdump shows: ap1# tcpdump -i run0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on run0, link-type EN10MB (Ethernet), capture size 262144 bytes 17:11:34.716656 EAPOL key (3) v2, len 95 17:11:34.724503 EAPOL key (3) v1, len 117 17:11:34.827149 EAPOL key (3) v2, len 157 17:11:35.209920 EAPOL key (3) v1, len 95 17:11:35.311142 IP6 :: > ff02::1:ffc9:f4cb: ICMP6, neighbor solicitation, who has fe80::2d01:bf18:cc9:f4cb, length 24 17:11:35.311381 IP6 :: > ff02::1:ffc9:f4cb: ICMP6, neighbor solicitation, who has fe80::2d01:bf18:cc9:f4cb, length 24 17:11:35.321774 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88 17:11:35.322028 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88 17:11:35.501651 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298 17:11:35.501943 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from d6:16:5e:b2:ae:67 (oui Unknown), length 298 17:11:35.502940 ARP, Request who-has 192.168.0.131 tell 192.168.0.1, length 50 17:11:36.085475 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 17:11:36.085737 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 17:11:36.087751 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router solicitation, length 16 17:11:36.088005 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::2: ICMP6, router solicitation, length 16 17:11:36.129132 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH ICMP6, multicast listener report v2, 4 group record(s), length 88 17:11:36.129426 IP6 fe80::2d01:bf18:cc9:f4cb > ff02::16: HBH
Re: Trying to run hostapd as solely a stand-alone Radius server
In article <0bee8c6432b826c8139af27b4e0c0...@mail.bigjar.com>,
jmitchel <jmitc...@bigjar.com> wrote:
>On 2018-01-13 22:06, chris...@zoulas.com wrote:
>> On Jan 13, 9:43pm, jmitc...@bigjar.com (jmitchel) wrote:
>> -- Subject: Re: Trying to run hostapd as solely a stand-alone Radius
>> server
>>
>> | And if I run hostapd with driver=bsd and my ethernet interface, I
>> lose
>> | my SSH connection and can no longer ping the interface. The machine
>> is
>> | still up and hostapd exits.
>>
>> I committed this on HEAD; try rebuilding it with:
>>
>> christos
>>
>> Index: Makefile
>> ===
>> RCS file: /cvsroot/src/external/bsd/wpa/bin/hostapd/Makefile,v
>> retrieving revision 1.10
>> diff -u -u -r1.10 Makefile
>> --- Makefile21 Nov 2016 20:15:16 - 1.10
>> +++ Makefile14 Jan 2018 03:04:54 -
>> @@ -47,6 +47,8 @@
>> # drivers
>> SRCS+= \
>> driver_bsd.c \
>> +driver_none.c \
>> +driver_wired.c \
>> driver_common.c \
>> drivers.c
>>
>> @@ -117,6 +119,9 @@
>> CPPFLAGS+= -DCONFIG_CTRL_IFACE
>> CPPFLAGS+= -DCONFIG_CTRL_IFACE_UNIX
>> CPPFLAGS+= -DCONFIG_DRIVER_BSD
>> +CPPFLAGS+= -DCONFIG_DRIVER_NONE
>> +CPPFLAGS+= -DCONFIG_DRIVER_WIRED
>> +CPPFLAGS+= -DCONFIG_DRIVER_WPA
>> .if ${MKINET6} != "no"
>> CPPFLAGS+= -DCONFIG_IPV6
>> .endif
>
>Thanks! hostapd runs now. But there's one problem remaining. The Radius
>server only seems to be looking for encapsulated EAP requests. When I
>try from a regular radius client, I get this message from hostapd (with
>debugging turned on)
>
>RADIUS SRV: Received 116 bytes from A.B.C.D:58059
>RADIUS SRV: Creating a new session
>RADIUS SRV: Matching user entry found
>EAP: Server state machine created
>RADIUS SRV: New session 0x0 initialized
>RADIUS SRV: No EAP-Message in RADIUS packet from A.B.C.D
>
>Is there any way to use the Radius server in hostapd without sending an
>encapsulated EAP request?
The relevant code is:
if (eap == NULL && sess->macacl) {
reply = radius_server_macacl(data, client, sess, msg);
if (reply == NULL)
return -1;
goto send_reply;
}
if (eap == NULL) {
RADIUS_DEBUG("No EAP-Message in RADIUS packet from %s",
from_addr);
data->counters.packets_dropped++;
client->counters.packets_dropped++;
return -1; // You could put goto send_reply; here
// but we need to fill the the packet before?
}
So if the session does not have a macacl (whatever that means) and there
is no eap data then we fail. Can you see how it gets macacl?
christos
Re: Trying to run hostapd as solely a stand-alone Radius server
On 2018-01-13 22:06, chris...@zoulas.com wrote:
On Jan 13, 9:43pm, jmitc...@bigjar.com (jmitchel) wrote:
-- Subject: Re: Trying to run hostapd as solely a stand-alone Radius
server
| And if I run hostapd with driver=bsd and my ethernet interface, I
lose
| my SSH connection and can no longer ping the interface. The machine
is
| still up and hostapd exits.
I committed this on HEAD; try rebuilding it with:
christos
Index: Makefile
===
RCS file: /cvsroot/src/external/bsd/wpa/bin/hostapd/Makefile,v
retrieving revision 1.10
diff -u -u -r1.10 Makefile
--- Makefile21 Nov 2016 20:15:16 - 1.10
+++ Makefile14 Jan 2018 03:04:54 -
@@ -47,6 +47,8 @@
# drivers
SRCS+= \
driver_bsd.c \
+driver_none.c \
+driver_wired.c \
driver_common.c \
drivers.c
@@ -117,6 +119,9 @@
CPPFLAGS+= -DCONFIG_CTRL_IFACE
CPPFLAGS+= -DCONFIG_CTRL_IFACE_UNIX
CPPFLAGS+= -DCONFIG_DRIVER_BSD
+CPPFLAGS+= -DCONFIG_DRIVER_NONE
+CPPFLAGS+= -DCONFIG_DRIVER_WIRED
+CPPFLAGS+= -DCONFIG_DRIVER_WPA
.if ${MKINET6} != "no"
CPPFLAGS+= -DCONFIG_IPV6
.endif
Thanks! hostapd runs now. But there's one problem remaining. The Radius
server only seems to be looking for encapsulated EAP requests. When I
try from a regular radius client, I get this message from hostapd (with
debugging turned on)
RADIUS SRV: Received 116 bytes from A.B.C.D:58059
RADIUS SRV: Creating a new session
RADIUS SRV: Matching user entry found
EAP: Server state machine created
RADIUS SRV: New session 0x0 initialized
RADIUS SRV: No EAP-Message in RADIUS packet from A.B.C.D
Is there any way to use the Radius server in hostapd without sending an
encapsulated EAP request?
Thanks,
Jason M.
Re: Trying to run hostapd as solely a stand-alone Radius server
On Jan 13, 9:43pm, jmitc...@bigjar.com (jmitchel) wrote:
-- Subject: Re: Trying to run hostapd as solely a stand-alone Radius server
| And if I run hostapd with driver=bsd and my ethernet interface, I lose
| my SSH connection and can no longer ping the interface. The machine is
| still up and hostapd exits.
I committed this on HEAD; try rebuilding it with:
christos
Index: Makefile
===
RCS file: /cvsroot/src/external/bsd/wpa/bin/hostapd/Makefile,v
retrieving revision 1.10
diff -u -u -r1.10 Makefile
--- Makefile21 Nov 2016 20:15:16 - 1.10
+++ Makefile14 Jan 2018 03:04:54 -
@@ -47,6 +47,8 @@
# drivers
SRCS+= \
driver_bsd.c \
+driver_none.c \
+driver_wired.c \
driver_common.c \
drivers.c
@@ -117,6 +119,9 @@
CPPFLAGS+= -DCONFIG_CTRL_IFACE
CPPFLAGS+= -DCONFIG_CTRL_IFACE_UNIX
CPPFLAGS+= -DCONFIG_DRIVER_BSD
+CPPFLAGS+= -DCONFIG_DRIVER_NONE
+CPPFLAGS+= -DCONFIG_DRIVER_WIRED
+CPPFLAGS+= -DCONFIG_DRIVER_WPA
.if ${MKINET6} != "no"
CPPFLAGS+= -DCONFIG_IPV6
.endif
Re: Trying to run hostapd as solely a stand-alone Radius server
On 2018-01-13 07:21, chris...@astron.com wrote: In article <7c6a79ab05e9fdd22e449d63d7cb1...@mail.bigjar.com>, jmitchel <jmitc...@bigjar.com> wrote: Hello, I'm trying to run hostapd as a standalone Radius server without any of the wireless functionality. /usr/src/external/bsd/wpa/dist/hostapd/hostapd.conf has the following: # Driver interface type (hostap/wired/madwifi/test/none/nl80211/bsd); # default: hostap). nl80211 is used with all Linux mac80211 drivers. # Use driver=none if building hostapd as a standalone RADIUS server that does # not control any wireless/wired driver. # driver=hostap But the only option for driver that doesn't cause hostapd to generate an error on startup is bsd, and you have to supply a physical interface (not lo0) which stops working when you run hostapd. I'm running NetBSD 6.1.5 on port-i386. As a test I'm running on a full installation of NetBSD, but the target is an embedded appliance. Is there a way to disable the wireless portion of things and still have a functioning radius server? Sorry if this is the wrong group. If so, please let me know where I should send this to. Thanks, Jason M. P.S. Please copy me on any replies, I'm not subscribed to netbsd-users. Thanks again! Have you tried driver=test? christos Yes, I tried them all. The only one that doesn't cause hostapd to exit with an error is bsd. quantumleap:/home/jmitchel/temp# hostapd /home/jmitchel/temp/hostapd.conf Configuration file: /home/jmitchel/temp/hostapd.conf Line 9: invalid/unknown driver 'test' 1 errors found in configuration file '/home/jmitchel/temp/hostapd.conf' quantumleap:/home/jmitchel/temp# hostapd /home/jmitchel/temp/hostapd.conf Configuration file: /home/jmitchel/temp/hostapd.conf Line 9: invalid/unknown driver 'none' 1 errors found in configuration file '/home/jmitchel/temp/hostapd.conf' quantumleap:/home/jmitchel/temp# hostapd /home/jmitchel/temp/hostapd.conf Configuration file: /home/jmitchel/temp/hostapd.conf Line 9: invalid/unknown driver 'hostap' 1 errors found in configuration file '/home/jmitchel/temp/hostapd.conf' quantumleap:/home/jmitchel/temp# hostapd /home/jmitchel/temp/hostapd.conf Configuration file: /home/jmitchel/temp/hostapd.conf Line 9: invalid/unknown driver 'wired' 1 errors found in configuration file '/home/jmitchel/temp/hostapd.conf' quantumleap:/home/jmitchel/temp# hostapd /home/jmitchel/temp/hostapd.conf Configuration file: /home/jmitchel/temp/hostapd.conf Line 9: invalid/unknown driver 'madwifi' 1 errors found in configuration file '/home/jmitchel/temp/hostapd.conf' quantumleap:/home/jmitchel/temp# hostapd /home/jmitchel/temp/hostapd.conf Configuration file: /home/jmitchel/temp/hostapd.conf Line 9: invalid/unknown driver 'nl80211' 1 errors found in configuration file '/home/jmitchel/temp/hostapd.conf' And if I run hostapd with driver=bsd and my ethernet interface, I lose my SSH connection and can no longer ping the interface. The machine is still up and hostapd exits. Thanks, Jason M.
Re: Trying to run hostapd as solely a stand-alone Radius server
In article <7c6a79ab05e9fdd22e449d63d7cb1...@mail.bigjar.com>, jmitchel <jmitc...@bigjar.com> wrote: >Hello, > >I'm trying to run hostapd as a standalone Radius server without any of >the wireless functionality. >/usr/src/external/bsd/wpa/dist/hostapd/hostapd.conf has the following: > ># Driver interface type (hostap/wired/madwifi/test/none/nl80211/bsd); ># default: hostap). nl80211 is used with all Linux mac80211 drivers. ># Use driver=none if building hostapd as a standalone RADIUS server that >does ># not control any wireless/wired driver. ># driver=hostap > >But the only option for driver that doesn't cause hostapd to generate an >error on startup is bsd, and you have to supply a physical interface >(not lo0) which stops working when you run hostapd. > >I'm running NetBSD 6.1.5 on port-i386. As a test I'm running on a full >installation of NetBSD, but the target is an embedded appliance. > >Is there a way to disable the wireless portion of things and still have >a functioning radius server? Sorry if this is the wrong group. If so, >please let me know where I should send this to. > >Thanks, > >Jason M. > >P.S. Please copy me on any replies, I'm not subscribed to netbsd-users. >Thanks again! Have you tried driver=test? christos
Trying to run hostapd as solely a stand-alone Radius server
Hello, I'm trying to run hostapd as a standalone Radius server without any of the wireless functionality. /usr/src/external/bsd/wpa/dist/hostapd/hostapd.conf has the following: # Driver interface type (hostap/wired/madwifi/test/none/nl80211/bsd); # default: hostap). nl80211 is used with all Linux mac80211 drivers. # Use driver=none if building hostapd as a standalone RADIUS server that does # not control any wireless/wired driver. # driver=hostap But the only option for driver that doesn't cause hostapd to generate an error on startup is bsd, and you have to supply a physical interface (not lo0) which stops working when you run hostapd. I'm running NetBSD 6.1.5 on port-i386. As a test I'm running on a full installation of NetBSD, but the target is an embedded appliance. Is there a way to disable the wireless portion of things and still have a functioning radius server? Sorry if this is the wrong group. If so, please let me know where I should send this to. Thanks, Jason M. P.S. Please copy me on any replies, I'm not subscribed to netbsd-users. Thanks again!
hostapd/dhcpd problem in netbsd-7, but not netbsd-6
Hello all, I'm having a strange problem. I've set up an access point using hostapd, a wifi adapter (ral0), a wired ethernet adapter (mvgbe0 in my dockstar) and I bridged ral0 and mvgbe0 together using brconfig. It works fine if I'm on netbsd-6. Specifically, 6.1_STABLE from kernels I've been building recently from netbsd-6. The userland is probably 6 months old or so. However, on my dockstar machine with netbsd-7 and an identical setup, everything works fine EXCEPT wifi clients attached to wifi adapter ural0 (new name for ral0 in netbsd-7) or athn0 (another wifi adapter, not supported in netbsd-6) cannot get a DHCP address. If you google hostapd dhcp not working, you'll see similar problem descriptions (but on Linux). If I set a static address on the wifi client, the problem is solved. This same dhcpd (installed on another machine in the same subnet) is working fine for many clients that are wired or attached to another wifi access point in the network. When the problem occurs, I can see that the dhcp client is asking for an address because the dhcpd server tries to respond. But those frames never make it back to the client that needs the address. And an address is never set. Well, actually, that's not true. I saw it work correctly maybe once or twice in netbsd-7. Bizarre. Does anyone know what changed in netbsd-7? Andy
