Mailing List Archive

Redistribute into OSPFD from routing table 220
Hi,

When roadwarriors connect to my gateway strongswan injects routes into table 220

# ip ro sh table 220
10.21.5.6 via 1.2.3.4 dev eth0 proto static src 172.16.3.1

10.21.5.6 - IP assigned to roadwarrior
1.2.3.4 - external IP of VPN
172.16.3.1 - internal subnet of VPN accessible to roadwarriors and vice versa

This route is dynamically injected into table 220 (strongswan default).

Is it possible to redistribute this static route into quagga/ospfd?

[hypothetical]
distribute-list MYSTATICS out static

access-list MYSTATICS permit 10.21.5.0/24 [FROM table 220] <--- I made this up

[.I could change strongswan's routing table, but I'm trying to stick to
its defaults and figure out how to live with multiple routing tables]

Anthony

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: Redistribute into OSPFD from routing table 220 [ In reply to ]
I think the best option is for you to propose a patch so Strongswan
provides à route to zeba daemon (like BGP, OSPF, etc.) over the zapi.

Then you could do a "redistribute ike-routes" for instance into ospfd



_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: Redistribute into OSPFD from routing table 220 [ In reply to ]
Here's how I do it:

ip import-table 220
router bgp X
redistribute table 220

root@dell-s6000-02 ~/q/zebra# ip route show table 220
4.3.2.0/24 dev eth0 scope link
4.3.3.0/24 dev eth0 scope link
4.3.4.0/24 dev eth0 scope link
root@dell-s6000-02 ~/q/zebra#

root@dell-s6000-02 ~/q/zebra# vtysh

Hello, this is Quagga (version 0.99.24+cl3eau5).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

dell-s6000-02# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, P - PIM, T - Table, v - VNC,
V - VPN,
> - selected route, * - FIB route

T[220]>* 4.3.2.0/24 [15/0] is directly connected, eth0, 00:02:00
T[220]>* 4.3.3.0/24 [15/0] is directly connected, eth0, 00:02:00
T[220]>* 4.3.4.0/24 [15/0] is directly connected, eth0, 00:02:00

dell-s6000-02# show ip bgp
BGP table version is 17, local router ID is 6.0.0.11
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*> 4.3.2.0/24 0.0.0.0 0 32768 ?
*> 4.3.3.0/24 0.0.0.0 0 32768 ?
*> 4.3.4.0/24 0.0.0.0 0 32768 ?
*> 6.0.0.5/32 169.254.0.9 0 0 65101 ?

donald

On Thu, Nov 3, 2016 at 3:35 AM, Vincent Jardin <vincent.jardin@6wind.com> wrote:
> I think the best option is for you to propose a patch so Strongswan provides
> à route to zeba daemon (like BGP, OSPF, etc.) over the zapi.
>
> Then you could do a "redistribute ike-routes" for instance into ospfd
>
>
>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users@lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: Redistribute into OSPFD from routing table 220 [ In reply to ]
Hi Donald, interesting approach. What version of quagga has "ip import-table" ?



On Thu, Nov 3, 2016 at 8:35 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
> Here's how I do it:
>
> ip import-table 220
> router bgp X
> redistribute table 220
>
> root@dell-s6000-02 ~/q/zebra# ip route show table 220
> 4.3.2.0/24 dev eth0 scope link
> 4.3.3.0/24 dev eth0 scope link
> 4.3.4.0/24 dev eth0 scope link
> root@dell-s6000-02 ~/q/zebra#
>
> root@dell-s6000-02 ~/q/zebra# vtysh
>
> Hello, this is Quagga (version 0.99.24+cl3eau5).
> Copyright 1996-2005 Kunihiro Ishiguro, et al.
>
> dell-s6000-02# show ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP,
> O - OSPF, I - IS-IS, B - BGP, P - PIM, T - Table, v - VNC,
> V - VPN,
> > - selected route, * - FIB route
>
> K>* 0.0.0.0/0 via 10.0.0.1, eth0
> T[220]>* 4.3.2.0/24 [15/0] is directly connected, eth0, 00:02:00
> T[220]>* 4.3.3.0/24 [15/0] is directly connected, eth0, 00:02:00
> T[220]>* 4.3.4.0/24 [15/0] is directly connected, eth0, 00:02:00
> B>* 6.0.0.5/32 [20/0] via 169.254.0.9, swp31s0, 12:03:33
>
> dell-s6000-02# show ip bgp
> BGP table version is 17, local router ID is 6.0.0.11
> Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
> i internal, r RIB-failure, S Stale, R Removed
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 4.3.2.0/24 0.0.0.0 0 32768 ?
> *> 4.3.3.0/24 0.0.0.0 0 32768 ?
> *> 4.3.4.0/24 0.0.0.0 0 32768 ?
> *> 6.0.0.5/32 169.254.0.9 0 0 65101 ?
>
> donald
>
> On Thu, Nov 3, 2016 at 3:35 AM, Vincent Jardin <vincent.jardin@6wind.com> wrote:
>> I think the best option is for you to propose a patch so Strongswan provides
>> à route to zeba daemon (like BGP, OSPF, etc.) over the zapi.
>>
>> Then you could do a "redistribute ike-routes" for instance into ospfd
>>
>>
>>
>>
>> _______________________________________________
>> Quagga-users mailing list
>> Quagga-users@lists.quagga.net
>> https://lists.quagga.net/mailman/listinfo/quagga-users

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: Redistribute into OSPFD from routing table 220 [ In reply to ]
https://github.com/CumulusNetworks/quagga

