Thanks to Peter N. M. Hansteen and to Stefan Sperling! On Sunday 26 January 2014 12:35:46 Stefan Sperling wrote: > On Sun, Jan 26, 2014 at 07:56:37AM -0300, Eike Lantzsch wrote: > > Interesting. I was just about to try this when your response came > > in, (OpenBSD Manual 6.9 "A bridge acting as a DHCP server") > > but since athn0 does not come up unless I assign a network to it, > > I > > doubt that only assigning an IP to vether0 will do the trick. > > "Does not come up" is not exactly true. The interface comes up but > > it does not switch on the transmitter - no WiFi signal. Not true. WiFi signal now comes up on channel 108. See below
> > Did you try 'ifconfig athn0 up'? > Or likewise a line saying 'up' in /etc/hostname.athn0? > > vether and bridge are indeed the way to go. I'm running a > setup like this and it works. > > This example should give you a working configuration (assuming > vr0 is your LAN interface): > The following adapted to my network setup: #cat /etc/hostname.vr0 dhcp # cat /etc/hostname.athn0 nwid mynetwork wpakey 'mypassword' media autoselect mediaopt hostap chan 108 #mode 11a (this is on 5GHz) up # cat /etc/hostname.vether0 inet 192.168.12.1 255.255.255.128 192.168.12.127 up # cat /etc/hostname.vr1 up # cat /etc/hostname.bridge0 add vether0 add vr1 add athn0 up dhcpd_flags="vether0" Yes, success! This works. MAC can connect but Samsung phone still not. [broadcast should not be necessary to mention explicitly but I had all kinds of weird behaviour before - so no harm done by including it in hostname] Now looking for a miniPCI ral card ... and working my way further through The Book of PF. All the best to y'all Eike -- no CC necessary. I'm subscribed to the group. but don't mind, I'm not finniky. Eike Lantzsch ZP6CGE
