Odd network behavior

[Colin Law]

On 1 August 2017 at 09:33, Xen <list at xenhideout.nl> wrote:
> rikona schreef op 01-08-2017 6:07:
>>
>> I'm seeing some odd network behavior that I don't understand.
>
>
> You've also not said, as Colin points out, how the second router is really
> connected.
>
> I assume it is really connected with its uplink to the main network, and
> that it is doing NAT on its own behalf?
>
> Typically... if you don't want the second router to do any routing... I mean
> that the wireless connection is usually bridged to the regular LAN ports of
> that router, so you don't have to use the uplink port.
>
> Therefore, you could simply use it as an access point by only using the
> LAN-connected ports of said router and not the actual "routed" port, which
> is also what I am doing.
>
> Ie. I have some second router plugged into the main router using its
> ordinary ports and it works just fine, it has an IP address but doesn't do
> anything with it (except allowing me to configure it).
>
> So this router doesn't have any sort of WAN connection.
>
> If you are going to use the same SSID then both clients have to be able to
> reach the same server doing DHCP. You say you have this. But they also need
> to have the same router, so the secondary router must only be pass-through
> (like I said).

All of those points may well be valid, but still nothing that the OP
has done should cause the router to crash and reset, so that still
suggests a bug in the router. I had one that worked perfectly well for
years, then I got a new phone and every time that phone connected the
router reset. I updated the firmware and all was well again.

Colin