@jjakob any idea?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 4 2020
I do not like this behavior as the config states the interface is "not disabled" but from an OS point of view it is - this is inconsistent and thus simply wrong.
Main reason would be I guess this error:
Jun 4 16:39:55 LR1 openvpn-vtun1[21166]: Could not determine IPv4/IPv6 protocol Jun 4 16:39:55 LR1 openvpn-vtun1[21166]: SIGUSR1[soft,init_instance] received, process restarting
Jun 2 2020
Wide dhcp6c does not generate a lease file, so if we want this we need to switch back to dhclient which has other drawbacks.
No feedback received "in time". Closing after a year.
VyOS 1.2.5 uses FRR 7.3, VyOS 1.2.6 will come with FRR 7.3.1 and rolling already runs on FRR 7.3.1
I also can not reproduce this issue with 3GB of RAM and two one ipv4/ipv6 full feed and a half feed. Closing this.
@hexes please provide exact version number "current" does not really help in this case as definately something else is going on with 1.3-rolling-202006011159
Unfortunately I receive a different error:
Jun 1 2020
vyos@vyos:~$ wake-on-lan interface eth0.201 host a:b:c:d:e:f