search

scion-backbone / sbas

Prototype implementation for the Secure Backbone AS (SBAS) routing system.
0 stars 1 forks source link

WireGuard endpoints on SBAS nodes are broken #10

Closed joelwanner closed 3 years ago

joelwanner commented 3 years ago

It looks like there's an issue with the routes:

scionlab@scionlab-1009-aristotle:~/sbas-proto/node$ ping 184.164.236.129
PING 184.164.236.129 (184.164.236.129) 56(84) bytes of data.
From 10.99.0.3: icmp_seq=2 Redirect Host(New nexthop: 10.99.0.2)
From 10.99.0.2: icmp_seq=2 Redirect Host(New nexthop: 10.99.0.1)
From 10.99.0.3: icmp_seq=3 Redirect Host(New nexthop: 10.99.0.2)
From 10.99.0.2: icmp_seq=3 Redirect Host(New nexthop: 10.99.0.1)
From 10.99.0.3: icmp_seq=4 Redirect Host(New nexthop: 10.99.0.2)
From 10.99.0.2: icmp_seq=4 Redirect Host(New nexthop: 10.99.0.1)
^C
--- 184.164.236.129 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4079ms
birgelee commented 3 years ago

I think this is related to the IP routing changes I made to give the router an IP address on the wireguard network. This will be fixed when we merge the containers.