Anything in network settings after add a setting by hand

S

S0meone Else

New Member
Dec 12, 2023
6
0
1
Hello everyone,

I wanted to add a wifi setting for my proxmox 8 using wpa_supplicant and now i have this :
Capture d’écran 2024-08-12 à 15.14.57.png


my /etc/network/interface look like this :
Capture d’écran 2024-08-12 à 15.16.13.png

btw, the wpa_supplicant.conf that are stored on an SD card work perfectly.


Thanks for you help !


PS: Sorry for my bad english as you can see im french haha.
 
It's very much possible that the parser for the interfaces file doesn't understand that directive and errors out. Could you check journalctl for possible errors?
 
shanreich said:
It's very much possible that the parser for the interfaces file doesn't understand that directive and errors out. Could you check journalctl for possible errors?
Click to expand...

Code: 
root@pve:~# journalctl
Aug 12 13:08:36 pve kernel: Linux version 6.2.16-3-pve (tom@sbuild) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC>
Aug 12 13:08:36 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-3-pve root=/dev/mapper/pve-root ro quiet
Aug 12 13:08:36 pve kernel: KERNEL supported cpus:
Aug 12 13:08:36 pve kernel:   Intel GenuineIntel
Aug 12 13:08:36 pve kernel:   AMD AuthenticAMD
Aug 12 13:08:36 pve kernel:   Hygon HygonGenuine
Aug 12 13:08:36 pve kernel:   Centaur CentaurHauls
Aug 12 13:08:36 pve kernel:   zhaoxin   Shanghai
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Aug 12 13:08:36 pve kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Aug 12 13:08:36 pve kernel: x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
Aug 12 13:08:36 pve kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
Aug 12 13:08:36 pve kernel: signal: max sigframe size: 3632
Aug 12 13:08:36 pve kernel: BIOS-provided physical RAM map:
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000061d56fff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000061d57000-0x0000000061d57fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000061d58000-0x0000000062792fff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000062793000-0x0000000062793fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000062794000-0x000000006fff9fff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000006fffa000-0x00000000730f9fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000730fa000-0x00000000731e6fff] ACPI data
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000731e7000-0x00000000732a6fff] ACPI NVS
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000732a7000-0x0000000073e65fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000073e66000-0x0000000073efefff] type 20
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000073eff000-0x0000000073efffff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000073f00000-0x0000000079ffffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000007aa00000-0x000000007abfffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000007b000000-0x00000000803fffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000100000000-0x000000047fbfffff] usable
Aug 12 13:08:36 pve kernel: NX (Execute Disable) protection: active
Aug 12 13:08:36 pve kernel: efi: EFI v2.80 by American Megatrends
Aug 12 13:08:36 pve kernel: efi: ACPI=0x731e6000 ACPI 2.0=0x731e6014 TPMFinalLog=0x73254000 SMBIOS=0x73bdf000 SMBIOS 3.0=0x73bde000 MEMATTR=0x6b906018 ESRT=0x6d3>
Aug 12 13:08:36 pve kernel: efi: Remove mem79: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
Aug 12 13:08:36 pve kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
Aug 12 13:08:36 pve kernel: efi: Not removing mem80: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
Aug 12 13:08:36 pve kernel: efi: Not removing mem81: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
Aug 12 13:08:36 pve kernel: efi: Not removing mem82: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
Aug 12 13:08:36 pve kernel: efi: Not removing mem84: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map


I don't know if its the good way to type this command lol
 
