On Mon, 2016-01-11 at 15:14 +0100, Guus Sliepen wrote: > On Mon, Jan 11, 2016 at 01:29:19PM +0000, Sam Morris wrote: > > > On Sun, 2016-01-10 at 22:33 +0100, Guus Sliepen wrote: > > > This is neither a bug in the installer or in ifupdown; a default > > > gateway should always be inside the local network. It is the kernel > > > that refuses to accept such a gateway route. > > > > > I'm not sure I follow. If the kernel rejects the gateway then how come > > > it's possible to configure this manually? It's been a while since I > > > filed the original bug but I'm pretty sure the problem was with the > > > installer rejecting the configuration provided by 1and1's DHCP server. > > What happens is that the moment the DHCP client tries to add the gateway > route, there is no route to the gateway itself. That causes it to reject > the gateway route. > > If you manually add a route to the gateway, then sure you can also > manually add the gateway route. > > Hm, I can make ifupdown force the addition of the gateway route, but > only for statically configured interfaces. For inet dhcp, it's the DHCP > client itself that adds the routes, ifupdown has no influence over it. > One could modify /sbin/dhclient-script to do that though...
I guess that'd be a separate bug against isc-dhcp-client. Unfortunately I can't actually test any modifications since I've moved on from 1and1. (Though I might be able to try to replicate their DHCP setup with a couple of VMs... I'll file a separate bug for that if I get some time to fiddle around with it). But perhaps if the modifications to the installer to make configuring the network manually aren't too risky then I think they'd be worth making. Anyway, thanks for looking at this rather ancient bug... I had forgotten that I ever filed it! :) -- Sam Morris <https://robots.org.uk/> CAAA AA1A CA69 A83A 892B 1855 D20B 4202 5CDA 27B9
signature.asc
Description: This is a digitally signed message part
