Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • RHEL 8 cockpit routing mess

    Posted on

    on a perfectly routing system. I created a bridge using cockpit - added eno2 and it worked fine. ping from other host on network etc.

    but then i deleted it and fter that only eno1 is pingable and tcpdump shows ping packets are reaching on other NICs like eno2 but, there is no route back to source.

    i do not see any difference in the routing table. I am suspecting something is messed up inside cockpit or networkmanager configurations for routing.

    ping to .146 still works - fails for all other intfcs!!!

    routing:

    [root@server network-scripts]# ip route
    default via 123.112.147.131 dev eno1 proto static metric 100
    123.112.147.128/26 dev eno1 proto kernel scope link src 123.112.147.146 metric 100
    123.112.147.128/26 dev eno2 proto kernel scope link src 123.112.147.147 metric 101
    123.112.147.128/26 dev eno3 proto kernel scope link src 123.112.147.148 metric 102
    123.112.147.128/26 dev eno4 proto kernel scope link src 123.112.147.149 metric 103
    192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
    
    [root@server ~]# netstat -nr
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
    0.0.0.0         123.112.147.131 0.0.0.0         UG        0 0          0 eno1
    123.112.147.128 0.0.0.0         255.255.255.192 U         0 0          0 eno1
    123.112.147.128 0.0.0.0         255.255.255.192 U         0 0          0 eno2
    123.112.147.128 0.0.0.0         255.255.255.192 U         0 0          0 eno3
    123.112.147.128 0.0.0.0         255.255.255.192 U         0 0          0 eno4
    192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 virbr0
    
    # nmcli d s
    DEVICE      TYPE      STATE         CONNECTION
    eno1        ethernet  connected     eno1
    eno2        ethernet  connected     eno2
    eno3        ethernet  connected     eno3
    eno4        ethernet  connected     eno4
    virbr0      bridge    connected     virbr0
    
    
    [root@server network-scripts]# ip -4 a
    1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
    2: eno1:  mtu 1500 qdisc mq state UP group default qlen 1000
        inet 123.112.147.146/26 brd 123.112.147.191 scope global noprefixroute eno1
           valid_lft forever preferred_lft forever
    3: eno2:  mtu 1500 qdisc mq state UP group default qlen 1000
        inet 123.112.147.147/26 brd 123.112.147.191 scope global noprefixroute eno2
           valid_lft forever preferred_lft forever
    4: eno3:  mtu 1500 qdisc mq state UP group default qlen 1000
        inet 123.112.147.148/26 brd 123.112.147.191 scope global noprefixroute eno3
           valid_lft forever preferred_lft forever
    5: eno4:  mtu 1500 qdisc mq state UP group default qlen 1000
        inet 123.112.147.149/26 brd 123.112.147.191 scope global noprefixroute eno4
           valid_lft forever preferred_lft forever
    12: virbr0:  mtu 1500 qdisc noqueue state DOWN group default qlen 1000
        inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
           valid_lft forever preferred_lft forever
    

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2025 Red Hat