This is a known Issue on Debian 8 and reported multiple times. As a fix would require rebuilding coreurils we just stick with the debian version. Equuleus has this already resolved
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Apr 17 2020
I'd also recommend not using a variable named stdout later on since it's very confusing (easily confused with sys.stdout, which took me a minute to figure out).
I've found that on the most recent releases of VyOS, Netflow flow-accounting is also broken. I've managed to fix the first 2 errors I encountered and verify uacctd is indeed running; however, if IPv6 is used, another error is encountered which I did not fix. I also probably did not fix Sflow entirely with these changes.
Initial error:
vyos@cr01a-vyos# commit [ system flow-accounting buffer-size 2048 ]
Apr 16 2020
PR for other servers https://github.com/vyos/vyos-1x/pull/350
cpo@LR2.wue3:~$ show ver Version: VyOS 1.2-release-train-202004161900 Release Train: crux
I can confirm this bug, also exist in 1.2.5 OVA
@UnicronNL not sure where exactly you resolved it but the problem exists till now
Version: VyOS 1.3-releasetrain-202004161535 Release Train: equuleus
Hypervisor is VMware ESXi. I believe these were installed from OVA several
months ago, but haven't reproduced recently.
Is 1.2.3 was deployed from OVA or install from ISO?
Which hypervisor?
This is really a good feature i hope i can see this feature in LTS version soon
https://github.com/vyos/vyos-1x/pull/342 should add IPv6 support for all use cases (server, listening socket, p2p, client).
The script now prints a warning on commit if the server client IP is in the pool. There is a new config node for setting the pool start/stop/netmask/disable, if not set, the defaults of openvpn are used.
Some other people reporting similar here.
Apr 15 2020
Yes, that changed it: neither single or double quotes worked previously --- with the change to use crypt(), single quotes around plaintext password with (those) special characters now works; double quoted special characters are still interpreted.
No it's the shell interpreting from Popen (cmd), but you may have already resolved this by using the library function; I'll check.
@jestabro is this probably another case for the CLI input reading discussion we hat the other day about special characters?
Ah, I missed that it's for 1.2, 1.3 has a newer isc-dhcp.
The previous commit didn't fix it, this one does: https://github.com/vyos/vyos-1x/pull/348
PR for fixing this issue https://github.com/vyos/vyos-1x/pull/347
After drawing some use cases I will propose to modify auth schema by LUA
As noted earlier in the ticket, this is a problem with the version of ISC DHCPD that VyOS 1.2.x is shipping. It's a very old version.
This issue exists in firmware 6.8 and 7.1.
Starting with 7.1 i can see that the disable command 'sudo ethtool --set-priv-flags <interface name> disable-fw-lldp on' also works.
@c-po this is just DHCP-client in this case, Windows, Linux or VPC (Virtual PC).
My first thought would be something wrong with offloading on the NIC -
there was a change recently that turns all the offloading settings on by
default, you can disable some in the ethernet config. My suggestion to
leave the default disabled and enable it on demand wasn't taken into
account.
@trae32566 the reason I used the call is b/c it was the call used in VyOS 1.2 - no particular reason to not look into crypt()
@Dmitry how can I test the IPoE server? Is there a client for Windows or a "howto"?
Any reason in particular you're not using crypt.crypt() here?
Still facing the issue of two initrd images for building iso using latest latest crux branch. Using this kernel rebuilding steps https://wiki.vyos.net/wiki/Rebuild_VyOS_kernel_Step#VyOS_1.2.x
I'm seeing this in Vyos 1.2.5 just released:
I've just encountered this bug with Vyos 1.2.5 (final, official ISO)
