Odd network behavior

[Xen]

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).

Thank me later, honey-bun. No, just kidding, I don't know if that's 
true.

I might be wrong about this you know.

But anyway.

(I mean there was recently a guy on a Dutch computer forum that saw his 
main router start power cycling when he connected an access point on the 
attic. It seems the exact same problem but I don't know how he solved 
it. I could look it up).

Regards,

(and pardon me for any allusions)

Xen.