All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
BGP vyos.
Hello everyone! I'm trying to set up a BGP session and it seems I can't get it right no matter what I do. I'm not that skilled, so please, if you can help me figure out where I went wrong.
Im:
1. vps ip. 103.105.111.xx
2. iptransit from freetransit.ch;
my-ip 2a01:20e:1001:139::2/64
neighibor ip 2a01:20e:1001:139::1/64
my asn 215126
neighibor asn 41051
my ip 103.105.111.xx
endpoint 5.226.149.zz
tunnel type gree
3. my ipv6 ip 2a14:7581:7a00::/39
I made the following configuration:
set interfaces tunnel tun0 encapsulation gre
set interfaces tunnel tun0 address 2a01:20e:1001:139::2/64
set interfaces tunnel tun0 local-ip 103.151.111.XX
set interfaces tunnel tun0 remote-ip 5.226.149.zz
commit
save
exit
show interfaces tunnel tun0
tun0@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1476 qdisc noqueue state UNKNOWN group default qlen 1000
link/gre 103.151.111.XX peer 5.226.149.zz
inet6 2a01:20e:1001:139::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::fd45:77ff:feef:aaa6/64 scope link
valid_lft forever preferred_lft forever
RX: bytes packets errors dropped overrun mcast
2781606906 1125282 0 0 0 0
TX: bytes packets errors dropped carrier collisions
58769465 811749 0 0 0 0
.
set protocols bgp system-as 215126
set protocols bgp parameters router-id 103.151.111.XX
set protocols bgp neighbor 2a01:20e:1001:139::1 address-family ipv6-unicast
set protocols bgp address-family ipv6-unicast network 2a14:7581:7a00::/39
set protocols bgp neighbor 2a01:20e:1001:139::1 remote-as 41051
set protocols bgp neighbor 2a01:20e:1001:139::1 update-source tun0
commit
save
exit
show bgp summary
IPv6 Unicast Summary (VRF default):
BGP router identifier 103.151.111.XX, local AS number 215126 vrf-id 0
BGP table version 206102
RIB entries 389545, using 36 MiB of memory
Peers 1, using 20 KiB of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd PfxSnt Desc
2a01:20e:1001:139::1 4 41051 53483 53283 206102 0 0 00:00:23 205863 205864
So far, from what I can see, it seems to be okay. As I mentioned, I'm not that well-trained... The problem is that the ping doesn't work either from the server with IP 2a14:7581:7a00::1 or to it.
Comments
I am not familoar with vyos, but seems like the session is up. Can you check if routes are correct, what is the traceroute from/to announced network
Also ensure that there is no firewall configured to discard icmpv6 echo-request
I receive a lot of routes; I have also checked if the class is announced, and it is okay. The only explanation I can think of is the firewall, which I need to start learning how to configure. What is strange is that I tried the same session with FRR, BIRD, and Quagga on Debian, Ubuntu, and AlmaLinux, and I had the same result.
@pedala
Can you dm me a running config output ? ( please do not put it here publicly)
Can have a look at it later today
As I can see, there is no prefix 2a14:7581:7a00::/39 visible globally
Also it looks not okay for me:
Seems like you readvertise received routes + 1 additional. I would highly suggest you to implement import/export filters