Changing proxmox management ip

May 16, 2020
51
0
6
I setup proxmox with ip 172.20.2.3 on a supermicro box with ip 172.20.2.2. I have a default linux bridge vmbr0 with a cidr at 172.20.2.3/24 and gateway of 172.20.2.1.

I am thinking of changing all the above to the following:
  • keep the supermicro box in the 172 subnet. So it remains 172.20.2.2.
  • Use VLAN 99 ( 10.0.0.1/24 subnet) for the Proxmox VE management IP with VLAN aware Linux bridge.
  • So change the proxmox management ip to something like 10.0.0.150, for example.
  • setup other lxc containers pointing to different vlans in my network - e.g dhcp lxc container going to vlan 99, database vlan going to 1001 etc.

I am not sure how to set all this up without blowing my current setup. Is any /all of the above possible? What is the correct sequence to set things up? First setup the vlan linux bridge ?
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
Can you write down your switch port config where you have the proxmox server attached?

Like:
Vlan 99 - 10.0.0.0/8 - untagged
Vlan 100 - 172.20.0.0/24 - tagged
.....
...

And your actual /etc/network/interfaces config?

Cheers
 
May 16, 2020
51
0
6
Can you write down your switch port config where you have the proxmox server attached?

Like:
Vlan 99 - 10.0.0.0/8 - untagged
Vlan 100 - 172.20.0.0/24 - tagged
.....
...

And your actual /etc/network/interfaces config?

Cheers

The proxmox server is connected to a switch port with vlan 1002 ( 172.20.2.0/24) tagged). I can of course change that to the native vlan - which is in the 10.0.0.1/24 subnet.

Here is my interface config file ...
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto eno5
iface eno5 inet manual

auto eno6
iface eno6 inet manual

auto eno7
iface eno7 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto eno2
iface eno2 inet manual

auto eno8
iface eno8 inet manual

auto vmbr0
iface vmbr0 inet static
        address 172.20.2.3/24
        gateway 172.20.2.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094
 
Last edited:

Ramalama

Member
Dec 26, 2020
88
14
8
32
I setup proxmox with ip 172.20.2.3 on a supermicro box with ip 172.20.2.2.
Then the last thing, that i don't fully understand.

- You have proxmox virtualized / proxmox has 172.20.2.3 and the hypervisor on supermicro has 172.20.2.2
OR
- Proxmox has 172.20.2.3 and your ipmi/bmc interface has 172.20.2.2 ?
 
May 16, 2020
51
0
6
Then the last thing, that i don't fully understand.

- You have proxmox virtualized / proxmox has 172.20.2.3 and the hypervisor on supermicro has 172.20.2.2
OR
- Proxmox has 172.20.2.3 and your ipmi/bmc interface has 172.20.2.2 ?

- Proxmox has 172.20.2.3 and your ipmi/bmc interface has 172.20.2.2 ?
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
The proxmox server is connected to a switch port with vlan 1002 ( 172.20.2.0/24) tagged). I can of course change that to the native vlan - which is in the 10.0.0.1/24 subnet.

Here is my interface config file ...
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto eno5
iface eno5 inet manual

auto eno6
iface eno6 inet manual

auto eno7
iface eno7 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto eno2
iface eno2 inet manual

auto eno8
iface eno8 inet manual

auto vmbr0
iface vmbr0 inet static
        address 172.20.2.3/24
        gateway 172.20.2.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094
"The proxmox server is connected to a switch port with vlan 1002 ( 172.20.2.0/24) tagged)."

-> Your network/interface doesn't use any vlan tag,
if your vlan 1002 (172.20.2.0/24) is tagged, and proxmox has 172.20.2.3 as IP without any tag (untagged), how does this works then? xD

if your vlan 1002 is untagged on that port with pvid, then it would make more sense.
 
May 16, 2020
51
0
6
"The proxmox server is connected to a switch port with vlan 1002 ( 172.20.2.0/24) tagged)."

-> Your network/interface doesn't use any vlan tag,
if your vlan 1002 (172.20.2.0/24) is tagged, and proxmox has 172.20.2.3 as IP without any tag (untagged), how does this works then? xD

