I have seen this before with consumer routers.
Not sure exactly how it sees the wan interface upon boot, but I am
sure its looking for the RFC1918 address on that interface.
I think it may be a discovery protocol like igmp and you may be able to
set up a rule to drop that traffic from entering the bridge.
On 09/30/2015 02:26 PM, Nate Burke wrote:
There are private address on the interface, but not setup in DHCP.
On 9/30/2015 11:58 AM, David wrote:
Do you have any private ip addresses assigned to that bridge
interface on the tower?
On 09/30/2015 10:25 AM, Nate Burke wrote:
Rogue DHCP Detection is setup, Needed with radios with no filters.
No Rogue DHCP Detected.
On 9/30/2015 10:07 AM, David wrote:
Nate,
Set up tower gateway to detect rouge dhcp server on the bridge
interface and see if there is
router facing the wrong way.
This happens because of DOH! moments of customers and if you have
a CPE that doesnt have any filtering for this
its a bummer
On 09/30/2015 08:57 AM, Nate Burke wrote:
I've been running into issues recently with SOHO routers deciding
that they need to be in Bridge mode instead of Nat Mode. It seems
like there is something with how they're detecting the connection
when they're setup. I'm not doing anything special. DHCP Assigns
a Public IP Address from the tower. Although it seems to be more
of an issue with EPMP than FSK/450. Has anyone else seen this, or
Dug deeper into it?
Last night I was working with a Customer who had an Netgear N300
that was in bridge mode (Customer and router <1 week old). I had
him Default the router, and it came up in router mode (Single MAC
in the bridge table, and got a DHCP Lease). He said his computer
was connected to the WIFI, but was showing limited connection.
He's never logged into the router, so I don't think he changed the
setup. This morning, it's back in bridge mode. I'm sending him a
RB951 to get him online, but why would the router choose bridge mode?
I think I've also seen this with a Linksys, but I thought the
customer had done something before I got there. Now I'm not sure.
