RE: vpn6-mpls routes on BIRD 2

2018-08-23 Thread Arvin Gan
Hi ,
  From your protocols info, “BGP Next hop:   ::”  in channel vpn6-mpls, if next 
hop is empty, the route is withdrawn. Suggest to check it.

Best Regards,
Arvin Gan

From: Bird-users  On Behalf Of Chris Herdt
Sent: Friday, August 24, 2018 5:48 AM
To: bird-users@network.cz
Subject: vpn6-mpls routes on BIRD 2

Thanks to the list for all the help you've given me so far!

Another question: I am running BIRD 2.0.2 and peering with a host that is 
announcing vpn4 mpls and vpn6 mpls routes.

The vpn4 mpls routes are working, but all of the vpn6 mpls routes appear as 
withdrawn routes. I'm not sure why -- I looked at the packet capture in 
Wireshark and the UPDATE messages containing the IPv6 routes all show zero for 
Withdrawn Routes Length. Any ideas?

Here's the result of 'show protocols all peer1' (addresses changed):

bird> show protocols all peer1
Name   Proto  Table  State  Since Info
peer1  BGP---up 14:35:04.353  Established
  BGP state:  Established
Neighbor address: 192.168.42.1
Neighbor AS:  65321
Neighbor ID:  192.168.42.1
Local capabilities
  Multiprotocol
AF announced: vpn4-mpls vpn6-mpls
  Route refresh
  Graceful restart
  4-octet AS numbers
  Enhanced refresh
Neighbor capabilities
  Multiprotocol
AF announced: vpn4-mpls vpn6-mpls
  Route refresh
  Extended next hop
IPv6 nexthop: ipv4 ipv4-mc
  Graceful restart
Restart time: 120
AF supported: vpn4-mpls vpn6-mpls
AF preserved:
  4-octet AS numbers
Session:  internal multihop AS4
Source address:   192.168.100.1
Hold timer:   12.954/15
Keepalive timer:  0.005/5
  Channel vpn4-mpls
State:  UP
Table:  vpntab4
Preference: 100
Input filter:   ACCEPT
Output filter:  REJECT
Routes: 9771 imported, 0 exported
Route change stats: received   rejected   filteredignored   accepted
  Import updates:   9771  0  0  0   9771
  Import withdraws:   20  0--- 20  0
  Export updates:   9771   9771  0---  0
  Export withdraws:0---------  0
BGP Next hop:   192.168.100.1
IGP IPv4 table: master4
  Channel vpn6-mpls
State:  UP
Table:  vpntab6
Preference: 100
Input filter:   ACCEPT
Output filter:  REJECT
Routes: 0 imported, 0 exported
Route change stats: received   rejected   filteredignored   accepted
  Import updates:  0  0  0  0  0
  Import withdraws: 2785  0---   2785  0
  Export updates:  0  0  0---  0
  Export withdraws:0---------  0
BGP Next hop:   ::
IGP IPv6 table: master6


--
Chris Herdt
https://osric.com/chris/


vpn6-mpls routes on BIRD 2

2018-08-23 Thread Chris Herdt
Thanks to the list for all the help you've given me so far!

Another question: I am running BIRD 2.0.2 and peering with a host that is
announcing vpn4 mpls and vpn6 mpls routes.

The vpn4 mpls routes are working, but all of the vpn6 mpls routes appear as
withdrawn routes. I'm not sure why -- I looked at the packet capture in
Wireshark and the UPDATE messages containing the IPv6 routes all show zero
for Withdrawn Routes Length. Any ideas?

Here's the result of 'show protocols all peer1' (addresses changed):

bird> show protocols all peer1
Name   Proto  Table  State  Since Info
peer1  BGP---up 14:35:04.353  Established
  BGP state:  Established
Neighbor address: 192.168.42.1
Neighbor AS:  65321
Neighbor ID:  192.168.42.1
Local capabilities
  Multiprotocol
AF announced: vpn4-mpls vpn6-mpls
  Route refresh
  Graceful restart
  4-octet AS numbers
  Enhanced refresh
Neighbor capabilities
  Multiprotocol
AF announced: vpn4-mpls vpn6-mpls
  Route refresh
  Extended next hop
IPv6 nexthop: ipv4 ipv4-mc
  Graceful restart
Restart time: 120
AF supported: vpn4-mpls vpn6-mpls
AF preserved:
  4-octet AS numbers
Session:  internal multihop AS4
Source address:   192.168.100.1
Hold timer:   12.954/15
Keepalive timer:  0.005/5
  Channel vpn4-mpls