if your vlan 1002 is untagged on that port with pvid, then it would make more sense.

ok. but do you have a solution for my original post assuming its untagged?
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
Sure, there are many ways to realize what you want.

The easiest way, to have only the management ip but not the whole bridge on your vlan 99 is this:

Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto eno5
iface eno5 inet manual

auto eno6
iface eno6 inet manual

auto eno7
iface eno7 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto eno2
iface eno2 inet manual

auto eno8
iface eno8 inet manual

auto vmbr0
iface vmbr0 inet static
        address 172.20.2.3/24
        gateway 172.20.2.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto eno1.99
iface eno1.99 inet static
        address 10.0.0.150/24
#        gateway 10.0.0.1

leave the gateway commented out for the first step.
then you bring the interface up:
ifup eno1.99

Then you try to ping your proxmox host with the new IP Adress, from a client that is on the same subnet (10.0.0.0/24)...
Because we have the gateway commented out...

if it works, then you can change the config to:
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto eno5
iface eno5 inet manual

auto eno6
iface eno6 inet manual

auto eno7
iface eno7 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto eno2
iface eno2 inet manual

auto eno8
iface eno8 inet manual

auto vmbr0
iface vmbr0 inet static
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto eno1.99
iface eno1.99 inet static
        address 10.0.0.150/24
        gateway 10.0.0.1

And reboot.

That means:
- You management ip is on vlan99 tagged, without any bridge or anything.
- Your vmbridge is vlan aware (all vlans) and default untagged for VM's

Cheers :)
 
May 16, 2020
51
0
6
Sure, there are many ways to realize what you want.

The easiest way, to have only the management ip but not the whole bridge on your vlan 99 is this:

Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto eno5
iface eno5 inet manual

auto eno6
iface eno6 inet manual

auto eno7
iface eno7 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto eno2
iface eno2 inet manual

auto eno8
iface eno8 inet manual

auto vmbr0
iface vmbr0 inet static
        address 172.20.2.3/24
        gateway 172.20.2.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto eno1.99
iface eno1.99 inet static
        address 10.0.0.150/24
#        gateway 10.0.0.1

leave the gateway commented out for the first step.
then you bring the interface up:
ifup eno1.99

Then you try to ping your proxmox host with the new IP Adress, from a client that is on the same subnet (10.0.0.0/24)...
Because we have the gateway commented out...

if it works, then you can change the config to:
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto eno5
iface eno5 inet manual

auto eno6
iface eno6 inet manual

auto eno7
iface eno7 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto eno2
iface eno2 inet manual

auto eno8
iface eno8 inet manual

auto vmbr0
iface vmbr0 inet static
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto eno1.99
iface eno1.99 inet static
        address 10.0.0.150/24
        gateway 10.0.0.1

And reboot.

That means:
- You management ip is on vlan99 tagged, without any bridge or anything.
- Your vmbridge is vlan aware (all vlans) and default untagged for VM's

Cheers :)

wonderful! going to implement and report back!
 
May 16, 2020
51
0
6
I edited the /etc/network/interfaces file, saved, did an ifup eno1.99, then tried to ping it from another machine at 10.0.0.108. Didnt work. So i reboot the proxmox host. I still see that the old ip is still working and the network interface seems not to have been saved. Was it overwritten? Should I be editing another file to force the changes?
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
Nono, that's why i told you to do this in 2 steps.

Can you post the output of "ip a" ?
 
May 16, 2020
51
0
6
Nono, that's why i told you to do this in 2 steps.

Can you post the output of "ip a" ?

Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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
2: eno5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:50 brd ff:ff:ff:ff:ff:ff
3: eno6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:51 brd ff:ff:ff:ff:ff:ff
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 3c:ec:ef:40:86:a8 brd ff:ff:ff:ff:ff:ff
5: eno7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3c:ec:ef:40:86:52 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3eec:efff:fe40:8652/64 scope link
       valid_lft forever preferred_lft forever
