weizhouapache commented on PR #9964:
URL: https://github.com/apache/cloudstack/pull/9964#issuecomment-4989934930

   > > @wido the configuration looks ok, however. the VMs cannot reach the 
internet, even the default egress policy is `Allow`. I need more time to figure 
out what causes the issue. Would you mind moving this to next release (4.24.0) ?
   > 
   > Thanks for the test! Lets re-run the test and we can push this one for 
later.
   > 
   > In which env did you test it?
   
   @wido 
   I tested on my testing environment with BGP
   
   with the old ipv4 config
   ```
   r-269-VM# show bgp summary
   
   IPv4 Unicast Summary (VRF default):
   BGP router identifier 10.200.0.12, local AS number 10010 vrf-id 0
   BGP table version 3
   RIB entries 5, using 960 bytes of memory
   Peers 1, using 724 KiB of memory
   
   Neighbor        V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down 
State/PfxRcd   PfxSnt Desc
   10.200.0.1      4      64999         8         8        0    0    0 00:00:05 
           2        3 N/A
   
   Total number of neighbors 1
   ```
   
   
   with the new ipv4 config
   ```
   r-269-VM# show bgp summary
   
   IPv4 Unicast Summary (VRF default):
   BGP router identifier 10.200.0.12, local AS number 10010 vrf-id 0
   BGP table version 1
   RIB entries 1, using 192 bytes of memory
   Peers 1, using 724 KiB of memory
   
   Neighbor        V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down 
State/PfxRcd   PfxSnt Desc
   10.200.0.1      4      64999         5         3        0    0    0 00:00:07 
    (Policy) (Policy) N/A
   
   Total number of neighbors 1
   r-269-VM# 
   ```
   
   
   my bgp router (10.200.0.1) is also setup with frr. with the new ipv4 config, 
`show ip route` has the line
   ```
   B>* 192.168.120.0/28 [20/0] via 10.200.0.12, eth1, weight 1, 00:00:00
   ```
   
   this is missing with the new configuration


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to