aquantia aqc107 dhcp failed during proxmox installation

[sismondi]

Hello. How are you?

I try to install proxmox and when I choose the 10GB network card I have a problem.

An IP address is not obtained within the range.

This makes the web interface unavailable.

Any idea what is happening?

It's not the cables because I used 2 different cables.

It's not my switch or my router either because I can install proxmox with the onboard network card without any problem.

The network card worked in debian/omv 5 until a couple of days ago without a problem, so I don't think the problem is there.

Thank you very much in advance

 

[hd--]

Hello

From your describtion i understand that the installation was successful, but now you don't have access to the webinterface on Port 8006 ?
Are you able to connect to the Host via ssh or do you have physical access and can plugin keyboard and Screen ?

 

[sismondi]

Hello

From your describtion i understand that the installation was successful, but now you don't have access to the webinterface on Port 8006 ?
Are you able to connect to the Host via ssh or do you have physical access and can plugin keyboard and Screen ?

Yes, the installation was successful.

But I don't have access to the web interface on port 8006.

I can't connect via ssh

with keyboard and screen I have access to the server

 

[hd--]

what is the output of ip a of your machine ?

 

[sismondi]

what is the output of ip a of your machine ?

I attach a photo. I'm sorry I can't copy and paste the code.

enp33s0 is the aquantia 10gb network card

enp42s0 is the onboard network card of the motherboard

Only the Aquantia network card is connected to the switch.

 

[hd--]

Can you also print the /etc/network/interfaces

And can you reach the web interface at the 192.168.1.50:8006 or connect via ssh root@192.168.1.50?

 

[sismondi]

Can you also print the /etc/network/interfaces

And can you reach the web interface at the 192.168.1.50:8006 or connect via ssh root@192.168.1.50?

I attach the print

no, I cannot enter the web interface or connect via ssh

 

[hd--]

if you want to use dhcp change the entry to:

auto vmbro
iface vmbr0 inet dhcp
    bridge-ports enp3s0
    bridge-stp off
    bridge-fd 0

What are your dhcp settings, your network range and the ip address of the pc you try to connect to the host ?
FYI If the system is installed correctly, it obtained an ip address from your dhcp server and sets the ip address as static ip, as your can see in your /etc/network/interfaces

 

[sismondi]

if you want to use dhcp change the entry to:

auto vmbro
iface vmbr0 inet dhcp
    bridge-ports enp3s0
    bridge-stp off
    bridge-fd 0

What are your dhcp settings, your network range and the ip address of the pc you try to connect to the host ?
FYI If the system is installed correctly, it obtained an ip address from your dhcp server and sets the ip address as static ip, as your can see in your /etc/network/interfaces

I prefer to have a static IP if possible

Attached capture of the information.

ipconfig of my notebook:

Vínculo: dirección IPv6 local. . . : fe80::540e:843f:7331:1cad%3
Dirección IPv4. . . . . . . . . . . . . . : 192.168.1.116
Máscara de subred . . . . . . . . . . . . : 255.255.255.0
Puerta de enlace predeterminada . . . . . : 192.168.1.1

If I install proxmox choosing my onboard card, everything works perfectly. I really don't know what's happening.

 

[sismondi]

Similar https://forum.proxmox.com/threads/proxmox-8-clients-cant-get-ip-from-dhcp-server.129538/

 

[hd--]

So from your output it does not look like any problem with your dhcp setting.
Proxmox VE was assigned an ip address from your dhcp server at installation (192.168.1.50) which is in the correct ip-address space.
Also your host has a correct ip address (192.168.1.116) in the same network. So from a network perspective you should be able to connect to the proxmox installation.
If this is still not the case, i assume that there is a either a problem on a lower level(1), with the hardware(2) or a firewall is intercepting the traffic(3).
(1) Can you print the output (show a picture) of
# journalctl -e -b 0
(2) Please verify that the 10G network card is working using a vanilla debian live installation.
(3) Do you channel the traffic in any way through a firewall or have you activated the firewall in Proxmox VE ?

 

[sismondi]

