29 Mar
2013
29 Mar
'13
2:13 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29/03/2013 19:59, Brian Kantor wrote:
Should be. When routing, the narrowest match is
supposed to be
found first, so it should work. Give it a try and we'll see.
As far as I can tell it works.
There is a route 44.161.0.0/16 for LX, but I have been experimenting
with longer (more specific) prefixes (44.161.229.0/25,
44.161.202.0/24, 44.161.203.0/24) and it works fine (so far) within
the IPIP mesh.
The only thing you might need to test is connectivity from the network
with the shorter prefix towards the network with the longer prefix.
The gateway with the covering (shorter) prefix might be configured to
handle this traffic locally instead of forwarding it via the IPIP mesh
or a direct interconnect or ...
You may also want to handle the occasional packet arriving at the
wrong gateway and forward it to the other gateway.
73 de Marc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRVefWAAoJEHFIN1T8ZA8v2D0P/iReTlR5JEy+HSGtoobDFe6d
1y8i0z4GwYizQfhUGaYMKQvT1hmhB8akGLocoJ30xiHKTYPoC6AOklCy6v+js/rk
aQ00ya76MmKM0auLuNi+DVjfSdB4UjjerNuHGJta9+VRAtt0Q2yS09VP5h6DUUbV
zuXDl3lgOzLg37UuYWweICJudtK0bXuJx7pIWlZg6DRTXGIVzX1J1PEDfwv8/Mw7
AwYW1L1QMU6laJ7H08uEBJI2YNJC//49vCF3NT79ivJ4sGtgj13Wa1x6DQ+9UJAu
uiuXOVwV5wF5qRMMbHDOkHGxvlaHax6x6sjt9v9BoUyJvuQl/U7d10+k+05OZbS0
3kijbvPQ3k09MgzqcDKqdrG3OzCKH1c7HH8TTi3PblTxXDnYWqUwzPk7qzIBg1zo
nx6IX5DUDZ74UohdCfHJ6yU0wtaXImU3+5T0mH0BmabiZaA90EDJ1ylnbH9MakWb
AK8ILZJXS9vMuzZJks+la/EVoqgkguu+L7NR9nfO9BgnkmU16+tJXwxYGfZSUx5X
a+5sYHdyEd6WFf/hzVohKpyBCogplO/BiyFzCxXeojUVaptchafp5vb36MzoKqIW
79lWeokowuBcpzRpw4/XHQ3YC5c0W60YTyDsM/KXYEM+4BmDzPNnuNi3zcm6Hdh4
5R5YsmkzNaSjxSgtTQCj
=YBum
-----END PGP SIGNATURE-----