Use the cmaster branch.

donald

On Thu, Nov 3, 2016 at 10:50 AM, Anthony Alba <ascanio.alba7@gmail.com> wrote:
> Hi Donald, interesting approach. What version of quagga has "ip import-table" ?
>
>
>
> On Thu, Nov 3, 2016 at 8:35 PM, Donald Sharp <sharpd@cumulusnetworks.com> wrote:
>> Here's how I do it:
>>
>> ip import-table 220
>> router bgp X
>> redistribute table 220
>>
>> root@dell-s6000-02 ~/q/zebra# ip route show table 220
>> 4.3.2.0/24 dev eth0 scope link
>> 4.3.3.0/24 dev eth0 scope link
>> 4.3.4.0/24 dev eth0 scope link
>> root@dell-s6000-02 ~/q/zebra#
>>
>> root@dell-s6000-02 ~/q/zebra# vtysh
>>
>> Hello, this is Quagga (version 0.99.24+cl3eau5).
>> Copyright 1996-2005 Kunihiro Ishiguro, et al.
>>
>> dell-s6000-02# show ip route
>> Codes: K - kernel route, C - connected, S - static, R - RIP,
>> O - OSPF, I - IS-IS, B - BGP, P - PIM, T - Table, v - VNC,
>> V - VPN,
>> > - selected route, * - FIB route
>>
>> K>* 0.0.0.0/0 via 10.0.0.1, eth0
>> T[220]>* 4.3.2.0/24 [15/0] is directly connected, eth0, 00:02:00
>> T[220]>* 4.3.3.0/24 [15/0] is directly connected, eth0, 00:02:00
>> T[220]>* 4.3.4.0/24 [15/0] is directly connected, eth0, 00:02:00
>> B>* 6.0.0.5/32 [20/0] via 169.254.0.9, swp31s0, 12:03:33
>>
>> dell-s6000-02# show ip bgp
>> BGP table version is 17, local router ID is 6.0.0.11
>> Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
>> i internal, r RIB-failure, S Stale, R Removed
>> Origin codes: i - IGP, e - EGP, ? - incomplete
>>
>> Network Next Hop Metric LocPrf Weight Path
>> *> 4.3.2.0/24 0.0.0.0 0 32768 ?
>> *> 4.3.3.0/24 0.0.0.0 0 32768 ?
>> *> 4.3.4.0/24 0.0.0.0 0 32768 ?
>> *> 6.0.0.5/32 169.254.0.9 0 0 65101 ?
>>
>> donald
>>
>> On Thu, Nov 3, 2016 at 3:35 AM, Vincent Jardin <vincent.jardin@6wind.com> wrote:
>>> I think the best option is for you to propose a patch so Strongswan provides
>>> à route to zeba daemon (like BGP, OSPF, etc.) over the zapi.
>>>
>>> Then you could do a "redistribute ike-routes" for instance into ospfd
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Quagga-users mailing list
>>> Quagga-users@lists.quagga.net
>>> https://lists.quagga.net/mailman/listinfo/quagga-users

_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users