Router and VMs can't ping network node and internet.

asked 2017-09-29 02:21:28 -0600

VladF gravatar image

I can't ping network ip from ip netns ROUTER_NAME exec ping 192.168.253.243 and I can't ping router external interface from network node too.

 [root@server1 ~(keystone_admin)]# ovs-vsctl show
397c85d7-d708-48a9-b8b2-3bb654808993
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        **Port "qg-c0c30b6d-e4"  //external router i-face 192.168.253.253
            tag: 3
            Interface "qg-c0c30b6d-e4"
                type: internal**
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port "qvo2aa3bd9e-d1"
            tag: 2
            Interface "qvo2aa3bd9e-d1"
        Port br-int
            Interface br-int
                type: internal
        Port "tap71521b57-40"
            tag: 3
            Interface "tap71521b57-40"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "qr-f2f9c695-67"
            tag: 4095
            Interface "qr-f2f9c695-67"
                type: internal
        Port "tap1cac6ebf-95"
            tag: 2
            Interface "tap1cac6ebf-95"
                type: internal
        **Port "qr-506b3f2a-e2"    //internal router interface
            tag: 2
            Interface "qr-506b3f2a-e2"
                type: internal**
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port "vxlan-c0a8fd18"
            Interface "vxlan-c0a8fd18"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="192.168.253.243", out_key=flow, remote_ip="192.168.253.24"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port "ens32"
            Interface "ens32"
        Port br-ex
            Interface br-ex
                type: internal
    ovs_version: "2.7.2"



   ----------Netns list from network node--------------
   [root@server1 ~(keystone_admin)]# ip netns list
    **qdhcp-684cde83-acf4-48ca-8315-7a3256a5f781**
    qrouter-94df80e1-d5c8-4be0-a337-dcaca4ce3783  // This is my router namespace
    qdhcp-25c04662-ef74-431b-85ee-70733f809f5e


  ----------ip a from router namespace--------------
  [root@server1 ~(keystone_admin)]# ip netns exec qrouter-94df80e1-d5c8-4be0-a337-dcaca4ce3783 ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    22: qr-506b3f2a-e2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN qlen 1000
        link/ether fa:16:3e:d9:84:3c brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.1/24 brd 192.168.1.255 scope global qr-506b3f2a-e2
           valid_lft forever preferred_lft forever
        inet6 fe80::f816:3eff:fed9:843c/64 scope link 
           valid_lft forever preferred_lft forever
    29: qg-c0c30b6d-e4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN qlen 1000
        link/ether fa:16:3e:9b:fa:16 brd ff:ff:ff:ff:ff:ff
        inet 192.168.253.253/24 brd 192.168.253.255 scope global qg-c0c30b6d-e4
           valid_lft forever preferred_lft forever
        inet 192.168.253.252/32 brd 192.168.253.252 scope global qg-c0c30b6d-e4
           valid_lft forever preferred_lft forever
        inet6 fe80::f816:3eff:fe9b:fa16/64 scope link 
       valid_lft forever preferred_lft forever



----------------------ip a from network node ---------------------------
[root@server1 ~(keystone_admin)]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host ...
(more)
edit retag flag offensive close merge delete

Comments

seems like external bridge br-ex is connected with loopback interface !!??

Praveen N gravatar imagePraveen N ( 2017-10-10 05:47:11 -0600 )edit