EFW Support

Support => General Support => Topic started by: bangsters on Thursday 17 November 2011, 03:09:36 pm



Title: System Access restriction by MAC Address not working??
Post by: bangsters on Thursday 17 November 2011, 03:09:36 pm
Hi.  I have installed 2.4.1.  In the System Access rule, I can filter who can access the endian administration, either by network, IP, or MAC.

I want to restrict by MAC so I can access it whererver I am via my laptop.... but it doesn't work.  I have entered my MAC address in the format aa:bb:cc:dd:ee:ff but it still wouldn't work.  If I put my IP it does work however, but I don't want by IP since that restricts me to where I'm at....

Any ideas what could be wrong?


Title: Re: System Access restriction by MAC Address not working??
Post by: bangsters on Friday 18 November 2011, 02:17:22 pm
bump anyone??


Title: Re: System Access restriction by MAC Address not working??
Post by: bangsters on Tuesday 29 November 2011, 02:16:06 pm
anyone got this working??


Title: Re: System Access restriction by MAC Address not working??
Post by: gabrielpugliese on Sunday 15 January 2012, 12:13:23 am
I'm having the same issue. It's impossible to deny packets from any port to any port through MAC filtering.
Using Endian 2.4.1 too.


Title: Re: System Access restriction by MAC Address not working??
Post by: qhris on Wednesday 01 February 2012, 06:03:42 pm
I wouldn't think that it is possible, as MAC is only a lan facing address. It is in the packet, but buried deep until it hits the lan. What I do is port forward to one of my internal servers, then have that server send me an email every hour. I can get the public IP from that email and remote desktop to the internal server, then access my EFW from that server. It is kind of roundabout, but it works flawlessly and does not expose my EFW to hack attempts from the web. If someone finds my forwarded port then the internal server will lock out after a few attempts (it happened once...). I use high port numbers in my forwarding to thwart the usual scanners, and you can see the failed attempts in the server log.
Q