If I get the chance to test that specific network again, I'd be happy to get hold of a windows environment and observe. However, I didn't see any indications that there were more clever things happening - I really do think its a case of muppet-config that just-works in windows, because windows is trusting that the gateway is on the LAN, whereas linux isn't.
So I don't think you *need* to tell that its really a /23: there are only two cases I can think of when adding the default route fails with no such process: - the dhcp config is more deeply broken than it looks, in which case a an explicit route to the gateway on the device will not make it worse :P (can't get more broken than broken) - the dhcp config is broken only to the point that the default gateway isn't in the subnet, in which case trusting the dhcp config to be accurate - that is that that ip is the right gateway and thus must be on the device's broadcast domain - will work. Testing a windows setup is probably very sensible, I'm entirely confident it will work though, based on when I did windows sysadminning :P -- support insane networks https://bugs.launchpad.net/bugs/250654 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
