No View of IP Addresses in VE 8?

hd-- said:
Sorry my mistake, it in the host, in your caste pve01
Click to expand...
There are NO VLAN that I can see. I did run the command you gave in the shell ifreload -v -d -a 2>&1 It appears to have gotten id of them...but to me something does not look right, still.

I also cannot get IPv6 on the eno1 port....which means no IPv6 on vmbr0

This one does not seem to have a problem:

1700140541948.png

Maybe I should just install DEBIAN by itself and see if that port gets IPv6.
 
UPDATE:

I installed Debian 12 (Graphic) on this same server - choosing defaults for all options on the install (where I could) - and once it booted up, the eno1 (it got the same name on this install) has both an IPv4 (same DHCP address where there is a reservation) and an IPv6 address within the range I have configured in pfSense for handing out IPv6 addresses.

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 noprefixroute
valid_lft forever preferred_lft forever
2: ens4f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:7f brd ff:ff:ff:ff:ff:ff
altname enp2s0f0
3: ens4f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:80 brd ff:ff:ff:ff:ff:ff
altname enp2s0f1
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether c8:d3:ff:b6:cb:29 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
inet 10.9.28.240/24 brd 10.9.28.255 scope global dynamic noprefixroute eno1
valid_lft 5922sec preferred_lft 5922sec
inet6 2601:c4:c501:8bf0::1744/128 scope global dynamic noprefixroute
valid_lft 5823sec preferred_lft 3123sec
inet6 2601:c4:c501:8bf0:3836:e816:cdf0:cab0/64 scope global temporary dynamic
valid_lft 86120sec preferred_lft 14120sec
inet6 2601:c4:c501:8bf0:cad3:ffff:feb6:cb29/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86120sec preferred_lft 14120sec
inet6 fe80::cad3:ffff:feb6:cb29/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: ens4f2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:81 brd ff:ff:ff:ff:ff:ff
altname enp2s0f2
6: ens4f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:82 brd ff:ff:ff:ff:ff:ff
altname enp2s0f3
 
iface vmbr0 inet static

iface vmbr0 inet6 dhcp
Click to expand...