6: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:a9 brd ff:ff:ff:ff:ff:ff
7: eno8: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:53 brd ff:ff:ff:ff:ff:ff
8: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:aa brd ff:ff:ff:ff:ff:ff
9: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:ab brd ff:ff:ff:ff:ff:ff
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3c:ec:ef:40:86:a8 brd ff:ff:ff:ff:ff:ff
    inet 172.20.2.3/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::3eec:efff:fe40:86a8/64 scope link
       valid_lft forever preferred_lft forever
11: veth123i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr123i0 state UP group default qlen 1000
    link/ether fe:af:3d:7b:e6:f8 brd ff:ff:ff:ff:ff:ff link-netnsid 0
12: fwbr123i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6e:cc:b6:06:ac:c7 brd ff:ff:ff:ff:ff:ff
13: fwpr123p0@fwln123i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether da:7e:27:8f:8e:2b brd ff:ff:ff:ff:ff:ff
14: fwln123i0@fwpr123p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr123i0 state UP group default qlen 1000
    link/ether 6e:cc:b6:06:ac:c7 brd ff:ff:ff:ff:ff:ff
15: veth111i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP group default qlen 1000
    link/ether fe:cb:e5:8a:16:63 brd ff:ff:ff:ff:ff:ff link-netnsid 1
16: fwbr111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 62:b8:49:21:a7:31 brd ff:ff:ff:ff:ff:ff
17: fwpr111p0@fwln111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 66:a1:8c:e3:48:a0 brd ff:ff:ff:ff:ff:ff
18: fwln111i0@fwpr111p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP group default qlen 1000
    link/ether 62:b8:49:21:a7:31 brd ff:ff:ff:ff:ff:ff
19: veth112i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr112i0 state UP group default qlen 1000
    link/ether fe:66:d1:16:f4:de brd ff:ff:ff:ff:ff:ff link-netnsid 2
20: fwbr112i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1a:3c:f4:47:3f:29 brd ff:ff:ff:ff:ff:ff
21: fwpr112p0@fwln112i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 02:1c:cb:39:94:21 brd ff:ff:ff:ff:ff:ff
22: fwln112i0@fwpr112p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr112i0 state UP group default qlen 1000
    link/ether 1a:3c:f4:47:3f:29 brd ff:ff:ff:ff:ff:ff
23: veth122i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr122i0 state UP group default qlen 1000
    link/ether fe:31:eb:46:98:81 brd ff:ff:ff:ff:ff:ff link-netnsid 3
24: fwbr122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether be:5b:6c:4d:5c:9b brd ff:ff:ff:ff:ff:ff
25: fwpr122p0@fwln122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 7a:b6:15:66:fd:93 brd ff:ff:ff:ff:ff:ff
26: fwln122i0@fwpr122p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr122i0 state UP group default qlen 1000
    link/ether be:5b:6c:4d:5c:9b brd ff:ff:ff:ff:ff:ff
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
And your /etc/network/interfaces reverted?

Can you move this block above vmbr0 block:
Code:
auto eno1.99
iface eno1.99 inet static
        address 10.0.0.150/24
#        gateway 10.0.0.1

Make an "ifup eno1.99" again and post the output of "ip a" again?
 
May 16, 2020
51
0
6
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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
2: eno5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:50 brd ff:ff:ff:ff:ff:ff
3: eno6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:51 brd ff:ff:ff:ff:ff:ff
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 3c:ec:ef:40:86:a8 brd ff:ff:ff:ff:ff:ff
5: eno7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3c:ec:ef:40:86:52 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3eec:efff:fe40:8652/64 scope link
       valid_lft forever preferred_lft forever
6: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:a9 brd ff:ff:ff:ff:ff:ff
7: eno8: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:53 brd ff:ff:ff:ff:ff:ff
8: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:aa brd ff:ff:ff:ff:ff:ff
9: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:ec:ef:40:86:ab brd ff:ff:ff:ff:ff:ff
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3c:ec:ef:40:86:a8 brd ff:ff:ff:ff:ff:ff
    inet 172.20.2.3/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::3eec:efff:fe40:86a8/64 scope link
       valid_lft forever preferred_lft forever