S0meone Else said:
Code: 
root@pve:~# journalctl
Aug 12 13:08:36 pve kernel: Linux version 6.2.16-3-pve (tom@sbuild) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC>
Aug 12 13:08:36 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-3-pve root=/dev/mapper/pve-root ro quiet
Aug 12 13:08:36 pve kernel: KERNEL supported cpus:
Aug 12 13:08:36 pve kernel:   Intel GenuineIntel
Aug 12 13:08:36 pve kernel:   AMD AuthenticAMD
Aug 12 13:08:36 pve kernel:   Hygon HygonGenuine
Aug 12 13:08:36 pve kernel:   Centaur CentaurHauls
Aug 12 13:08:36 pve kernel:   zhaoxin   Shanghai
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Aug 12 13:08:36 pve kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Aug 12 13:08:36 pve kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Aug 12 13:08:36 pve kernel: x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
Aug 12 13:08:36 pve kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
Aug 12 13:08:36 pve kernel: signal: max sigframe size: 3632
Aug 12 13:08:36 pve kernel: BIOS-provided physical RAM map:
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000061d56fff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000061d57000-0x0000000061d57fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000061d58000-0x0000000062792fff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000062793000-0x0000000062793fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000062794000-0x000000006fff9fff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000006fffa000-0x00000000730f9fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000730fa000-0x00000000731e6fff] ACPI data
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000731e7000-0x00000000732a6fff] ACPI NVS
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000732a7000-0x0000000073e65fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000073e66000-0x0000000073efefff] type 20
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000073eff000-0x0000000073efffff] usable
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000073f00000-0x0000000079ffffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000007aa00000-0x000000007abfffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x000000007b000000-0x00000000803fffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 12 13:08:36 pve kernel: BIOS-e820: [mem 0x0000000100000000-0x000000047fbfffff] usable
Aug 12 13:08:36 pve kernel: NX (Execute Disable) protection: active
Aug 12 13:08:36 pve kernel: efi: EFI v2.80 by American Megatrends
Aug 12 13:08:36 pve kernel: efi: ACPI=0x731e6000 ACPI 2.0=0x731e6014 TPMFinalLog=0x73254000 SMBIOS=0x73bdf000 SMBIOS 3.0=0x73bde000 MEMATTR=0x6b906018 ESRT=0x6d3>
Aug 12 13:08:36 pve kernel: efi: Remove mem79: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
Aug 12 13:08:36 pve kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
Aug 12 13:08:36 pve kernel: efi: Not removing mem80: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
Aug 12 13:08:36 pve kernel: efi: Not removing mem81: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
Aug 12 13:08:36 pve kernel: efi: Not removing mem82: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
Aug 12 13:08:36 pve kernel: efi: Not removing mem84: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map


I don't know if its the good way to type this command lol
Click to expand...

That's only the beginning of the logs, which probably contain a lot more stuff. You can export logs via the following command

Code: 
journalctl -b > syslog.txt
 
Did you just start the machine? The logs with this command are only shown until the last time the machine booted (which seems to be only a few minutes ago).

In this case, you would need to navigate to the Network panel at least once after you booted in order for any possible errors to show up in the txt file.
 
shanreich said:
Did you just start the machine? The logs with this command are only shown until the last time the machine booted (which seems to be only a few minutes ago).

In this case, you would need to navigate to the Network panel at least once after you booted in order for any possible errors to show up in the txt file.
Click to expand...

I connected the web interface and i left my server like that waiting your response. That's the new journal :

PS : I re enter the network menu several times before doing again this command : journalctl -b > syslog.txt
 

Attachments

  • syslog.txt
    180.3 KB · Views: 1
Last edited:
After further investigations, this problem seems to happen when I installed wpasupplicant.

Is there a way to use wpasupplicant on proxmox without issues ?



My wifi card connect without issues on my wifi but as I understand, it make every network config hided from the network menu :/
 
Last edited:
You could try to move the network configuration for the wifi inside /etc/network/interfaces.d and then source the file from there in your /etc/network/interfaces
 
shanreich said:
You could try to move the network configuration for the wifi inside /etc/network/interfaces.d and then source the file from there in your /etc/network/interfaces
Click to expand...
Maybe but as I said, the issue with the network menu happen when i typed :
apt install wpasupplicant -y && reboot

I tried that on an other machine a lot of time and it's seems to not be an issue with the interfaces file
 
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