These two lines won't work with each other. There's some bug with debian (or maybe it's proxmox specific?) and "ifupdown2" (I think) that prevents mixing "static" and "dhcp." The best compromise I've found for myself was to leave the ipv4 (inet) line as static, and have nothing for ipv6 (remove the inet6 line.) That should result in linux giving itself a SLAAC address once it sees an ipv6 router announcement.

(You could also assign both ipv4 and ipv6 addresses via DHCP, but it's usually better for proxmox to have a static IP.)
 
garyd9 said:
These two lines won't work with each other. There's some bug with debian (or maybe it's proxmox specific?) and "ifupdown2" (I think) that prevents mixing "static" and "dhcp." The best compromise I've found for myself was to leave the ipv4 (inet) line as static, and have nothing for ipv6 (remove the inet6 line.) That should result in linux giving itself a SLAAC address once it sees an ipv6 router announcement.

(You could also assign both ipv4 and ipv6 addresses via DHCP, but it's usually better for proxmox to have a static IP.)
Click to expand...
Gary,

Thanks - I have tried ALL possible combinations. I think that PROMOX is doing this. I just installed DEBIAN 12 with GUI to the same machine - nothing but defaults on the install. Using the same on-board NIC that the Proxmox is using. It pulled both IPv4 and IPv6 address as I would expect it to. The IPv6 was in the range set in pfSense for my network.

I have tried IPv4 and IPv6 as DHCP (I have a reservation on pfSense to give the 10.9.28.240/24). This works, as even during the installation of Proxmox - the field is preloaded with that IP on the install wizard.
 
bearhntr said:
Gary,

Thanks - I have tried ALL possible combinations. I think that PROMOX is doing this. I just installed DEBIAN 12 with GUI to the same machine - nothing but defaults on the install. Using the same on-board NIC that the Proxmox is using. It pulled both IPv4 and IPv6 address as I would expect it to. The IPv6 was in the range set in pfSense for my network.

I have tried IPv4 and IPv6 as DHCP (I have a reservation on pfSense to give the 10.9.28.240/24). This works, as even during the installation of Proxmox - the field is preloaded with that IP on the install wizard.
Click to expand...
I realize you've tried all possible combinations, but have you tried all possible exclusions?

Specifically, just stick a "#" symbol before the "inet6 dhcp" line. At least on my setup, that causes vmbr0 to be assigned the static IP for ipv4, and use SLAAC to get an ipv6 address:

Code: 
auto vmbr0
iface vmbr0 inet static
address 10.9.28.240/24
gateway 10.9.28.254
bridge-ports eno1
bridge-stp off
bridge-fd 0
#On-Board NIC (for HOST)

#inet vmbr0 inet6 dhcp

On my machine, that results in something like:
Code: 
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether fa:aa:bb:cc:dd:ee brd ff:ff:ff:ff:ff:ff
    inet 192.168.31.98/24 scope global vmbr0.31
       valid_lft forever preferred_lft forever
    inet6 xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr 
       valid_lft 85857sec preferred_lft 85857sec
    inet6 fe80::f8e4:24ff:fe5b:78cf/64 scope link 
       valid_lft forever preferred_lft forever
(I edited the inet6 address for privacy, but it's in the scope of my router's net)
 
garyd9 said:
I realize you've tried all possible combinations, but have you tried all possible exclusions?

Specifically, just stick a "#" symbol before the "inet6 dhcp" line. At least on my setup, that causes vmbr0 to be assigned the static IP for ipv4, and use SLAAC to get an ipv6 address:

Code: 
auto vmbr0
iface vmbr0 inet static
address 10.9.28.240/24
gateway 10.9.28.254
bridge-ports eno1
bridge-stp off
bridge-fd 0
#On-Board NIC (for HOST)

#inet vmbr0 inet6 dhcp

On my machine, that results in something like:
Code: 
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether fa:aa:bb:cc:dd:ee brd ff:ff:ff:ff:ff:ff
    inet 192.168.31.98/24 scope global vmbr0.31
       valid_lft forever preferred_lft forever
    inet6 xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr
       valid_lft 85857sec preferred_lft 85857sec
    inet6 fe80::f8e4:24ff:fe5b:78cf/64 scope link
       valid_lft forever preferred_lft forever
(I edited the inet6 address for privacy, but it's in the scope of my router's net)
Click to expand...

This is from a brand new install last night. No changes at all except applying UPDATES - fresh install from the USB that I made from the proxmox-ve_8.0-2.iso:

root@pve01:~# ip addr
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 noprefixroute
valid_lft forever preferred_lft forever
2: ens4f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:7f brd ff:ff:ff:ff:ff:ff
altname enp2s0f0
3: ens4f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:80 brd ff:ff:ff:ff:ff:ff
altname enp2s0f1
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether c8:d3:ff:b6:cb:29 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
5: ens4f2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:81 brd ff:ff:ff:ff:ff:ff
altname enp2s0f2
6: ens4f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:82 brd ff:ff:ff:ff:ff:ff
altname enp2s0f3
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c8:d3:ff:b6:cb:29 brd ff:ff:ff:ff:ff:ff
inet 10.9.28.240/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::cad3:ffff:feb6:cb29/64 scope link
valid_lft forever preferred_lft forever


Here is the /etc/network/interfaces file - untouched.

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
address 10.9.28.240/24
gateway 10.9.28.254
bridge-ports eno1
bridge-stp off
bridge-fd 0

iface ens4f0 inet manual

iface ens4f1 inet manual

iface ens4f2 inet manual

iface ens4f3 inet manual
 
As you can see - vmbr0 just pulled a Link-Local address, no IPv6. This is what has been happening since I began this journey. Whereas when I installed Debian by itself - using the same configuration, it pulls an IPv6 address.
 
Thank you for trying. My Best Guess at this point would be that RA's aren't being seen by the bridge. I'm not familiar enough with the lower level tools to help you to triage that, however.

I'm wondering why "eno1" is being used here instead of "enp0s31f6". It's a shot in the dark, but what if you replace every occurrence of "eno1" in your interfaces file with the enp0s31f6 alias?
 
garyd9 said:
Thank you for trying. My Best Guess at this point would be that RA's aren't being seen by the bridge. I'm not familiar enough with the lower level tools to help you to triage that, however.

I'm wondering why "eno1" is being used here instead of "enp0s31f6". It's a shot in the dark, but what if you replace every occurrence of "eno1" in your interfaces file with the enp0s31f6 alias?
Click to expand...
eno1 = the on-board NIC which is what I use for the 'access' to the host.

There is a 4-port card in the server which I plan to use for VMs - namely one of them will be pfSense or OPNsense or OpenWRT. So it needs a port to MODEM and a port OUT to the Wireless AP and hub which gives my home network.
 
bearhntr said:
eno1 = the on-board NIC which is what I use for the 'access' to the host.

There is a 4-port card in the server which I plan to use for VMs - namely one of them will be pfSense or OPNsense or OpenWRT. So it needs a port to MODEM and a port OUT to the Wireless AP and hub which gives my home network.
Click to expand...

Aren't en0 and enp0s31f6 the same NIC? It looks like your 4 port card uses ens4f[0-3]. I'm just wondering if the aliasing of en0 to enp0s31f6 is impacting something - which was why I was wondering if things would work if they were referenced by the alias (enp0s31f6.) As I said, it's just a shot in the dark. Probably wouldn't fix anything.
 
garyd9 said:
Aren't en0 and enp0s31f6 the same NIC? It looks like your 4 port card uses ens4f[0-3]. I'm just wondering if the aliasing of en0 to enp0s31f6 is impacting something - which was why I was wondering if things would work if they were referenced by the alias (enp0s31f6.) As I said, it's just a shot in the dark. Probably wouldn't fix anything.
Click to expand...
Nope --- see the MAC ADDR ... the ens4f0, f1, f2, f3 are the 4-port card. I do not know why IP ADDR groups them like it does.

1700228771602.png
 
bearhntr said:
Nope --- see the MAC ADDR ... the ens4f0, f1, f2, f3 are the 4-port card. I do not know why IP ADDR groups them like it does.

View attachment 58264
Click to expand...
The enp0s31f6 is the same as the eno1. See #4 in your image. eno1.. altname enp0s31f6.

That's why I'm suggesting that you change references from "eno1" to "enp0s31f6." It probably won't change anything at all, but... can it hurt to try?
 
garyd9 said:
The enp0s31f6 is the same as the eno1. See #4 in your image. eno1.. altname enp0s31f6.

That's why I'm suggesting that you change references from "eno1" to "enp0s31f6." It probably won't change anything at all, but... can it hurt to try?
Click to expand...
I see the enp0s31f6 AltName name - but the eno1 / vmbr0 was not created by me at all. The installation created that.

The files and images that I have share are a 'brand new' install - no a single change by me, other than updates.

If you try and change it - you get this:

1700229340413.png
 
bearhntr said:
I see the enp0s31f6 AltName name - but the eno1 / vmbr0 was not created by me at all. The installation created that.

The files and images that I have share are a 'brand new' install - no a single change by me, other than updates.

If you try and change it - you get this:

View attachment 58268
Click to expand...
Did you also change the "iface eno1 inet manual" line?
 
garyd9 said:
Did you also change the "iface eno1 inet manual" line?
Click to expand...
I made the changes (blue) and rebooted, and here are the results (red) - machine came right back with same IP address (there is a DHCP reservation for it):

auto lo
iface lo inet loopback

iface eno1 inet dhcp

auto vmbr0
iface vmbr0 inet dhcp
# address 10.9.28.240/24
# gateway 10.9.28.254
bridge-ports eno1
bridge-stp off
bridge-fd 0

iface ens4f0 inet manual

iface ens4f1 inet manual

iface ens4f2 inet manual

iface ens4f3 inet manual


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Nov 17 07:57:33 EST 2023 on pts/0
root@pve01:~# ip addr
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 noprefixroute
valid_lft forever preferred_lft forever
2: ens4f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:7f brd ff:ff:ff:ff:ff:ff
altname enp2s0f0
3: ens4f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:80 brd ff:ff:ff:ff:ff:ff
altname enp2s0f1
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether c8:d3:ff:b6:cb:29 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
5: ens4f2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:81 brd ff:ff:ff:ff:ff:ff
altname enp2s0f2
6: ens4f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:e0:c0:4f:48:82 brd ff:ff:ff:ff:ff:ff
altname enp2s0f3
7: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c8:d3:ff:b6:cb:29 brd ff:ff:ff:ff:ff:ff
inet 10.9.28.240/24 brd 10.9.28.255 scope global dynamic vmbr0
valid_lft 7139sec preferred_lft 7139sec
inet6 fe80::cad3:ffff:feb6:cb29/64 scope link
valid_lft forever preferred_lft forever
 
I think there's a misunderstanding. It might be my fault - I'm not quite fully awake yet. Here's what I'm suggesting you try in your interfaces file (with changes in bold.)

auto lo
iface lo inet loopback

iface enp0s31f6 inet manual

auto vmbr0
iface vmbr0 inet dhcp
# address 10.9.28.240/24
# gateway 10.9.28.254
bridge-ports enp0s31f6
bridge-stp off
bridge-fd 0

iface ens4f0 inet manual

iface ens4f1 inet manual

iface ens4f2 inet manual

iface ens4f3 inet manual
 
OK -- So, made those changes and rebooted... now I have no access to the console remotely. I will have to go hook up a monitor and keyboard to the box and undo from there. :eek:

I get this:

1700232081172.png
 
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