RARE user and assistance email list

[Gabriel Tetzner <gabrieltetznermenegueti16@gmail.com>]

Hi all,

I managed to solve it with Csaba's tip to isolate the vrf, I used the EIGRP protocol and configured the routing issue:

Now 20.0.0.3 ping 10.0.0.3:

freertr-3:

sh int tun1:

tunnel1 is up      
 description:      
 state changed 17 times, last at 2022-08-24 21:42:28, 2d0h ago
 last packet input 00:00:02 ago, output 00:00:02 ago, drop never ago
 type is wireguard, hwaddr=none, mtu=1400, bw=8000kbps, vrf=wireguard
 ipv4 address=20.0.0.3/24, mask=255.255.255.0, ifcid=150335649
 received 33024 packets (2180896 bytes) dropped 0 packets (0 bytes)
 transmitted 1193 packets (74066 bytes) macsec=false sgt=false

freertr#ping 10.0.0.3 vrf wireguard                                            
pinging 10.0.0.3, src="null," vrf=wireguard, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
!!!!!
result=100.0%, recv/sent/lost/err=5/5/0/0, took 726, min/avg/max/dev rtt=143/144/150/7.4, ttl 254/254/254/0.0, tos 0/0.0/0/0.0

The reverse is also possible:

freertr-r2:

freertr#sh int tun1                                                            
tunnel1 is up
 description:
 state changed 21 times, last at 2022-08-26 21:13:09, 00:55:27 ago
 last packet input 00:00:03 ago, output 00:00:03 ago, drop never ago
 type is wireguard, hwaddr=none, mtu=1400, bw=8000kbps, vrf=wireguard
 ipv4 address=10.0.0.3/24, mask=255.255.255.0, ifcid=906822900
 received 30063 packets (1989950 bytes) dropped 0 packets (0 bytes)
 transmitted 1298 packets (80644 bytes) macsec=false sgt=false

freertr#ping 20.0.0.3 vrf wireguard                                            
pinging 20.0.0.3, src="null," vrf=wireguard, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
!!!!!
result=100.0%, recv/sent/lost/err=5/5/0/0, took 717, min/avg/max/dev rtt=143/143/145/0.6, ttl 254/254/254/0.0, tos 0/0.0/0/0.0

Now I am left with a question, how do I make the debian machine in freeRtr-r3 ping the ip of the freeRtr-2 tunnel?

In this topology consider that there is a prometheus server running on top of freeRtr-r3 debian and I need to talk to 10.0.0.3?

Can anyone help me?

Thanks...

Em sex., 26 de ago. de 2022 às 04:03, Gabriel Tetzner via groups.io <gabrieltetznermenegueti16=gmail.com@groups.io> escreveu:

anybody?

Em qua., 24 de ago. de 2022 às 12:40, mc36 <cs@mp.ls> escreveu:

anybody?


On 8/18/22 18:09, Gabriel Tetzner wrote:
> Hi all,
>
> I have the following topology built using two wireguard tunnels:
>
> image.png
>
> In this case freertr-r3 is isolated on another network, but has a public ip to tunnel wireguard with freertr-r1 which is also on another network and has a public ip.
>
> This topology is working and the pings respectively for each ip:
>
> 10.0.0.2 ping 10.0.0.3
> 20.0.0.2 ping 20.0.0.3
> 10.0.0.3 ping 10.0.0.2
> 20.0.0.3 ping 20.0.0.2
>
> But I want 20.0.0.2 to reach 10.0.0.3, do I need to configure a route for this using ipv4 route? or is there another way to route the traffic? in this case I am talking about
> freertr-r1.
>

_._,_._,_

---

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#616) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [gabrieltetznermenegueti16@gmail.com]

_._,_._,_