Wol on eno2 problem

U

uroh

New Member
Jul 12, 2023
7
0
1
HI, I have a problem (server not powerup) on the eno2 interface and the wol.
I have currently bypassed the problem by using eno1.
Both interfaces are 'g', however I prefer eno2 as it is more stable. Any ideas or suggestions?

Code: 
root@pve1:~# dmesg | grep eth
[    0.802057] igb 0000:03:00.0: added PHC on eth0
[    0.802073] igb 0000:03:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 90:xx:0e:60:xx:xx
[    0.802147] igb 0000:03:00.0: eth0: PBA No: 323xxxxxx
[    0.849600] igb 0000:03:00.0 eno1: renamed from eth0
[    0.916733] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 90:1b:xx:xx:xx:xx
[    0.916741] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    0.916791] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: 3131xxxxx
[    1.453399] e1000e 0000:00:19.0 eno2: renamed from eth0
[   64.287117] fwbr100i0: port 2(veth100i0) entered blocking state
[   64.287133] fwbr100i0: port 2(veth100i0) entered disabled state
[   64.288200] device veth100i0 entered promiscuous mode
[   64.349681] eth0: renamed from vethxJ0KaQ
[   69.762634] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   69.762675] fwbr100i0: port 2(veth100i0) entered blocking state
[   69.762685] fwbr100i0: port 2(veth100i0) entered forwarding state
root@pve1:~# uname
Linux
root@pve1:~# uname -a
Linux pve1 6.2.16-4-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-4 (2023-07-07T04:22Z) x86_64 GNU/Linux
root@pve1:~# lspci -nnk | grep -A2 Ether
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 05)
    DeviceName: Intel I217LM onboard LAN 2
    Subsystem: Fujitsu Technology Solutions Ethernet Connection I217-LM [1734:11f2]
    Kernel driver in use: e1000e
    Kernel modules: e1000e
--
03:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)
    DeviceName: Intel I210 onboard LAN 1
    Subsystem: Fujitsu Technology Solutions I210 Gigabit Network Connection [1734:11f1]
root@pve1:~#
 
Last edited:
Im dont know exactly your hardware but i found this . Does is this your problem?
 
uroh said:
HI, I have a problem (server not powerup) on the eno2 interface and the wol.
I have currently bypassed the problem by using eno1.
Both interfaces are 'g', however I prefer eno2 as it is more stable. Any ideas or suggestions?

Code: 
root@pve1:~# dmesg | grep eth
[    0.802057] igb 0000:03:00.0: added PHC on eth0
[    0.802073] igb 0000:03:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 90:xx:0e:60:xx:xx
[    0.802147] igb 0000:03:00.0: eth0: PBA No: 323xxxxxx
[    0.849600] igb 0000:03:00.0 eno1: renamed from eth0
[    0.916733] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 90:1b:xx:xx:xx:xx
[    0.916741] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    0.916791] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: 3131xxxxx
[    1.453399] e1000e 0000:00:19.0 eno2: renamed from eth0
[   64.287117] fwbr100i0: port 2(veth100i0) entered blocking state
[   64.287133] fwbr100i0: port 2(veth100i0) entered disabled state
[   64.288200] device veth100i0 entered promiscuous mode
[   64.349681] eth0: renamed from vethxJ0KaQ
[   69.762634] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   69.762675] fwbr100i0: port 2(veth100i0) entered blocking state
[   69.762685] fwbr100i0: port 2(veth100i0) entered forwarding state
root@pve1:~# uname
Linux
root@pve1:~# uname -a
Linux pve1 6.2.16-4-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-4 (2023-07-07T04:22Z) x86_64 GNU/Linux
root@pve1:~# lspci -nnk | grep -A2 Ether
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 05)
    DeviceName: Intel I217LM onboard LAN 2
    Subsystem: Fujitsu Technology Solutions Ethernet Connection I217-LM [1734:11f2]
    Kernel driver in use: e1000e
    Kernel modules: e1000e
--
03:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03)
    DeviceName: Intel I210 onboard LAN 1
    Subsystem: Fujitsu Technology Solutions I210 Gigabit Network Connection [1734:11f1]
root@pve1:~#
Click to expand...

try this:
nano /etc/network/interface

under vmbr0 (or what bridge or interface number is) add this command

post-up /sbin/ethtool -s eno2 wol g


you can use this command for all interfaces
 
Last edited:
unfortunately it doesn't work!
The wol continues to work on the I210 with the igp drivers (eno1), while the server fails with the magic packet on the eno2 on the onboard lan I217-LM with the e1000e drivers.
Very strange!

Code: 
root@pve1:~# ethtool eno2
Settings for eno2:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: 1000Mb/s
    Duplex: Full
    Auto-negotiation: on
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    MDI-X: off (auto)
    Supports Wake-on: pumbg
    Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: yes
   
   
    ######
   
   
    root@pve1:~# ethtool eno1
Settings for eno1:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: 1000Mb/s
    Duplex: Full
    Auto-negotiation: on
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    MDI-X: off (auto)
    Supports Wake-on: pumbg
    Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: yes
 
Last edited:
Yes!
Code: 
root@pve1:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno2
iface eno2 inet manual

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.2.39/24
        gateway 192.168.2.1
        bridge-ports eno1 eno2
        bridge-stp off
        bridge-fd 0
        post-up /sbin/ethtool -s eno2 wol g

root@pve1:~#
 
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