11: veth123i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr123i0 state UP group default qlen 1000
    link/ether fe:af:3d:7b:e6:f8 brd ff:ff:ff:ff:ff:ff link-netnsid 0
12: fwbr123i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6e:cc:b6:06:ac:c7 brd ff:ff:ff:ff:ff:ff
13: fwpr123p0@fwln123i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether da:7e:27:8f:8e:2b brd ff:ff:ff:ff:ff:ff
14: fwln123i0@fwpr123p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr123i0 state UP group default qlen 1000
    link/ether 6e:cc:b6:06:ac:c7 brd ff:ff:ff:ff:ff:ff
15: veth111i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP group default qlen 1000
    link/ether fe:cb:e5:8a:16:63 brd ff:ff:ff:ff:ff:ff link-netnsid 1
16: fwbr111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 62:b8:49:21:a7:31 brd ff:ff:ff:ff:ff:ff
17: fwpr111p0@fwln111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 66:a1:8c:e3:48:a0 brd ff:ff:ff:ff:ff:ff
18: fwln111i0@fwpr111p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP group default qlen 1000
    link/ether 62:b8:49:21:a7:31 brd ff:ff:ff:ff:ff:ff
19: veth112i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr112i0 state UP group default qlen 1000
    link/ether fe:66:d1:16:f4:de brd ff:ff:ff:ff:ff:ff link-netnsid 2
20: fwbr112i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1a:3c:f4:47:3f:29 brd ff:ff:ff:ff:ff:ff
21: fwpr112p0@fwln112i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 02:1c:cb:39:94:21 brd ff:ff:ff:ff:ff:ff
22: fwln112i0@fwpr112p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr112i0 state UP group default qlen 1000
    link/ether 1a:3c:f4:47:3f:29 brd ff:ff:ff:ff:ff:ff
23: veth122i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr122i0 state UP group default qlen 1000
    link/ether fe:31:eb:46:98:81 brd ff:ff:ff:ff:ff:ff link-netnsid 3
24: fwbr122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether be:5b:6c:4d:5c:9b brd ff:ff:ff:ff:ff:ff
25: fwpr122p0@fwln122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 7a:b6:15:66:fd:93 brd ff:ff:ff:ff:ff:ff
26: fwln122i0@fwpr122p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr122i0 state UP group default qlen 1000
    link/ether be:5b:6c:4d:5c:9b brd ff:ff:ff:ff:ff:ff
27: eno1.99@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3c:ec:ef:40:86:a8 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.150/24 scope global eno1.99
       valid_lft forever preferred_lft forever
    inet6 fe80::3eec:efff:fe40:86a8/64 scope link
       valid_lft forever preferred_lft forever
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
It works, you should be able to ping from the same network (10.0.0.0/24)

Maybe firewawall?
iptales -L -nv

Or your client isn't in vlan 99?
Or vlan 99 isn't tagged on the switch where proxmox is connected?
 
May 16, 2020
51
0
6
vlan99 is my default management vlan on my pfsense box using the 10.0 subnet. The switch and all access points are in this same subnet . Let me go back to recheck everything. In the meantime, here is the output you asked for:

Code:
Chain INPUT (policy ACCEPT 8357 packets, 2573K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 6707 packets, 3278K bytes)
 pkts bytes target     prot opt in     out     source               destination
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
Well, check, if it doesn't work, we could add an interface to the bridge itself too.

Probably you could ping from proxmox 10.0.0.1 if that's your gw.
 

Ramalama

Member
Dec 26, 2020
88
14
8
32
Well sure, if you have a port free.

Im sorry, i was building my next pc, covid time
However, i forgot something

You need to add
vlan-raw-device eno1

So the block should look like this:
Code:
auto eno1.99
iface eno1.99 inet static
        address 10.0.0.150/24
#        gateway 10.0.0.1
        vlan-raw-device eno1
Test that again, you can bring the interface down with:
ifdown eno1.99
Then make the change and
ifup eno1.99

Cheers
 

About

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

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 your own in 60 seconds.

Buy now!