V4LESS-AS (AS215250) is a development ground for running an AS fully on IPv4-with-IPv6 Nexthop. For this purpose, V4LESS-AS is present at IXPs, where passive sessions for all neighbors at the IX are pre-configured. To start peering, just setup a session on your side.

Furthermore, V4LESS-AS hosts RIPE Atlas probes and NLNOG Ring Nodes to allow operators to introspect such a network.

Please reach out to noc@measurement.network if you encounter any issues.

Sponsoring an IXP Connection

If you want to bring AS215250 to an IXP near you, the following would be needed:

• Virtual or physical machine where we/you can install a custom VyOS build
  • 1 Core
  • 4GB Memory
• Backhaul VLAN or interface with a publicly routed IPv6 address
• Port to the IX

If you can provide this for an IXP, please drop an email to: noc@measurement.network

Network Information

PeeringDB: https://www.peeringdb.com/net/35836
BGP.tools: https://bgp.tools/as/215250
bgp.he.net: https://bgp.he.net/AS215250

IXes

Test-Cases

The following test-cases are configured in V4LESS-AS:

Prefix Hijack – RPKI Invalid / IRR Invalid

When configuring RFC8950 sessions, filters may not apply correctly due to v4 prefixes being learned over a v6 session.

To test for that, V4LESS-AS announces 193.31.54.0/24, which has a ROA for being originated by AS211286 (MSMT-NTWRK), as well a corresponding route object. You should not ingest this prefix.

All IPv4 addresses in this prefix respond to ICMP; If you can ping any IP in that network, you need to check your filters.

Forged Origin Prefix Hijack – Origin RPKI Valid / IRR Valid

When configuring RFC8950 sessions, filters may not apply correctly due to v4 prefixes being learned over a v6 session.

To test for that, V4LESS-AS advertises 193.31.55.0/24, pretending it was learned from AS211286. The prefix has a ROA for being originated by AS211286 (MSMT-NTWRK), as well a corresponding route object. As this is a forged origin hijack (AS211286 is not in AS215250’s AS-SET) you should not ingest this prefix.

All IPv4 addresses in this prefix respond to ICMP; If you can ping any IP in that network, you need to check your filters.

MTU1500 path, no IPv4 source address for ICMP on-path

In this setup, a node receives an IPv4 address via IPv4-with-IPv6 nexthop, and the path to all upstreams/peers has an MTU of 1500. All on-path routers do not have an IPv4 address, and originate ICMP packets from 192.0.0.8.

Resources:

NLNOG Ring node: v4less01.ring.nlnog.net
RIPE Atlas probe: https://atlas.ripe.net/probes/1007910/
Smokeping to DNS root: https://smkpng-mtu1500-no-v4icmp.dus01.v4less.measurement.network/

MTU1400 path, no IPv4 source address for ICMP on-path

In this setup, a node receives an IPv4 address via IPv4-with-IPv6 nexthop, and the path to all upstreams/peers has an MTU of 1400. All on-path routers do not have an IPv4 address, and originate ICMP packets from 192.0.0.8.

NLNOG Ring node: v4less02.ring.nlnog.net
RIPE Atlas probe: https://atlas.ripe.net/probes/1007911/
Smokeping to DNS root: https://smkpng-mtu1400-no-v4icmp.dus01.v4less.measurement.network/

MTU1500 path, IPv4 unicast source address for ICMP on-path

In this setup, a node receives an IPv4 address via IPv4-with-IPv6 nexthop, and the path to all upstreams/peers has an MTU of 1500. The last two hops use an dedicated unicast IPv4 address to originate ICMP packets.

NLNOG Ring node: v4less03.ring.nlnog.net
RIPE Atlas probe: https://atlas.ripe.net/probes/1007912/
Smokeping to DNS root: https://smkpng-mtu1500-v4icmp.ber01.v4less.measurement.network/

MTU1400 path, IPv4 unicast source address for ICMP on-path

In this setup, a node receives an IPv4 address via IPv4-with-IPv6 nexthop, and the path to all upstreams/peers has an MTU of 1400. The last two hops (around the MTU break) use an dedicated unicast IPv4 address to originate ICMP packets.

NLNOG Ring node: v4less04.ring.nlnog.net
RIPE Atlas probe: https://atlas.ripe.net/probes/1007913/
Smokeping to DNS root: https://smkpng-mtu1400-v4icmp.ber01.v4less.measurement.network/