Like I said in the email from yesterday:
So, I did some testing on my Windows laptop with a static IP set, connected via Cat 5 to my client bridge router. And guess what? Low and behold, when the client bridge router is power cycled it completely loses DNS also and the static route doesn't ever get reinstated. I can see the network interface come back up in Windows (animation in the tray) once the router is plugged back in, but whatever routing table that was between the 2 DD-WRT routers gets hosed when the client bridge router gets cycled. If set to DHCP, there's no problem. I'm not sure if this is just the limits of having a client bridge setup and having a main router serve DHCP to the wired clients on the client bridge router, or if it's some DD-WRT bug.
Btw, in Client Bridge (Routed Mode) the Network Address Server Settings (DHCP) in DD-WRT option goes away, so it looks as if the main router will always be the one to serve DHCP. I thought about trying to see if there was an option to have the client bridge router be a DHCP server but that's not possible.
On the main router, "Use DNSMasq for DHCP" and "Use DNSMasq for DNS" are both ticked; those are the DD-WRT defaults so I left them alone. So since this appears to not only be happening with Wicked but also with Windows, it's looking like this has something to do with the client bridge setup I have. Later I am going to try plugging the Windows laptop directly into the main router with a static IP, and unplug that router and see what happens when it comes back up. So for the record, it looks like it's not Wicked, it's something finicky with DD-WRT client bridge mode setup. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org