Windows 11 on ARM, no network

Buster14 commented 3 months ago

Hi I followed your guide here precisely, pi5 + windows 11 ltsc 2024 iot but there's 1 thing i cant replicate, the network

https://github.com/jiangcuo/Proxmox-Port/wiki/Windows-11-arm64

How do you create e1000 bridge? Proxmox GUI wont let me create that name, bridge ports cannot find that ethernet.. is there any network config that must be done beforehand?

Buster14 commented 3 months ago

Let me update what i've tried :

creating virtual nic named e1000 doesn't work, perhaps cause proxmox wont allow it as described here https://pve.proxmox.com/wiki/Network_Configuration
```
Naming Conventions
We currently use the following naming conventions for device names:
```

Ethernet devices: en*, systemd network interface names. This naming scheme is used for new Proxmox VE installations since version 5.0.

Ethernet devices: eth[N], where 0 ≤ N (eth0, eth1, …) This naming scheme is used for Proxmox VE hosts which were installed before the 5.0 release. When upgrading to 5.0, the names are kept as-is.

Bridge names: Commonly vmbr[N], where 0 ≤ N ≤ 4094 (vmbr0 - vmbr4094), but you can use any alphanumeric string that starts with a character and is at most 10 characters long.

Bonds: bond[N], where 0 ≤ N (bond0, bond1, …)

VLANs: Simply add the VLAN number to the device name, separated by a period (eno1.50, bond1.30)

This makes it easier to debug networks problems, because the device name implies the device type.


- Installing network driver virtio : 
Virtio : Install redhat vnic using virtio driver, but even with static ip it wont ping outside network, it says no network found.
E1000, VMWare, Realtek : no drivers found on virtio

Buster14 commented 3 months ago

Solved, i followed pymylife's guide and redo the whole thing and it's working. Not sure why it isnt working with this method.

jiangcuo / Proxmox-Port

Windows 11 on ARM, no network #95