[atlas] Probe on a /31 or /32 IPv4 network

Hi,

We would like to deploy our Atlas probe on a separate L2 network, but
without having to spend 4 IPv4 addresses (i.e. a /30 network).

Using a /31 would be nice, but the web UI doesn't allow it as static IPv4
configuration ("The Gateway address should be different from the ending
network address").  Would it be possible to allow /31 in the web UI?
I believe the probes themselves support it.

Even nicer would be support for /32 networks, even though it is perhaps
less usual.  This can easily be done with iproute2 on Linux, assuming the
probe is 192.0.2.48/32 and its gateway is 192.0.2.1:

  ip addr add 192.0.2.48/32 dev eth0
  ip route add 192.0.2.1/32 dev eth0
  ip route add default via 192.0.2.1

or even shorter:

  ip addr add 192.0.2.48/32 dev eth0
  ip route add default via 192.0.2.1 onlink dev eth0


Using a gateway that is not on the same subnet doesn't sound very nice,
but again, the goal is to avoid wasting precious IPv4 space.

Thanks,
Baptiste
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-atlas/attachments/20140814/b1a99014/attachment.sig>