On Tue, Jun 12, 2018 at 06:01:49PM -0400, Kenneth R Westerback wrote:
> On Sun, Jun 10, 2018 at 02:15:09PM -0400, Kenneth R Westerback wrote:
> > On Sat, Jun 09, 2018 at 02:10:09PM +0200, Claudio Jeker wrote:
> > > On Sat, Jun 09, 2018 at 01:31:20PM +0200, Martin Pieuchot wrote:
> > > > On
On Sun, Jun 10, 2018 at 02:15:09PM -0400, Kenneth R Westerback wrote:
> On Sat, Jun 09, 2018 at 02:10:09PM +0200, Claudio Jeker wrote:
> > On Sat, Jun 09, 2018 at 01:31:20PM +0200, Martin Pieuchot wrote:
> > > On 08/06/18(Fri) 18:06, Kenneth R Westerback wrote:
> > > > Testing at the alternate
>>This cannot possibly work, the client can't find the
lladdr of the gateway
Oops, I now see my experiment was not valid: dhcpcd adds route to router but
can't reach it.
I added alias and it now works, thank you.
So, dhcp client assumes that router anounced by server is always reachable
by
On 2018/06/11 07:39, Il Ka wrote:
> >Which RFC?
> It says "IP addresses for routers on the client's subnet", so my idea was
> that router must be on client subnet.
>
> >We already deal with this for the case fairly common in VPS where the
> >client gets a /32 with a router outside the subnet
>
>Which RFC?
It says "IP addresses for routers on the client's subnet", so my idea was
that router must be on client subnet.
>We already deal with this for the case fairly common in VPS where the
>client gets a /32 with a router outside the subnet
But how does it work from client side?
Does your
On 2018/06/10 13:20, Il Ka wrote:
> Another approach is to extend subnet by decreasing mask to include router to
> client subnet.
> I.e.: 10.112.38.73/16.
I think that's the wrong approach, because it will send packets directly
to addresses which should be sent to the router.
> From my point of
I just checked how openbsd dhcpd handles this:
subnet 10.10.10.0 netmask 255.255.255.0 {
option routers 20.10.10.1;
range 10.10.10.10 10.10.10.50;
}
It starts fine and happily sends unusable configuration to client.
dhcpcd (dhcp client I use on linux-based client) installed
Another approach is to extend subnet by decreasing mask to include router to
client subnet.
I.e.: 10.112.38.73/16.
dhcp-options(5), RFC-2132: "The router option specifies a list of IP
addresses for routers on the client's subnet."
>From my point of view dhcp server in your example violates RFC,
