[ previous ] [ next ] [ threads ]
 
 From:  "Stephen McCormick" <sdmcc at ihug dot co dot nz>
 To:  "'Jimmy Bones \(Mhottie\)'" <mhottie at gmail dot com>, <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Monowall 1.21 Captive portal and WRT54G wireless router MAC Problem
 Date:  Fri, 6 Jan 2006 10:14:05 +1300
Any chance on doing the same tests using 1.21?

Stephen McCormick
SDM Consulting Ltd
Auckland

-----Original Message-----
From: Jimmy Bones (Mhottie) [mailto:mhottie at gmail dot com] 
Sent: Friday, 6 January 2006 9:58 a.m.
To: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Monowall 1.21 Captive portal and WRT54G wireless
router MAC Problem

Chris,

Per previous thread, I did take some time this weekend to test this issue
briefly.

I used WRT54g H/W V 2.0 -- V 2.1 -- V 3.0 (3 seperate units) Running
HyperWRT 2.1b1 + Tofu 11 on the Linksys 4.30.1 codebase. One router (the
V2.1) was using Linksys Stock 4.30.1 for a control.

I do not, nor ever have, used the WRT54G's for gateway use, so nothing is
ever plugged into the WAN ports. It goes;

ISP --> m0n0wall 1.20 cd-rom version [amd k6-3 500] --> Cisco 2924XL switch
[port flagged highest priority, network port, spanning tree off] -->
WRT54G LAN port. That's how they are all setup as a wire drop from the Cisco
switch into a lan port. One of them comes off another 8 port switch
[cisco-->8 port switch-->wrt54g]. There they serve wireless clients, etc.
Using WPA2 TKIP+AES PSK. [They will soon be WPA2 Radius]

m0n0wall is setup with dns forwarder off, all clients point to internal DNS
server (AD domain) for nameservice.

**Note, I am still having this weird issue where clients will not use
anything other then the 1st DNS server listed with captive portal on, the
rare occasion when the DNS is being worked on, etc. they all timeout instead
of using the 2nd DNS server listed [an outside DNS]**

I brought 13 wireless clients, some have been seen before some never. All
authenticated to the WRT54G's, and hit the Captive Portal page instantly.
Hit accept, client went straight through. All MAC's showing up under Status
-> Captive Portal belong to the wireless cards of the clients. I do not see
any of the WRT54g's MAC's anywhere in Captive Portal.

I have the data saved and can do further testing if neccessary, but this is
what I am seeing here. The 2 HyperWRT's and the 1 Stock Linksys all behaved
the same with regard to Captive Portal.

-j

On 1/3/06, Chris Buechler <cbuechler at gmail dot com> wrote:
>
> On 1/3/06, Stephen McCormick <sdmcc at ihug dot co dot nz> wrote:
> > Hi all,
> >
> > Just upgraded to 1.21 and was testing out the new captive portal
> > functionality.
> >
> > Pre 1.21, I have had no problems with wirelessly connecting through the
> > WRT54G to a dedicated optional interface on Mono running captive portal.
> > Mono would pick up the right MAC address and apply the appropriate rule
> > (whether it was a MAC  that was allowed to passthrough or one that was
> > processed by the portal)
> >
>
> what firmware are you running on the WRT54G?  Every report of this
> thus far seems to be traceable to some buggy third party firmware.
>
> -Chris
>
> ---------------------------------------------------------------------
> 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
>
>