Re: OpenBSD as a non-routing access point

Hi, I had the same problem with 6.1 on Alix 2D13 boards, I've created a bridge0 interface with vr0, vr1, vr2 and athn0 (the wireless one configured in hostap mode) but no ip address was given to any of the wifi connected devices by my dhcp server. However, all the computers linked with an

Re: OpenBSD as a non-routing access point

On 2017-04-12, trondd wrote: > > I have this problem as well. DHCP requests go out over the bridge to the > main interface. The response comes back to the main interface but never > goes to the bridge. > > I'm trying to use vmm VMs on a bridge. I've tried set skip on

Re: OpenBSD as a non-routing access point

On 2017-04-12, Jordon wrote: > When one buys a linksys/netgear/whatever “Wireless Access Point”, it is > often intended to be a full Internet gateway (router, NAT, DHCP, etc) that > also does wifi. Those tend to get called "router" or "wireless gateway" or similar, AP

Re: OpenBSD as a non-routing access point

On Wednesday, 12 April 2017 14:40:28 -04 trondd wrote: > On Wed, April 12, 2017 4:27 am, Stuart Henderson wrote: > > On 2017-04-12, Jordon wrote: > >>> rcctl enable dhcrelay > >>> rcctl set dhcrelay flags -i athn0 192.168.1.1 "assuming that is your > >>> routers > >> > >>

Re: OpenBSD as a non-routing access point

> On Apr 12, 2017, at 3:27 AM, Stuart Henderson wrote: > > On 2017-04-12, Jordon wrote: >>> rcctl enable dhcrelay >>> rcctl set dhcrelay flags -i athn0 192.168.1.1 "assuming that is your routers >> address" >>> rcctl start dhcrelay >>> >>> and possibly

Re: OpenBSD as a non-routing access point

> On Apr 12, 2017, at 1:47 PM, Mihai Popescu wrote: > > Because of titles like this post there is no clear anymore what > someone is reffering to when one is using words like bridge, switch, > hub, access point, router, ... > Add the IPv6 in the mix and you think you understand

Re: OpenBSD as a non-routing access point

> On Apr 12, 2017, at 1:54 AM, Stefan Sperling wrote: > > On Tue, Apr 11, 2017 at 08:04:45PM -0500, Jordon wrote: >> /ets/hostname.athn0 >> media autoselect mode 11n media opt host ap chan 1 > > Is there actual whitespace between 'media' and 'opt' and between > 'host' and 'ap'

Re: OpenBSD as a non-routing access point

Because of titles like this post there is no clear anymore what someone is reffering to when one is using words like bridge, switch, hub, access point, router, ... Add the IPv6 in the mix and you think you understand the spagetti of internet. Bleah, looking again at "non-routing access point".

Re: OpenBSD as a non-routing access point

On Wed, April 12, 2017 4:27 am, Stuart Henderson wrote: > On 2017-04-12, Jordon wrote: >>> rcctl enable dhcrelay >>> rcctl set dhcrelay flags -i athn0 192.168.1.1 "assuming that is your >>> routers >> address" >>> rcctl start dhcrelay >>> >>> and possibly add -d (log to

Re: OpenBSD as a non-routing access point

On 2017-04-12, Jordon wrote: >> rcctl enable dhcrelay >> rcctl set dhcrelay flags -i athn0 192.168.1.1 "assuming that is your routers > address" >> rcctl start dhcrelay >> >> and possibly add -d (log to stderr) to see what its doing. >> > > Thank you! That got it working!

Re: OpenBSD as a non-routing access point

On Tue, Apr 11, 2017 at 08:04:45PM -0500, Jordon wrote: >/ets/hostname.athn0 > media autoselect mode 11n media opt host ap chan 1 Is there actual whitespace between 'media' and 'opt' and between 'host' and 'ap' in your config file? Or is this a copy/paste error? It should look like this:

Re: OpenBSD as a non-routing access point

> I'm not certain but I suspect you're athn address is outside your routers > subnet. > No, they’re both on 192.168.77.x

Re: OpenBSD as a non-routing access point

Sent from my iPhone On Apr 11, 2017, at 9:55 PM, Jordon wrote: >> >> rcctl enable dhcrelay >> rcctl set dhcrelay flags -i athn0 192.168.1.1 "assuming that is your routers address" >> rcctl start dhcrelay >> >> and possibly add -d (log to stderr) to see what its doing. >> >

Re: OpenBSD as a non-routing access point

> rcctl enable dhcrelay > rcctl set dhcrelay flags -i athn0 192.168.1.1 "assuming that is your routers address" > rcctl start dhcrelay > > and possibly add -d (log to stderr) to see what its doing. > Thank you! That got it working! So why is that necessary? Doesnt the bridge just forward

Re: OpenBSD as a non-routing access point

On 04/11/17 20:13, Jordon wrote: What is your dhcpd.conf and have you verified it's running? There is none - the OpenBSD machine that I am trying to turn into an access point is not the DHCP server or router in my network. With bridging enabled, shouldn’t DHCP requests just be forwarded to

Re: OpenBSD as a non-routing access point

> What is your dhcpd.conf and have you verified it's running? > There is none - the OpenBSD machine that I am trying to turn into an access point is not the DHCP server or router in my network. With bridging enabled, shouldn’t DHCP requests just be forwarded to the wired network, where the

Re: OpenBSD as a non-routing access point

Sent from my iPhone > On Apr 11, 2017, at 8:04 PM, Jordon wrote: > > Ok, lets try this again… > > I got the 9280 installed. My configs are like this: > > My interfaces are configured like this: > > /etc/hostname.re0 > dhcp > > /ets/hostname.athn0 > media autoselect mode

Re: OpenBSD as a non-routing access point

Ok, lets try this again… I got the 9280 installed. My configs are like this: My interfaces are configured like this: /etc/hostname.re0 dhcp /ets/hostname.athn0 media autoselect mode 11n media opt host ap chan 1 nwid testytesterson wpakey testingx inet 192.168.77.253 255.255.255.0

Re: OpenBSD as a non-routing access point

On Sat, Apr 08, 2017 at 09:43:29AM -0500, Jordon wrote: > > > On Apr 8, 2017, at 3:38 AM, Stefan Sperling wrote: > > > > On Fri, Apr 07, 2017 at 05:06:22PM -0500, Jordon wrote: > >> My new wifi adapter finally arrived today (AR9271) so I want to give > >> hostap a > >> try with

Re: OpenBSD as a non-routing access point

ny bug in the athn code :P > Original Message ---- > Subject: Re: OpenBSD as a non-routing access point > Local Time: April 8, 2017 4:43 PM > UTC Time: April 8, 2017 2:43 PM > From: open...@sirjorj.com > To: Stefan Sperling <s...@stsp.name> > openbsd-misc &

Re: OpenBSD as a non-routing access point

> Or ar9280 may be better. Pcie devices are usually more capable too. > Exactly what I ordered! And an antenna/pigtail kit. Total price under $30. My openbsd machine (a broadwell Shuttle system) has the mini pcie slot for it, so no pice adapter card needed.

Re: OpenBSD as a non-routing access point

On 8 Apr 2017 6:56 pm, "Kevin Chadwick" wrote: On 8 Apr 2017 3:44 pm, "Jordon" wrote: > On Apr 8, 2017, at 3:38 AM, Stefan Sperling wrote: > > On Fri, Apr 07, 2017 at 05:06:22PM -0500, Jordon wrote: >> My new wifi adapter finally

Re: OpenBSD as a non-routing access point

Earlier this week on this mailing list someone recommended the following product: https://www.olimex.com/Products/USB-Modules/USB-CAP/ I thought I will give it a try and ordered it... Original Message Subject: Re: OpenBSD as a non-routing access point Local Time: April 8

Re: OpenBSD as a non-routing access point

> On Apr 8, 2017, at 3:38 AM, Stefan Sperling wrote: > > On Fri, Apr 07, 2017 at 05:06:22PM -0500, Jordon wrote: >> My new wifi adapter finally arrived today (AR9271) so I want to give hostap a >> try with its new 802.11n support. > >> Am I on the right track? > > No. AR9271 is a

Re: OpenBSD as a non-routing access point

On Fri, Apr 07, 2017 at 05:06:22PM -0500, Jordon wrote: > My new wifi adapter finally arrived today (AR9271) so I want to give hostap a > try with its new 802.11n support. > Am I on the right track? No. AR9271 is a USB device, and unfortunately there are bugs in the driver that prevent hostap

Re: OpenBSD as a non-routing access point

Op 04/08/17 om 00:06 schreef Jordon: My new wifi adapter finally arrived today (AR9271) so I want to give hostap a try with its new 802.11n support. Unfortunately, all the examples I’ve found center around creating a router/AP when all I want to make is an AP - as in, no DHCP or routing. I