Getting martian source errors in kernel and dropping network

[dr_techno (Dave Mikeska)]

@phane

For now, I don’t see cascading martian source errors, just one set of them from my Xbox One since I did the factory reset. I’m hoping that the buggy firmware may have just had an issue before and doing the full reset may have resolved it.

it could be an effect of the xbox trying upnp. Which is something that needs to be refined everywhere including all manufactured routers. At least with this system you see any error that occurs.

[phane (James Redel)]

@dr_techno

It should be fine then because once the static entry is put in the router its going to keep it. Because there is a bug in their firmware because the 1st one in the chain has to get a static so the others link properly and when it does you will be able to use the dns name that goes back to the 1st one which it sounds like what you ended up with. On their OS, they suppose to show the static address of the first node here on the network screen but it doesn’t. I don’t think it has an ssh server to log into its version of Linux/BSD to actually look at how the net is set up. But working backwards seemed to solve the issue since the static address doesn’t go away when resetting it.

The IP is being automatically picked up through DHCP via IPFire. I have IPFire’s DHCP configured with fixed lease IP’s for each node of .2, .3, and .4. (These are outside the DHCP server’s range for dynamic leases). It was set up this way before the factory reset as well. I know that each node is getting the .2, .3, and .4 since when I point to those addresses with a web browser, they are automatically redirecting me to .2 (the main node). They also show up with those IP addresses in the Linksys app.

You’ll note in the screenshot above, that it even pulled the domain name (redel) from IP Fire’s DHCP. There is no way to set it up in Bridge Mode and bypass the DHCP client without updating to a custom firmware, AFAIK. It is, however, not running a DHCP server and wireless clients are getting their correct IP’s from IPFire (as they were before the reset).