Date: Sat, 31 Oct 2009 16:37:03 +0100 From: Sebastian Hyrwall <sh@keff.org> To: Nikos Vassiliadis <nvass9573@gmx.com> Cc: freebsd-net@freebsd.org Subject: Re: Hi. /31 on ethernet links Message-ID: <4AEC599F.90202@keff.org> In-Reply-To: <4AEC2297.40805@gmx.com> References: <4AEB7AE8.5090101@keff.org> <18C758A7-1908-4D1A-BDCA-80FF7FD8BC22@mac.com> <4AEB834D.1050907@keff.org> <BCE5F8B9-D52A-4F58-A5B9-DDDCF78B7D1B@mac.com> <4AEB911E.1070104@keff.org> <4AEC2297.40805@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Nikos Vassiliadis skrev: > Sebastian Hyrwall wrote: >> Chuck Swiger skrev: >>> inside, or using a /32 and an explicit default route via your >>> ethernet interface. >>> >> Unfortunetly that doesn't work. It just sets 192.1.1.2 as broadcast. >> >> Well wrapping a /31 inside of a /30 kinda defeats the purpose :) >> > > You could still use a /32 and then add a route for the other IP via > the ethernet interface. This is effectively the same with a /31. > Does not work, # ifconfig re0.212 172.16.25.10 netmask 255.255.255.255 # route add 172.16.25.11 -iface re0.212 add host 172.16.25.11: gateway re0.212 # ping 172.16.25.11 36 bytes from 172.16.25.10: Redirect Host(New addr: 172.16.25.11) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 bdbb 0 0000 40 01 0000 172.16.25.10 172.16.25.11
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AEC599F.90202>