Thanks for this note. We have not tested 1.2b2, but 1.2b7 works for us in
this set/up, but not the latest two betas, this is on soekris. It also works
with WDS enabled on wirelessly connected devices, all on alchemy 1.0.
Out of interest, who makes / what drivers do the Ethernet ports use on Wrap
boards? Is it the Nat semi as on Soekris?
From: Jens Wellhausen [mailto:jw at ib dash wellhausen dot de]
Sent: 30 June 2005 08:09
To: Christian H Borrman
Cc: m0n0wall at lists dot m0n0 dot ch; cbuechler at gmail dot com
Subject: Re: [m0n0wall] Captive Portal and WRT54G
maybe it is interesting for somebody: I have tested my setup (WRT54G
with alchemy firmware and a wrap m0n0wall with captive portal) with
different versions of m0n0wall: Authentication works for me with 1.2b2,
but not with 1.2b7 and 1.2b8 and 1.2b9.
"Not" means, that the MAC/IP of the AP is authenticated, and not the client.
Christian H Borrman schrieb:
> This set-up (WDS with Sveasoft, and other firmwares) Works in 1.2b7, but
> in 1.2b8 or 1.2b9, for some unknown reason, we get the same issues with
> latest two m0n0wall Beta.
> The only linksys firmware you may like to try is the portless networks
> as I read somewhere that it is the only firmware to do a true wireless to
> LAN bridge, however, WDS on this firmware is done via Shell and then
> committing to NVRAM if you want WDS to work after a reboot, however this
> means if you want to later add other WDS clients after commit to NVRAM on
> the original ones, you will have to flash all linksys routers and start
> scratch again.
> However, given that this works on 1.2b7, you may wish to just use this
> -----Original Message-----
> From: Jens Wellhausen [mailto:jw at ib dash wellhausen dot de]
> Sent: 24 June 2005 08:09
> To: m0n0wall at lists dot m0n0 dot ch; cbuechler at gmail dot com
> Subject: Re: [m0n0wall] Captive Portal and WRT54G
> >> Hi there,
> >> I have installed m0n0wall 1.2b8 on a wrap box, configured the captive
> >> portal for radius authentication and everything worked very fine
> when >> I
> >> had an D-Link 2000AP+ accesspoint attached to the m0n0wall.
> >> Now I would like to use a Linksys WRT54G as accesspoint (with
> >> alchemy firmware), because it would be nice to extend the wireless
> >> using WDS. Unfortunately, the authentication does not work anymore,
> >> because the IP and MAC address of the accesspoint are authenticated,
> >> not the client...
> >> As I have read before, it is not possible to use an IP routed network
> >> behind the captiveportal, but how can I disable the router in the
> >> in that way that it acts like a simple accesspoint? Using WDS later
> >> should not be any problem because it is a MAC-layer protocol, am I
> >> here?
> >In 1.2b8 you can do authentication based on IP only.
> >I don't know about the Sveasoft firmware, but with the Linksys
> >firmware you just have to plug one of the LAN ports into the m0n0wall,
> >not the WAN port, and it briges the wireless over to the LAN port.
> So far I think I am doing right. I have connected the WRT54G using a LAN
> port, switched off the WAN port, but no success. The next step could be
> to flash back the original Linksys firmware. But it would be very nice
> to use the WDS, so are there any other ideas (for example, other
> accesspoint hardware)?
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch