BGP on GRE Idle
Ondrej Zajicek
santiago at crfreenet.org
Tue Aug 3 16:33:06 CEST 2021
On Sun, Aug 01, 2021 at 11:32:42PM +0800, 智慧雨泽 wrote:
> Hi,My configuration file can work normally on the wireguard tunnel, but GRE
> does not work.
>
> Server1
>
> 11: home_1_vpn: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue
> state UNKNOWN group default qlen 1000
> link/none
> inet 5.101.92.125/32 scope global home_1_vpn
> valid_lft forever preferred_lft forever
> root at ll-ix:~# ip route get 2602:feda:ab4:5247:5247:5247:5247:5247
> 2602:feda:ab4:5247:5247:5247:5247:5247 from :: dev frc_ca src
> 2602:feda:ab2:5247:5247:5247:5247:5247 metric 1024 pre
> f medium
Hi
I guess the issue is that this GRE link does not have the prefix
configured as a regular address range (is not shown in 'ip addr show'),
thus BGP neighbor IP is not considered a direct neighbor and BIRD BGP is
waiting for it to appear.
You can either add such prefix to the GRE iface, or just use 'multihop'
instead of 'direct' (as neighbor is reachable through routing table).
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
More information about the Bird-users
mailing list