FANDOM


back to http://scratchpad.wikia.com/wiki/Sasecurity

arp -a -macaddress Edit

*arp -a - mac address that is being presented to the mesh box

We have to use the MAC of the CB-3 for MAC auth. /var/state/dhcp/dhcpd.leases will show the MAC of the ethernet adapter, as this is actually the device that the ip is given to. However, if you look in the ARP tables (arp -n), you will see that the ip that it's associating to the MAC address is the MAC of the CB-3.

You can clone the MAC of the CB-3 to the MAC of the device behind it, but we've found that just setting WiaNa RADIUS to use the MAC of the CB-3 works best.

Kenny thanks for you info, we to are also using the CB3+. We have been using other Ethernet clients but not found them to be a reliable as the CB3+.

With our old client we could run lots of clients of the back in the wireless client, I.e. feed the WC in to a switch in a office then everyone that accessed the net was given the splash screen and got on the net. The mesh node also saw each wired client through the WC and reported them in SigSpy or IwList and TraFfic.

The CB3+ only seams to show one wired client on the mesh box, but other users can get access via the CB3, but the mesh box does not show them in sigspy or iwlist and traffic, although they get the splash screen and web access, it's as if the first mac is passed through the WC then others or not, but this can not be as the Mesh node gives them an IP address and access via the splash logon.

We are not using the mac cloning on the CB3.

> Hi All, > > I've been using some CB3s as client devices, and the MAC > authentication no longer seems to work, although the DhCp address > allocation shows the correct end user MAC address.

> My guess is that the CB3 is actually the MAC address used for the > authentication - is there any way to change this behaviour? What other > workarounds have people used?

> I've been using some CB3s as client devices, and the MAC > authentication no longer seems to work, although the DHCP address > allocation shows the correct end user MAC address.

> My guess is that the CB3 is actually the MAC address used for the > authentication - is there any way to change this behaviour? What other > workarounds have people used?

* Doesn't arp -an force to refresh the arp status and give you everything 
* iwspy wlan0 will give them to you as well

> >We have to use the MAC of the CB-3 for MAC auth. > >/var/state/dhcp/dhcpd.leases will show the MAC of the ethernet > >adapter, as this is actually the device that the ip is given to. > >However, if you look in the ARP tables (arp -n), you will see that > >the ip that it's associating to the MAC address is the MAC of the > >CB-3.

> If I do arp -n, I only see devices on the ethernet or br0 devices (ie > meshboxes only, not clients).

> Any idea how I see the devices on wlan0?

using MAC auth Edit

> I am trying to keep a user logged in by using mac or password pair > authentication wiana based captive portal. > > the user connects with a CB3 delux. the other cb3 had a clone mac setting > that seemed to help. I have entered both the mac of the router (netgear > WGR614) as well as the MAC of the CB3 (2 user accounts) and still the user > is presented with the splash screen. Any suggestions are greatly > appreciated! >


Voip, CB3, MAC authentication

I found that if we DID NOT clone the MAC - the CB-3 will pass
everything through under it's MAC. Your ARP table will show all of the devices
behind the CB-3 pulling IP's, but it all comes from the MAC of the CB-3.
Traffic gets shaped by this MAC as well, which is nice. I have to have auto-MAC
on clients that have VoIP, because if the portal times out, they have no
phone service!


If you do arp -a you should get the mac address that is being presented
to the mesh box

We have to use the MAC of the CB-3 for MAC auth.
/var/state/dhcp/dhcpd.leases will show the MAC of the ethernet adapter,
as this is actually the device that the ip is given to. However, if you
look in the ARP tables (arp -n), you will see that the ip that it's
associating to the MAC address is the MAC of the CB-3.

We to are also using the CB3+. We have been
using other Ethernet clients but not found them to be a reliable as the CB3+.
With our old client we could run lots of clients of the back in the wireless
client, I.e. feed the WC in to a switch in a office then everyone that
accessed the net was given the splash screen and got on the net. The
mesh node also saw each wired client through the WC and reported them in
sigspy or iwlist and traffic. The CB3+ only seams to show one wired client
on the mesh box, but other users can get access via the CB3, but the mesh
box does not show them in sigspy or iwlist and traffic, although they get
the splash screen and web access, it's as if the first mac is passed through
the WC then others or not, but this can not be as the Mesh node gives them
an IP address and access via the splash logon.
We are not using the mac cloning on the CB3.

You can clone the MAC of the CB-3 to the MAC of the device behind it,
but we've found that just setting Wiana RADIUS to use the MAC of the
CB-3 works best.

Doesn't arp -an force to refresh the arp status and give you everything?
iwspy wlan0 will give them to you as well

I am trying to keep a user logged in by using mac or password pair
authentication wiana based captive portal. The user connects
with a CB3 delux. the other cb3 had a clone mac
setting that seemed to help. I have entered both the mac of the router
(netgear WGR614) as well as the MAC of the CB3 (2 user accounts) and still the
user is presented with the splash screen. Any suggestions are greatly
appreciated!

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.