Queue your best Homer Simpson for this one…. *DOH* !!!!!!!!!!!!!!!!!!!!!!
Thanks !!! > On 28/04/2019, at 8:07 AM, Alexander Zubkov <[email protected]> wrote: > > Try this: > show route all 192.168.7.0/24 > > On Sat, Apr 27, 2019 at 9:54 PM Pieter De Wit <[email protected]> wrote: >> >> Sorry, I did forget that off the email: >> >> bird> show route 192.168.7.0/24 >> 192.168.7.0/24 via 10.255.255.101 on ppp1 [bgp_site_1 07:50:22] * (100) >> [AS65101i] >> >> Should that last section not contain all the numbers ? >> >> That command was ran on the VPN server btw :) >> >> >>> On 28/04/2019, at 7:50 AM, Alexander Zubkov <[email protected]> wrote: >>> >>> Hi, >>> >>> Why do you think there are no prepends? Have you look at the receiving >>> side what is sent? >>> >>> On Sat, Apr 27, 2019 at 9:16 PM Pieter De Wit <[email protected]> wrote: >>>> >>>> Hi Everyone, >>>> >>>> I have been fighting with this now for a while and I can’t seem to get my >>>> paths prepended. I am running 1.6.3 from the Ubuntu repo. >>>> >>>> Network wise, I have a VPN server that takes VPNs from remote sites. This >>>> VPN server exports the ranges to the rest of the network. It learns the >>>> connected sites from a Raspberry PI on site. These links are used as >>>> backup paths :) >>>> >>>> Here is the BGP config on the server, from a remote site: >>>> >>>> The filters basically just restrict it to RFC1918 addresses >>>> >>>> protocol bgp bgp_site_1 { >>>> description “site_1"; >>>> local as 65001; >>>> neighbor 10.255.255.101 as 65101; >>>> import filter remote_sites; >>>> export filter export_to_remote_sites; >>>> } >>>> >>>> Here is the config on the remote site: >>>> >>>> filter prepend_path { >>>> bgp_path.prepend(65101); >>>> bgp_path.prepend(65101); >>>> bgp_path.prepend(65101); >>>> accept; >>>> } >>>> >>>> protocol bgp itc_vpn { >>>> description "ITC VPN"; >>>> local as 65101; >>>> neighbor 10.255.255.1 as 65001; >>>> import all; >>>> export filter prepend_path; >>>> } >>>> >>>> What am I missing ? >>>> >>>> Thanks ! >>> >> >
