NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Issue on doing hostap on urtwn



> I'm now trying to do hostap on NetBSD on my raspberry pi B+ board
Hmm, I thought I was the only person on the planet doing this.

I don't exactly know what the problem is, but since I'm running a similar
setup that Works(TM), I'll just point out some differences to your
information.

(Note that I'm currently using run(4) rather than urtwn(4), but IIRC
the latter did work for me in the past, too)

> 1) /var/log/message: https://gist.github.com/darkgeek/3ab506302ba08d2ffc39
Nothing interesting (except for the DHCPDISCOVER right after a successful
WPA handshake, but I suppose this is a symptom.


> 2) ifconfig output: https://gist.github.com/darkgeek/6f2335d230962acbe91c
> urtwn0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
My interface is additionally in promiscuous mode (But maybe that is
because I've bridge(4)ed it to the wired NIC.
> [...]
> 	inet 10.1.16.21 netmask 0xffffff00 broadcast 10.1.16.255 detached
This seems like the obvious candidate for causing the "Network
unreachable" (the address being detached).  Does that change if you
manually re-assign the address (which I believe also adds some routes to
the routing table) using `ifconfig urtwn0 inet 10.1.16.21/24`?

> 3) hostapd.conf: https://gist.github.com/darkgeek/03052bda8f4559e4ea5e
Can't really tell.  My hostapd.conf has a lot more cruft most of which
I'm unsure about (partly because it's been migrated from a FreeBSD
machine). The settings included in your paste are the same as I have,
though, except auth_algs being 3, and wpa_pairwise lacking the TKIP (I'm
doing WPA2-only)

> 4) dmesg: https://gist.github.com/darkgeek/ed71d501f07ed7b47402
Nothing interesting as far as I can tell

> 5) dhcpd.conf: https://gist.github.com/darkgeek/33bc247e578d5050f529
Looks about right to me

> 6) pf.conf (for NAT): https://gist.github.com/darkgeek/3aeeeadc82b5fb488d67
No idea (I'm still using iptables).  But I would suggest to turn off any
network filtering to rule out this being in the way.  Enable it once
the setup is working.


Other interesting things you could provide:
- netstat -rn
- hostapd logs (see the logger_ lines in
  /usr/share/examples/hostapd/hostapd.conf


Home | Main Index | Thread Index | Old Index