User Details
- User Since
- Jun 16 2022, 8:22 PM (93 w, 11 h)
Jan 5 2024
Aug 9 2023
I admit my setup isn't really the most common for production, but for the home lab crowd it might be ok. Realtek makes many network chip models I assume and their implementation might also vary from board manufacturer to another.
About not using VMware - that's a tougher ask :)
Aug 7 2023
The way I use it is a bit weird. I have ESXi installed on the host and since it has no driver for it, i pass it through to vyos and then bridge it with a vmxnet interface so that hosts in the same virtual switch can use that interface instead of the usb one I use for ESXi remote access.
Aug 6 2023
Jan 28 2023
Jan 24 2023
There is also a service called "pppd-dns.service" that references "/etc/ppp/ip-down.d/0000usepeerdns", this service is enabled by default and fails on new installs.
It should be disabled and optionally, the file removed too.
Oct 9 2022
I think this needs to be backported to 1.3 too
Sep 29 2022
@pasik you can build your own image: https://github.com/vyos/vyos-build/compare/equuleus...fvlaicu:vyos-build:equuleus-1.3.2
@pasik the problem is with the igc driver in the 5.4 kernel, not with vyos.
Aug 14 2022
@dmbaturin, here are the changes I made: https://github.com/vyos/vyos-build/compare/equuleus...fvlaicu:equuleus
I'm using the 1.4 kernel in 1.3.
Jun 20 2022
vyos@gw:~$ show version
yes, I had to do a bit of hacking - i.e. use the 1.4 kernel configs and patches, removed the wirguard-modules package, install the backports open-vm-tools version.
I committed those changes in my fork:
https://github.com/vyos/vyos-build/compare/equuleus...fvlaicu:equuleus
Jun 16 2022
I'm also trying to get this up and running. The latest 5.4 kernel fixes this issue, but other issues remain, like bridging not working.
Instead of backporting the driver, I ended up backporting the lataest 5.10 kernel to the 1.3 branch.