Ah, that is just legacy. Ironically, when I updated the code manually to mitigate this problem, I deleted the root user. Lol. Still, there may still be users out there from the Vyatta days that still have it there. Off topic here but I am also a PPPoE user and am now running the latest version with all the recent PPPoE re-write and all is working fine.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Feb 27 2020
Feb 27 2020
c-po added a comment to T2072: Shell autocomplete of option (config node) with quoted value doesn't work.
For TLS crypt please see T2075
c-po changed the status of T2075: Add support for OpenVPN tls-crypt file option from Open to In progress.
looking at your config I see the issue, it is b/c you define a root user which triggered an exception. I will fix the code to mitigate this bug.
Thanks for testing and reporting.
Unknown Object (User) changed the status of T2074: VyOS docker container: Cannot configure ethernet interface from Open to In progress.
Unknown Object (User) created T2074: VyOS docker container: Cannot configure ethernet interface.
i think, you sould use crux branch for 1.2 build, current branch is 1.3
This should actually be possible after the PPPoE interface rewrite in the latest rolling image.
No answer from user.
Feb 26 2020
Feb 26 2020
c-po added a comment to T2072: Shell autocomplete of option (config node) with quoted value doesn't work.
Yes there are definately other places like DHCP.
jjakob added a comment to T2072: Shell autocomplete of option (config node) with quoted value doesn't work.
I personally don't mind the raw options, and there are other people using them too (T127, T1246, T1383, T1421, T1430).
There is no option for tls-crypt, just tls-auth. Also I'm experimenting with the various mtu options (tun-mtu, link-mtu, mssfix, fragment) and keepalive options (ping-restart, ping) that can't be set through the existing keepalive options (keepalive doesn't take 0 as a value if I want ping-restart 0 for example, and there's no way to not have keepalive be set with default vaules). So yeah, if all of these options were integrated, I personally wouldn't need the openvpn-options. But I think there are other places that use raw values with quotes that are affected by the autocompletion bug too, dhcp-server for example.
c-po added a comment to T2072: Shell autocomplete of option (config node) with quoted value doesn't work.
Thats the downside of those nodes which allow passing raw values down the config. I never liked them and they should be removed. The CLI should be extended to support the raw options instead.
daniil raised the priority of T2073: ipoe-server: reset op-mode command for sessions from Wishlist to Low.
daniil changed the subtype of T2073: ipoe-server: reset op-mode command for sessions from "Task" to "Feature Request".
jjakob renamed T2072: Shell autocomplete of option (config node) with quoted value doesn't work from utocomplete option (config node) with quoted value to Shell autocomplete of option (config node) with quoted value doesn't work.
Feb 25 2020
Feb 25 2020
There you go
Could you provide me with your full 1:1 configuration (paswords can be omitted)? Then I check again
c-po moved T2070: Rewrite (dis-)connect op-mode commands in XML and Python from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po closed T2070: Rewrite (dis-)connect op-mode commands in XML and Python, a subtask of T1318: PPPoE client CLI redesign, as Resolved.
c-po renamed T2070: Rewrite (dis-)connect op-mode commands in XML and Python from Rewrite connect/disconnect command sin XML/python to Rewrite (dis-)connect op-mode commands in XML and Python.
c-po changed the status of T2070: Rewrite (dis-)connect op-mode commands in XML and Python from Open to In progress.
c-po changed the status of T2070: Rewrite (dis-)connect op-mode commands in XML and Python, a subtask of T1318: PPPoE client CLI redesign, from Open to In progress.
c-po moved T1971: Missing modules in initrd.img for PXE boot from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.5) board.
Feb 24 2020
Feb 24 2020
Unknown Object (User) added a comment to T2051: Throughput anomalies.
Robert did new tests on his GNS3 lab (results attached).
weird-rolling.ods4 KBDownload
Unknown Object (User) changed the status of T2069: PPPoE-client does not works with service-name option from In progress to Needs testing.
hagbard changed the status of T2067: pppoe-server: Add possibility set multiple service-name from Needs testing to Backport candidate.
c-po added a comment to T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses.
Unknown Object (User) added a comment to T2069: PPPoE-client does not works with service-name option.
PR for 1.3-rolling https://github.com/vyos/vyos-1x/pull/228
dirkjanm added a comment to T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses.
FWIW, this issue is still occuring on 1.3 rolling (1.3-rolling-202002180217) for interfaces with DHCP set. While the above referenced repository is archived, the script here https://github.com/vyos/vyos-vmwaretools-scripts/blob/current/scripts/resume-vm-default.d/ether-resume.py seems to be the latest version.
For any interface with DHCP enabled, it will try to run
ip address add dhcp dev ethX
Since dhcp is not a valid address this fails and after the interface loses it's IP until dhclient is run manually or the system reboots. The script linked by @dmaasland works correctly.
Unknown Object (User) changed the status of T2069: PPPoE-client does not works with service-name option from Open to In progress.
thomas-mangin moved T2057: Generalised Interface configuration from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
The patch is ready for inclusion.
This work raised an issue with the current pattern of using Interface(..).remove() which is used in VLANIf as it requires Interface to know that EthernetIf can not be deleted (an implementation detail which should remain in EthernetIf).
Unknown Object (User) claimed T2069: PPPoE-client does not works with service-name option.
Unknown Object (User) added a comment to T2067: pppoe-server: Add possibility set multiple service-name.
@hagbard thanks, works as expected. I think this might be backport candidate to 1.2.X
Unknown Object (User) created T2069: PPPoE-client does not works with service-name option.
c-po changed the status of T1748: vbash: beautify tab completion output/line breaks from Open to In progress.
hagbard changed the status of T2067: pppoe-server: Add possibility set multiple service-name from In progress to Needs testing.
https://github.com/vyos/vyos-1x/commit/d9fa3fb7d7613cd5d6297115da0dc63462d4cf69
@Dmitry next rolling will have it enabled, let me know if it works for you as intended.
Feb 23 2020
Feb 23 2020
hagbard changed the status of T2067: pppoe-server: Add possibility set multiple service-name from Open to In progress.
This is the bottom of the config that fails the upgrade
Hi, That wasn't the problem. I did remove some of the config. I must have left a bit.
removing the check makes it work like a charme push request incomming..
c-po changed the status of T2050: Problem migrating from 1.3-rolling-202002050217 to current from Open to On hold.
On first glance this looks to me like zone policy issue.
c-po changed the status of T1971: Missing modules in initrd.img for PXE boot from In progress to Backport pending.
c-po edited projects for T1971: Missing modules in initrd.img for PXE boot, added: Ready for Crux (1.2.x), VyOS 1.2 Crux (VyOS 1.2.5); removed VyOS 1.2 Crux.
c-po moved T1971: Missing modules in initrd.img for PXE boot from Need Triage to Finished on the VyOS 1.3 Equuleus board.
A fix for this is available in the latest rolling release
c-po changed the status of T1971: Missing modules in initrd.img for PXE boot from Open to In progress.
run into the same. If I add parameters default 'no-ipv4-unicast' to my config and commit I get the waring above. All runs fine, cause the sessions where already configured before.
If I do a reboot, bgp config in frr is neartly empty only "router bgp 64512" was there not more. Removing it and do an commit nothing changed. Removing it an reboot helped.
Unknown Object (User) created T2067: pppoe-server: Add possibility set multiple service-name.
c-po moved T1998: Update FRR to 7.3 from Backport Candidates to Finished on the VyOS 1.3 Equuleus board.
c-po moved T1998: Update FRR to 7.3 from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.5) board.
c-po closed T2055: Remove IPv6 router-advert options for PPPoE, a subtask of T1318: PPPoE client CLI redesign, as Resolved.
c-po moved T2055: Remove IPv6 router-advert options for PPPoE from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po closed T1318: PPPoE client CLI redesign, a subtask of T1579: Rewrite all interface types in new XML/Python style, as Resolved.
c-po moved T1318: PPPoE client CLI redesign from Need Triage to Finished on the VyOS 1.3 Equuleus board.
syncer changed the subtype of T2065: VyOS 1.3 Don't set daemon in openvpn-{intf}.conf file from "Feature Request" to "Bug".
yun changed Difficulty level from unknown to easy on T2065: VyOS 1.3 Don't set daemon in openvpn-{intf}.conf file.
Feb 22 2020
Feb 22 2020
c-po moved T2063: vyos-salt-minion package is missing from vyos-world from In Progress to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2063: vyos-salt-minion package is missing from vyos-world from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po added a parent task for T1969: OSPF with WireGuard cause Route Inactive: T1998: Update FRR to 7.3.
Feb 21 2020
Feb 21 2020
Pull Request: https://github.com/vyos/ppp-upstream/pull/2