> *From:* The EDUCAUSE Wireless Issues Community Group Listserv <
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> *On Behalf Of *Mike Fitzgerald
> *Sent:* Tuesday, September 07, 2021 12:16 PM
> *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> *Subject:* Re: [WIRELESS-LAN] [EXTERNAL] Re: [WIRELES
Hi Educause wifi:
We use a filter that only allows clients to "have" a valid IP address from
"our" range.
It' a bit of overhead, but it solves this issue for us. We also say
clients listed with addresses that really make no sense.
you build a list something like this:
netdestination umn-wiredv4
lip-flopped the “IP Address” and
> the “Default Gateway”….started denying traffic for the default
> gateway….whoops!
>
> *From:* The EDUCAUSE Wireless Issues Community Group Listserv <
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> *On Behalf Of *Mike Fitzgerald
> *Sent:* Tuesday, Septem
gerald
Sent: Tuesday, September 07, 2021 12:16 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] [EXTERNAL] Re: [WIRELESS-LAN] Websites inaccessible
from wireless network - Aruba
Some people who received this message don't often get email from
fi...@brandeis.edu. Learn
Check your valid user table config to make sure you only allow the IP
ranges your DHCP server would give a wireless client. Otherwise, you can
end up with user table entries for destination IP's and then those IP's get
policed by the controller as you were seeing. Aruba default for that
config us
So. sigh!
It seems like an end client either statically or for some unknown reason
got assigned the IP address for these websites. The role that the client
was assigned had a policy to "deny" traffic to the internet (as per
design). The part that we did not know was that when a client is going
