Same result : (
BGP 1 Zebra.conf now
------------------------------
interface as1-eth0
ip address 10.0.0.2/24
interface as1-eth1
ip address 100.0.0.1/24
BGP 2 Zebra.conf now
-----------------------------
interface as2-eth0
ip address 20.0.0.2/24
interface as2-eth1
ip address 100.0.0.2/24
Below is the show route output
-------------------------------------------
mininext> as1 vtysh -c "show ip route"
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, A - Babel,
> - selected route, * - FIB route
C>* 1.1.1.0/24 is directly connected, lo
C>* 10.0.0.0/8 is directly connected, as1-eth0
C>* 10.0.0.0/24 is directly connected, as1-eth0
B>* 20.0.0.0/24 [20/0] via 100.0.0.2, as1-eth1, 00:01:16
C>* 100.0.0.0/24 is directly connected, as1-eth1
C>* 127.0.0.0/8 is directly connected, lo
mininext> as2 vtysh -c "show ip route"
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, A - Babel,
> - selected route, * - FIB route
C>* 2.2.2.0/24 is directly connected, lo
B>* 10.0.0.0/24 [20/0] via 100.0.0.1, as2-eth1, 00:02:02
C>* 20.0.0.0/8 is directly connected, as2-eth0
C>* 20.0.0.0/24 is directly connected, as2-eth0
C>* 100.0.0.0/24 is directly connected, as2-eth1
C>* 127.0.0.0/8 is directly connected, lo
Thanks,
On Wed, Aug 31, 2016 at 5:16 PM, Sami Halabi <[email protected]> wrote:
> Hi,
> add also in zebra.conf your second interface through 100.0.0.1/24 in bgp1
> and 100.0.0.2/24 in bgp2
>
> also show in vtysh in each router:
> show route
>
> Sami
>
> בתאריך 1 בספט׳ 2016 00:03, "Qing Wang" <[email protected]> כתב:
>
> Hi Sami,
>>
>> Thanks for the reply.
>>
>> I don't think you need redistribute-connected
>> Do you mean I dont need bgp redistribution, or I should use some other
>> redistribution option? I somehow still think we need bgp redistribution
>> though.
>>
>> after that alk should work
>> I am afraid it is still not working. Here is the bgpd.conf and zebra.conf
>> and netstat -nr as below:
>>
>> BGP1 bgpd.conf
>> ----------------------
>>
>> ! path logfile for bgpd daemon
>> log file /var/log/quagga/bgpd.log
>>
>> ! password for telnet authentication
>> password bgpuser
>>
>>
>> router bgp 100
>> bgp router-id 10.0.0.2
>> neighbor 100.0.0.2 remote-as 200
>> neighbor 100.0.0.2 next-hop-self
>> network 10.0.0.0/24
>>
>>
>> BGP 1 zebra.conf
>> -----------------------
>>
>> interface as1-eth0
>> ip address 10.0.0.2/24
>>
>>
>> BGP 1 netstat -nr
>> -----------------------
>> mininext> as1 netstat -nr
>> Kernel IP routing table
>> Destination Gateway Genmask Flags MSS Window irtt
>> Iface
>> 10.0.0.0 0.0.0.0 255.255.255.0 U 0
>> 0 0 as1-eth0
>> 10.0.0.0 0.0.0.0 255.0.0.0 U 0
>> 0 0 as1-eth0
>> 20.0.0.0 100.0.0.2 255.255.255.0 UG 0 0
>> 0 as1-eth1
>> 100.0.0.0 0.0.0.0 255.255.255.0 U 0
>> 0 0 as1-eth1
>>
>>
>>
>> BGP 2 bgpd.conf
>> -----------------------
>>
>> ! path logfile for bgpd daemon
>> log file /var/log/quagga/bgpd.log
>>
>> ! password for telnet authentication
>> password bgpuser
>>
>>
>> router bgp 200
>> bgp router-id 20.0.0.2
>> neighbor 100.0.0.1 remote-as 100
>> neighbor 100.0.0.1 next-hop-self
>> network 20.0.0.0/24
>>
>>
>>
>> BGP 2 zebra.conf
>> ------------------------
>>
>> interface as2-eth0
>> ip address 20.0.0.2/24
>>
>>
>> BGP 2 netstat -nr
>> -----------------------
>> mininext> as2 netstat -nr
>> Kernel IP routing table
>> Destination Gateway Genmask Flags MSS Window irtt
>> Iface
>> 10.0.0.0 100.0.0.1 255.255.255.0 UG 0 0
>> 0 as2-eth1
>> 20.0.0.0 0.0.0.0 255.255.255.0 U 0
>> 0 0 as2-eth0
>> 20.0.0.0 0.0.0.0 255.0.0.0 U 0
>> 0 0 as2-eth0
>> 100.0.0.0 0.0.0.0 255.255.255.0 U 0
>> 0 0 as2-eth1
>>
>>
>> Thanks,
>>
>>
>> Qing
>>
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Aug 31, 2016 at 4:05 PM, Sami Halabi <[email protected]> wrote:
>>
>>> Hi,
>>> I don't think you need redistribute-connected.
>>> in Bgp1 use: network 10.0.0.0/24
>>> in Bgp2 use: network 20.0.0.0/24
>>>
>>> also you need (you didn't mention it) to configure zebra.conf to
>>> configure your ip's, eg: in Bgp1:
>>> interface eth0
>>> ip address 10.0.0.3/24
>>>
>>> after that alk should work.
>>> if not show your bgpd.co f and zebra.conf and netstat -nr
>>>
>>> Sami
>>>
>>> בתאריך 31 באוג׳ 2016 04:47 PM, "Qing Wang" <[email protected]> כתב:
>>>
>>>> Hi there,
>>>>
>>>> I am trying to build up the following topology:
>>>>
>>>> H1 <----> OVS Switch1 < --- > Quagga BGP router 1 < ----- > Quagga BGP
>>>> Router 2 < --- > OVS Switch 2 < --- > H2.
>>>>
>>>> Basically I am trying to keep H1 and OVS1, BGP1 as a same subnet, same
>>>> thing for H2, OVS2 and BGP2. My goal is to make H1 and H2 be able to ping
>>>> each other. In order to do that, I think I need BGP redistribution in order
>>>> to exchange routing knowledge between BGP and Linux routing table.
>>>>
>>>> The problem is: after I did all above, I still not be able to ping from
>>>> H1 to H2. Currently, I can ping from H1 to BGP1 ( even the interface that
>>>> facing BGP 2 ), similarly I can ping from H2 to BGP2. I can also between
>>>> BGP routers, the BGP peer established the neighbor relationship and they
>>>> can advertise the network without a problem.
>>>>
>>>> More details:
>>>> 1 ) Nodes Info
>>>> H1: IP : 10.0.0.3
>>>>
>>>> BGP Router 1: 10.0.0.2 and 100.0.0.1
>>>>
>>>> BGP Router 2: 20.0.0.2 and 100.0.0.2
>>>>
>>>> H2 : 20.0.0.3
>>>>
>>>>
>>>> 2 ) Quagga Router bgpd.conf Info
>>>>
>>>> BGP router 1
>>>>
>>>> ! path logfile for bgpd daemon
>>>> log file /var/log/quagga/bgpd.log
>>>>
>>>> ! password for telnet authentication
>>>> password bgpuser
>>>>
>>>>
>>>> router bgp 100
>>>> bgp router-id 10.0.0.2
>>>> neighbor 100.0.0.2 remote-as 200
>>>> neighbor 100.0.0.2 next-hop-self
>>>> network 10.0.0.2
>>>> redistribute connected
>>>>
>>>> BGP Router 2
>>>>
>>>> ! path logfile for bgpd daemon
>>>> log file /var/log/quagga/bgpd.log
>>>>
>>>> ! password for telnet authentication
>>>> password bgpuser
>>>>
>>>>
>>>> router bgp 200
>>>> bgp router-id 20.0.0.2
>>>> neighbor 100.0.0.1 remote-as 100
>>>> neighbor 100.0.0.1 next-hop-self
>>>> network 20.0.0.2/24
>>>> redistribute connected
>>>>
>>>>
>>>> 3 ) Routing Table Info
>>>> mininext> h1 route -n
>>>> Kernel IP routing table
>>>> Destination Gateway Genmask Flags Metric Ref Use
>>>> Iface
>>>> 0.0.0.0 10.0.0.2 0.0.0.0 UG 0 0 0
>>>> h1-eth0
>>>> 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
>>>> h1-eth0
>>>>
>>>>
>>>>
>>>> BGP1 Routing Table:
>>>> mininext> as1 route -n
>>>> Kernel IP routing table
>>>> Destination Gateway Genmask Flags Metric Ref Use
>>>> Iface
>>>> 2.2.2.0 100.0.0.2 255.255.255.0 UG 1 0 0
>>>> as1-eth1
>>>> 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
>>>> as1-eth0
>>>> 20.0.0.0 100.0.0.2 255.255.255.0 UG 0 0 0
>>>> as1-eth1
>>>> 100.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0
>>>> as1-eth1
>>>>
>>>>
>>>> mininext> as1 vtysh -c "show ip bgp"
>>>> BGP table version is 0, local router ID is 10.0.0.2
>>>> Status codes: s suppressed, d damped, h history, * valid, > best, i -
>>>> internal,
>>>> r RIB-failure, S Stale, R Removed
>>>> Origin codes: i - IGP, e - EGP, ? - incomplete
>>>>
>>>> Network Next Hop Metric LocPrf Weight Path
>>>> *> 1.1.1.0/24 0.0.0.0 1 32768 ?
>>>> *> 2.2.2.0/24 100.0.0.2 1 0 200 ?
>>>> *> 10.0.0.0 0.0.0.0 0 32768 i
>>>> *> 10.0.0.0/24 0.0.0.0 1 32768 ?
>>>> *> 20.0.0.0/24 100.0.0.2 0 0 200 i
>>>> * 100.0.0.0/24 100.0.0.2 1 0 200 ?
>>>> *> 0.0.0.0 1 32768 ?
>>>>
>>>>
>>>> On AS1 node(BGP 1 I mentioned above), I can see the BGP does exchange
>>>> its neighbor information to the routing table as I use BGP redistribution.
>>>> So I currently have no clue where is incorrect, I think I might need some
>>>> help from here. If somebody can give some hint I will really appreciated,
>>>> thanks in advance!
>>>>
>>>>
>>>> Qing
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Quagga-users mailing list
>>>> [email protected]
>>>> https://lists.quagga.net/mailman/listinfo/quagga-users
>>>>
>>>>
>>
_______________________________________________
Quagga-users mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-users
