@hagbard not a problem. Looks like we now go the "our own lib" way as pyroute2 has some flaws. DHCP is already fix and I continue improve the script and remove redundant code before it will be extended to support VLAN/bonding.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Sep 1 2019
Aug 31 2019
@c-po sorry was camping in a remote area without cell coverage. What's the way we go then? I'll look tomorrow, eventually Tuesday next week into the dhcp stuff.
Cherry-picked into crux.
@zsdc please follow up on this
@zsdc can you follow up on this
Thanks!!!! I'll test it once it's pulled...
@rgrant I've cherry-picked it into Crux, will be in the 1.2.3 release soon.
+1 to this. I have VyOS running on several serial-console-only devices (they do have a graphics card on the chipset but it has no connector and is disabled in BIOS).
The console works in GRUB and once fully booted (login screen) but the boot console messages (kernel) still go to the video console. I have console device ttyS0 set in config, but every "install system image" resets the GRUB default entry to KVM console.
After recovering ping flood won't work ping for ipv6, because always run ping command instead ping6
vyos@vyos:~$ ping 2001:4860:4860::8888 ping: unknown host 2001:4860:4860::8888
DHCP + DHCPv6 working now in bridge interface.