On Sunday 26 January 2014 04:29:54 Giancarlo Razzolini wrote:
> Em 25-01-2014 19:15, Eike Lantzsch escreveu:
> > On Saturday 25 January 2014 11:11:43 you wrote:
> > 
> > if you want athn0 and vr1 to be on the same network, bridge them
> > together then assign an IP address to only one of the two.
> > 
> > 
> > -ken
> > 
> > Thanks Ken for the hint!
> > I reckon that assigning IP addresses to both interfaces in the
> > same
> > network is not the correct approach.
> > 
> > I tried your hint and at least the ALIX 2d13 is routing again.
> > 
> > Just for the record:
> > 
> > athn0 is the interface to assign the IP address. Otherwise it gets
> > status "no network" and will not come up.
> > 
> > # cat /etc/hostname.athn0
> > inet 192.168.12.1 255.255.255.128
> > chan 108
> > mediaopt hostap
> > nwid mywlanid
> > wpakey somelongkey
> > 
> > # cat /etc/hostname.vr1
> > up media autoselect
> > 
> > # cat /etc/hostname.bridge0
> > add athn0
> > add vr1
> > up
> > 
> > ****************
> > 
> > And for the record again because somebody else had problems with
> > this card:
> > 
> > I can now connect via WiFi with my MACbook-Air on 5GHz (channel
> > 108) but my Samsung Galaxy3 does not want to connect although it
> > sees the network and the field strength is -39dBm @ 5540MHz.
> > 
> > Trying the same on channel 6 results in nothing but a timeout
> > error on both the MAC and the Samsung phone.
> > 
> > No idea if this is due to the Compex card, the athn driver or the
> > Samsung phone.
> > 
> > ****************
> > 
> > On Sat, Jan 25, 2014 at 10:46 AM, Eike Lantzsch <zp6...@gmx.net>
> > wrote:
> > 
> > I'm using 5.4 stable on an ALIX 2D13 with Compex WLM200NX
> > 
> > My internal network is 192.168.12.0/24
> > My ISP gives me 181.40.100.8 nm 255.255.255.0 gw 181.40.100.1 via
> > DHCP with reserved IP address. This is on vr0
> > No problems here.
> > 
> > I wanted to set up two internal networks
> > on vr1:
> > 192.168.12.0/25
> > 
> > and on vr2:
> > 192.168.12.128/25
> > 
> > athn0 is also supposed to be on 192.168.12.0/25
> > The intended /etc/hostname.athn0 is:
> > inet 192.168.12.2 255.255.255.128
> > 
> > /etc/hostname.vr0
> > dhcp
> > 
> > /etc/hostname.vr1
> > inet 192.168.12.1 255.255.255.128
> > 
> > /etc/hostname.vr2
> > inet 192.168.12.129 255.255.255.128
> > 
> > The weirdness is as follows:
> > according to ifconfig all interfaces are active
> > BUT
> > 
> > athn0 does not want to be on the same subnet with vr1
> > 
> > I cannot ping the internal IP 192.168.12.1
> > as long as athn0 is on 192.168.12.2 or any other address up to
> > 192.168.12.126 that is in the subnet 192.168.12.128/25.
> > 
> > I have to change athn0 to the other subnet with
> > /etc/hostname.athn0
> > inet 192.168.12.130 255.255.255.128
> > 
> > In this case I can ping 192.168.12.1 and 192.168.12.130
> > 
> > (ping from inside the ALIX that is)
> > 
> > [rest snipped for brevity]
> 
> Or even better, bridge them and a vether(4) and assign the ip
> address to it, instead of one of the physical interfaces.
> 
> Cheers,

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.
I realise that the Atheros drivers still seem to be quite finniky - at 
least in hostap mode, or is this hardwired into the card?

Anybody out there who did this? I can't imagine that this setup is so 
rare; at least every cheap consumer-grade router does this.

Thanks Giancarlo!
All the best
Eike

Reply via email to