<a0a22b9f0512042124q57e4afacuab0075c3e18a08e7 at mail dot gmail dot com>, Ervin
Malicdem <schadow1 at gmail dot com> writes
>Pardon my ignorance, Neil, because I am a newbie in terms of networking
>so I do not know how put a passive tap and check if MAC address are
>What I only observe whenever I try to authenticate a wireless client is
>that the wireless AP's (WRT54G) MAC address gets authenticated but the
>wireless client's MAC does not get authenticated. But when
>authenticating the wired clients through the LAN ports of WRT54G, the
>MAC of the AP plus the MAC of the wired client gets authenticated.
>I see those info, btw, at m0n0wall's captive portal logs.
OK. I know there was someone else on the list who had the same problem.
Is there anyone here with this problem that can perform a packet capture
between the wireless AP and m0n0wall to ensure that the AP isn't hiding
everything behind its own MAC address?
>On 12/5/05, Neil A. Hillard <m0n0 at dana dot org dot uk> wrote:
> In message <
> a0a22b9f0512041638r4da66ddk473b2b8a57e692a0 at mail dot gmail dot com>,
> Ervin Malicdem <schadow1 at gmail dot com> writes
> >This was an issue I have brought up since July but no working
> solutions were
> >given. Using WRT54G as WAP (not using WAN port) and disabled MAC
> >Sadly, WRT54G - Captive Portal Authentication only works with 1.2b7
> for me.
> >Anything above that version will simply loop you back to the
> >But if you connect through the wired port of the WRT54G, you can
> >successfully authenticate. This problem only happens if you
> Are you able to put either a hub or passive tap between the AP and
> m0n0wall to check the MAC address being sent in the packets from the
> wireless client by performing a packet capture?
> Neil A. Hillard E-Mail: m0n0 at dana dot org dot uk
> 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
Neil A. Hillard E-Mail: m0n0 at dana dot org dot uk