So from your output it does not look like any problem with your dhcp setting.
Proxmox VE was assigned an ip address from your dhcp server at installation (192.168.1.50) which is in the correct ip-address space.
Also your host has a correct ip address (192.168.1.116) in the same network. So from a network perspective you should be able to connect to the proxmox installation.
If this is still not the case, i assume that there is a either a problem on a lower level(1), with the hardware(2) or a firewall is intercepting the traffic(3).
(1) Can you print the output (show a picture) of
# journalctl -e -b 0
(2) Please verify that the 10G network card is working using a vanilla debian live installation.
(3) Do you channel the traffic in any way through a firewall or have you activated the firewall in Proxmox VE ?

I finally managed to get the web interface working.

I connected the Aquantia network card to a 1G port on the switch instead of a 10G port.

Now everything works, although logically not at the maximum speed of the network card.

I think there is some problem in the kernel with the drivers. I installed OMV 6 and same situation, in 1g it works and in 10g it doesn't work.

(1) I paste the information taken (but running at 1g)

root@pve1:~# journalctl -e -b 0
Jan 17 16:10:17 pve1 sshd[1896]: pam_unix(sshd:session): session opened for use>
Jan 17 16:10:17 pve1 systemd[1]: Created slice user-0.slice - User Slice of UID>
Jan 17 16:10:17 pve1 systemd[1]: Starting user-runtime-dir@0.service - User Run>
Jan 17 16:10:17 pve1 systemd-logind[968]: New session 1 of user root.
Jan 17 16:10:17 pve1 systemd[1]: Finished user-runtime-dir@0.service - User Run>
Jan 17 16:10:17 pve1 systemd[1]: Starting user@0.service - User Manager for UID>
Jan 17 16:10:17 pve1 (systemd)[1924]: pam_unix(systemd-user:session): session o>
Jan 17 16:10:17 pve1 systemd[1924]: Queued start job for default target default>
Jan 17 16:10:17 pve1 systemd[1924]: Created slice app.slice - User Application >
Jan 17 16:10:17 pve1 systemd[1924]: Reached target paths.target - Paths.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target timers.target - Timers.
Jan 17 16:10:17 pve1 systemd[1924]: Listening on dirmngr.socket - GnuPG network>
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent-browser.socket - Gnu>
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent-extra.socket - GnuPG>
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent-ssh.socket - GnuPG c>
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent.socket - GnuPG crypt>
Jan 17 16:10:17 pve1 systemd[1924]: Reached target sockets.target - Sockets.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target basic.target - Basic System.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target default.target - Main User T>
Jan 17 16:10:17 pve1 systemd[1924]: Startup finished in 132ms.
Jan 17 16:10:17 pve1 systemd[1]: Started user@0.service - User Manager for UID >
Jan 17 16:10:17 pve1 systemd[1]: Started session-1.scope - Session 1 of User ro>
Jan 17 16:10:17 pve1 sshd[1896]: pam_env(sshd:session): deprecated reading of u>
lines 978-1000/1000 (END)
Jan 17 16:10:17 pve1 sshd[1896]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jan 17 16:10:17 pve1 systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Jan 17 16:10:17 pve1 systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Jan 17 16:10:17 pve1 systemd-logind[968]: New session 1 of user root.
Jan 17 16:10:17 pve1 systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Jan 17 16:10:17 pve1 systemd[1]: Starting user@0.service - User Manager for UID 0...
Jan 17 16:10:17 pve1 (systemd)[1924]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Jan 17 16:10:17 pve1 systemd[1924]: Queued start job for default target default.target.
Jan 17 16:10:17 pve1 systemd[1924]: Created slice app.slice - User Application Slice.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target paths.target - Paths.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target timers.target - Timers.
Jan 17 16:10:17 pve1 systemd[1924]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Jan 17 16:10:17 pve1 systemd[1924]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target sockets.target - Sockets.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target basic.target - Basic System.
Jan 17 16:10:17 pve1 systemd[1924]: Reached target default.target - Main User Target.
Jan 17 16:10:17 pve1 systemd[1924]: Startup finished in 132ms.
Jan 17 16:10:17 pve1 systemd[1]: Started user@0.service - User Manager for UID 0.
Jan 17 16:10:17 pve1 systemd[1]: Started session-1.scope - Session 1 of User root.
Jan 17 16:10:17 pve1 sshd[1896]: pam_env(sshd:session): deprecated reading of user environment enabled

(2) It is not broken. At least at 1g it works.

(3) no firewall

 

[hd--]

Good to hear that your network card works with 1G.
Could you print the output of ethtool <ethxyz> (please change the name) and also the journalctl -e -b 0 when connected to the 10G Port ?