Strange network behavior after router change

A

amwo

New Member
Aug 27, 2023
2
0
1
Hi all!

I am very fresh to all of this, so this is probably something simple, but I can't figure it out.

I have bought a Mikrotik HAP AX3 router/switch/AP all-in-one, so I can finally set LACP, port forwarding etc for my proxmox server.
I have set a new network in 10.0.0.0/24 with router being 10.0.0.1 and set up link aggregation to the proxmox machine. DHCP pool: 10.0.0.10 - 10.0.0.99
I have changed IP address in proxmox to 10.0.0.100, my containers are 10.0.0.*containerID*. I have changed the gateway to 10.0.0.1

I can:
ping the host from my pc in the same network
ping the host from my router
ping my computer from the host
access internet from a VM hosted on the proxmox (dhcp)
ping the forementioned VM from my computer

I can't:
ping the router from the host
ping the router from any container on the host (static ip)
ping any of the containers from my computer

What am I missing?

/etc/network/interfaces
Code: 
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto enp10s0
iface enp10s0 inet manual

auto enp9s0
iface enp9s0 inet manual

auto bond0
iface bond0 inet manual
        bond-slaves enp10s0 enp9s0
        bond-miimon 100
        bond-mode 802.3ad
        bond-xmit-hash-policy layer2

auto vmbr0
iface vmbr0 inet static
        address 10.0.0.100/24
        gateway 10.0.0.1
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

hosts
Code: 
127.0.0.1 localhost.localdomain localhost
10.0.0.100 homelab.lan homelab

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

ip link
Code: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp9s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 52:4d:5b:cd:f5:f0 brd ff:ff:ff:ff:ff:ff permaddr e8:06:88:cb:31:9a
3: enp10s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 52:4d:5b:cd:f5:f0 brd ff:ff:ff:ff:ff:ff permaddr e8:06:88:cb:10:5d
6: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP mode DEFAULT group default qlen 1000
    link/ether b2:da:03:7f:c8:f1 brd ff:ff:ff:ff:ff:ff link-netnsid 0
7: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 8e:71:da:b3:ce:df brd ff:ff:ff:ff:ff:ff
8: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 1a:c4:cf:9d:93:3b brd ff:ff:ff:ff:ff:ff
9: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP mode DEFAULT group default qlen 1000
    link/ether 16:52:5d:43:10:83 brd ff:ff:ff:ff:ff:ff
10: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP mode DEFAULT group default qlen 1000
    link/ether 22:93:39:4c:b4:31 brd ff:ff:ff:ff:ff:ff link-netnsid 1
11: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 72:4f:1c:a8:09:c3 brd ff:ff:ff:ff:ff:ff
12: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether ae:46:c5:3a:a0:a0 brd ff:ff:ff:ff:ff:ff
13: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP mode DEFAULT group default qlen 1000
    link/ether d2:1b:38:d8:7e:0e brd ff:ff:ff:ff:ff:ff
14: veth103i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP mode DEFAULT group default qlen 1000
    link/ether 1a:8a:43:c4:4f:d5 brd ff:ff:ff:ff:ff:ff link-netnsid 2
15: fwbr103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 5a:74:87:f3:fd:ad brd ff:ff:ff:ff:ff:ff
16: fwpr103p0@fwln103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether f2:a4:47:b8:6e:3a brd ff:ff:ff:ff:ff:ff
17: fwln103i0@fwpr103p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP mode DEFAULT group default qlen 1000
    link/ether 0a:bb:f7:4b:20:d2 brd ff:ff:ff:ff:ff:ff
40: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 52:4d:5b:cd:f5:f0 brd ff:ff:ff:ff:ff:ff
41: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 52:4d:5b:cd:f5:f0 brd ff:ff:ff:ff:ff:ff
42: tap313i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr313i0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether ee:54:6b:e2:8c:c9 brd ff:ff:ff:ff:ff:ff
43: fwbr313i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 42:97:dd:ea:73:a5 brd ff:ff:ff:ff:ff:ff
44: fwpr313p0@fwln313i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether e2:2f:ca:60:3d:c4 brd ff:ff:ff:ff:ff:ff
45: fwln313i0@fwpr313p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr313i0 state UP mode DEFAULT group default qlen 1000
    link/ether 22:78:7f:91:0c:ae brd ff:ff:ff:ff:ff:ff

/proc/net/bonding/bond0
Code: 
Ethernet Channel Bonding Driver: v6.2.16-8-pve

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0

802.3ad info
LACP active: on
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 52:4d:5b:cd:f5:f0
Active Aggregator Info:
        Aggregator ID: 1
        Number of ports: 2
        Actor Key: 9
        Partner Key: 9
        Partner Mac Address: 48:a9:8a:e2:87:01

Slave Interface: enp10s0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: e8:06:88:cb:10:5d
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
    system priority: 65535
    system mac address: 52:4d:5b:cd:f5:f0
    port key: 9
    port priority: 255
    port number: 1
    port state: 61
details partner lacp pdu:
    system priority: 65535
    system mac address: 48:a9:8a:e2:87:01
    oper key: 9
    port priority: 255
    port number: 1
    port state: 61

Slave Interface: enp9s0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: e8:06:88:cb:31:9a
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
    system priority: 65535
    system mac address: 52:4d:5b:cd:f5:f0
    port key: 9
    port priority: 255
    port number: 2
    port state: 61
details partner lacp pdu:
    system priority: 65535
    system mac address: 48:a9:8a:e2:87:01
    oper key: 9
    port priority: 255
    port number: 2
    port state: 61
 
if u use vlans with your bridge u must use a separate ip config for your host.
search the forum and u will find examples. also look into the docu for part "3.3.8. VLAN 802.1Q".
I think proxmox should change the gui background function to serve this configuration because its a typical one.
 
Last edited:
floh8 said:
if u use vlans with your bridge u must use a separate ip config for your host.
search the forum and u will find examples. also look into the docu for part "3.3.8. VLAN 802.1Q".
I think proxmox should change the gui background function to serve this configuration because its a typical one.
Click to expand...
Thank you for your response. For some reason my proxmox didn't like that I changed the network even though I followed documentation. I have not used vlans. I couldn't figure it out so I decided to reinstall the host and set the network to 10.0.0.0/24 during the install and it works without issues.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back