State:  UP
Table:  vpntab4
Preference: 100
Input filter:   ACCEPT
Output filter:  REJECT
Routes: 9771 imported, 0 exported
Route change stats: received   rejected   filteredignored
accepted
  Import updates:   9771  0  0  0
9771
  Import withdraws:   20  0---
20  0
  Export updates:   9771   9771  0
---  0
  Export withdraws:0------
---  0
BGP Next hop:   192.168.100.1
IGP IPv4 table: master4
  Channel vpn6-mpls
State:  UP
Table:  vpntab6
Preference: 100
Input filter:   ACCEPT
Output filter:  REJECT
Routes: 0 imported, 0 exported
Route change stats: received   rejected   filteredignored
accepted
  Import updates:  0  0  0
0  0
  Import withdraws: 2785  0---
2785  0
  Export updates:  0  0  0
---  0
  Export withdraws:0------
---  0
BGP Next hop:   ::
IGP IPv6 table: master6


-- 
Chris Herdt
https://osric.com/chris/


Re: Help with multiple routing tables.

2018-08-23 Thread Grant Taylor

On 08/23/2018 04:42 AM, Ondrej Zajicek wrote:

Hi


Hi Ondrej,

You can do it that way, or you can have just two tables, one for 
main_rib+RIP and another for default_rib, connect them with pipe that 
allows export in the direction from default to main but not in the other 
one, and have export filter for kernel protocol attached to main_rib 
(254) configurured to accept everything EXCEPT the default route.


Thank you for your reply.

Do you, or any other BIRD users, have any guidance / ProTips to suggest 
which method might be better long term?  Does one method (two tables vs 
three tables) potentially run into more problems or otherwise paint me 
into a corner down the road?




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature


Re: show route command syntax

2018-08-23 Thread Chris Herdt
On Wed, Aug 22, 2018 at 4:33 PM Maria Jan Matějka 
wrote:

> On August 22, 2018 8:40:16 PM GMT+02:00, Chris Herdt 
> wrote:
> > I'm using BIRD v2.0.2. I have successfully peered with another host
> > and am
> > receiving iBGP routes.
> >
> > bird> show route count
> > 0 of 0 routes for 0 networks in table master4
> > 0 of 0 routes for 0 networks in table master6
> > 9763 of 9763 routes for 9763 networks in table vpntab4
> > 0 of 0 routes for 0 networks in table vpntab6
> > Total: 9763 of 9763 routes for 9763 networks in 4 tables
> >
> > I can use 'show route all' to see all the routes (IP addresses
> > replaced):
> >
> > bird> show route all
> > Table vpntab4:
> > 192.168.100.0:24 192.168.42.199/32 unreachable [peer1 13:22:47.245
> > from
> > 192.168.12.3] * (100/-) [AS65321i]
> > Type: BGP univ
> > BGP.origin: IGP
> > BGP.as_path: 65321
> > BGP.next_hop: 192.168.100.0
> > BGP.local_pref: 100
> > BGP.originator_id: 192.168.100.0
> > BGP.cluster_list: 192.168.12.3 192.168.100.1
> > BGP.ext_community: (rt, 65123, 6)
> > BGP.mpls_label_stack: 54321
> > etc.
> >
> > However, I can't seem to figure out the syntax to retrieve a specific
> > route. E.g.:
> >
> > bird> show route for 192.168.42.199/32
> > Network not found
> >
> > Thanks in advance.
>
> Hello!
>
> You are using a vpn4 table so you should ask for a vpn4 prefix, like
>
> show route for 192.168.100.0:24 192.168.42.99/32
>
> I'm writing from my phone, not testing it. Anyway, it should work.
>
> Maria
>

That worked! Thanks for your help!

-- 
Chris Herdt
https://osric.com/chris/


Re: Help with multiple routing tables.

2018-08-23 Thread Ondrej Zajicek
On Wed, Aug 22, 2018 at 05:25:33PM -0600, Grant Taylor wrote:
> One for each kernel routing table (253 & 254) and the view that RIP has.
> 
> I think that I will need to import from the default_rib (253) into RIP -and-
> filter said default from RIP so that it doesn't get into the main_rib (254).
> 
> Or am I going to need a 3rd table inside of BIRD which does the following:
> 
>  - Imports all from main_rib (254)
>  - Exports all to main_rib (254) EXCEPT the default.
>  - Imports all from default_rib (253)
>  - Exports none to default_rib (253)

Hi

You can do it that way, or you can have just two tables, one for
main_rib+RIP and another for default_rib, connect them with pipe that
allows export in the direction from default to main but not in the other
one, and have export filter for kernel protocol attached to main_rib
(254) configurured to accept everything EXCEPT the default route.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santi...@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."