Search results

yeah, last two line command may not need because my summary was to short and lack too much information last two line command may solve this problem at all

Thanks for your post! it Really save my day . solved my problem. base on your post here is my summary: linux kernel 6.7.* above won't fit for Debian nvidia-driver and DKMS main blame on this file drm_ioctl.h solution: install old version kernel source code and take this file drm_ioctl.h...

final result: install ifupdown ppp pppoe pppoeconf remove ifupdown2 then you can use pppoeconf to setup DSL connection but lack of ifupdown2 you may missing few new features at pve7, 8 featuee like: change network setting without reboot

try this 3 commands may solve your ssh port problem systemctl disable ssh.socket systemctl stop ssh.socket reboot

Hi : I hit the same problem at ct image debian11 sshd won't accept my change ssh port at sshd_config after I edited sshd_config and restart sshd service I got new ssh port but when I reboot ct , it will back to 22port it seems this bug from ct image debian10,11 and debian12 still has this bug...

maybe you can tell us about your network topology and your switch model type and your NIC port enp24s0f0 , enp24s0f1 plug into the same switch or not?

yeah, I use LACP for two things 1. 10G+10G so I got 20G bandwidth 2. prevent network failure , like: unplug one wire , server still online

here is my interfaces for your reference auto lo iface lo inet loopback #Intel X540-AT2 iface enp65s0f0 inet manual iface enp65s0f1 inet manual auto bond0 iface bond0 inet manual bond-slaves enp65s0f0 enp65s0f1 bond-miimon 100 bond-mode 802.3ad bond-xmit-hash-policy...

if you don't know why can I have two gateway at /etc/network/interfaces then your problem may not at how to use pve server at basic network knowledge

problem at here : gateway 192.168.0.1 192.168.0.1 NAT function has problem go to check this machine 192.168.0.1 and you can not have two gateway at /etc/network/interfaces only one gateway was correct

do you have switch with vlan function? do you plug pve8 at switch trunk port? can you show your /etc/network/interfaces content?

those command can be simplify like this: apt install -y aptitude aptitude remove -y ifupdown2- pve-manager= proxmox-ve= aptitude install -y pppoe pppoeconf aptitude unhold pve-manager proxmox-ve

how to install pppoe and pppoeconf here is what I do: # apt install aptitude # aptitude remove ifupdown2 The following packages will be REMOVED: ifupdown2 0 packages upgraded, 0 newly installed, 1 to remove and 66 not upgraded. Need to get 0 B of archives. After unpacking 1,777 kB will be...

cisco image has 2 type: Dynamips: old school Cisco device simulated IOL: IOS on Linux alsa call IOU (IOS on Unix) eve-ng Recommended IOL image dynamips is more difficult and consume more resource had you try IOL? easy than dynamips I follow this page to run IOL in eve-ng...

yeah, I guess it's source close , thanks for clarify it!

Are you use this template:ubuntu-16.04-standard_16.04.5-1_amd64.tar.gz to create CT? add-apt-repository this command is for ubuntu not for debian or host pve

Hi everyone: I use this template create a CT http://download.proxmox.com/images/system/ubuntu-22.04-standard_22.04-1_amd64.tar.zst when I wanna change ssh 22port to another port won't work. here is detail: vim /etc/ssh/sshd_config modify Port 22 to 2933 /etc/init.d/ssh restart it work...

update: EVE-NG install in LXC known issue: vSwitch network unstable hard to use it the reason may LACP only can use mode on, when you create HA vSwitch or use MLAG network .... thoese functions require LACP mode active hence MLAG or HA will fail

be careful this: EVE-NG install in LXC still has different with KVM known issue: vSwitch create LACP may fail LACP mode on will work LACP mode active won't work EVE-NG in KVM doesn't have such issue

Hi everyone: I'd like share how to run EVE-NG in LXC success here is my environment: Proxmox VE 6.4 kernel: 5.4.162-1-pve LXC template:ubuntu-16.04-standard_16.04.5-1_amd64.tar.gz LXC NIC:2 Create CT in normal way, after created CT edit /etc/pve/lxc/CTID.conf add 2 line: features: nesting=1...