cat /opt/vyatta/share/vyatta-op/templates/reboot/node.def help: Reboot the system run: sudo ${vyos_op_scripts_dir}/powerctrl.py --reboot
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 3 2019
c-po closed T1840: PPPoE doesn't not rename pppX to pppoeX as Resolved.
Mon, Dec 2, 19:52 · VyOS 1.3 Equuleus
On the other hand it still can live in the interface directly which would spare the migrator. VLANs are a good example - I‘ve written a common function to parse it in each interface. I am not fully convinced on any implementation be it under an interface or as dedicated service.
Dec 2 2019
That is definately much better then before. But it doe not fix the second problem.
Works as expected. Now I can use VyOS 1.3 on my PPPoE link(s)
If we replace string 108 in file /usr/libexec/vyos/op_mode/powerctrl.py
Backported
In rolling this was fixed T1204, we need add this to crux.
Dec 1 2019
https://phabricator.vyos.net/T1228 sent the bug and I backported from upstream . The PR is in T1228 but needs to be merged into our package which I don't have permissions for.
as far as i know the content of the platform field is the first characters from sysdescr (20 characters?). on one of my devices this is
System Description: Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 15.0(2)SE8, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2015 by Cisco Systems, Inc. Compiled Thu 14-May-15 02:39 by prod_rel_team
As noone complained that this option is not working (and it is an extension to regular ppp) I propose to remove it.
This is not possible as it requires changing the C source code of vyatta-bash during runtime.
Nov 30 2019
Yes, I know that the best way to do is a python rewriting from perl, I love perl :-(
This should be done when rewriting the whole flow-accounting portion
Nov 29 2019
An alpha version can be found here: https://github.com/c-po/vyos-1x/tree/pppoe-rewrite
After looking into this, the problem seems bigger than originally thought. If the syslog config is being removed from the config the syslog.py script is called and syslog stopped. However if the system is rebooted the init system starts syslog and the config is not calling the script since there is no 'system syslog' node in the config. systemctl disable rsyslog doesn't work some type of depend unit is starting it during reboot.
tested successfully
Nov 28 2019
@ekim seems this issue with kernel and your device. If I build custom stable kernel for VyOS installed on same device without CONFIG_PINCTRL_CHERRYVIE all works properly.
Can you show cat /pro/interrupt output for confirm this?
You can also change /boot/grub/grub.cfg add noapic and reboot device.
menuentry "VyOS 1.2.3 linux (Serial console)" { linux /boot/1.2.3/vmlinuz boot=live noapic quiet rootdelay=5 vyos-union=/boot/1.2.3 console=tty0 console=ttyS0,9600 initrd /boot/1.2.3/initrd.img }
Can you confirm that with grub modification after reboot all works correct?
aone migrator for all interfaces is sufficient (see mew bridge interface and migrator 0-to-1 in interfaces)
Yes, I think set service ra interface ... or something like that might be the best option. That would eliminate the template generator script all together and I was thinking to remove interface by interface from the generator, as the rewrite progresses.
Since it needs a migrator script for each interface then as well, even if the option are the same.
How is it planned to implement this in the new style configuration? As own service bound to interfaces (denest) or as part of an interface?
Thanks, should be backported to crux then as I found it there
Next rolling will have it included.
done
Gotcha, I start implement it for the rolling release for now. Since it affects multiple other nodes as well, I'll do it for all of them equally. aka facility has no constraint and completion help too. There are a few more I've found, so I crawl through all of them and enhance it a bit.
need to merge it into crux
This patch successfully tested on VyOS 1.2.3
vyos@vyos# run show snmp mib ifmib lo: ifIndex = 1 ifAlias = lo ifDescr = lo eth0: ifIndex = 2 ifAlias = eth0 ifDescr = eth1: ifIndex = 3 ifAlias = eth1 ifDescr = eth2: ifIndex = 4 ifAlias = eth2 ifDescr = eth3: ifIndex = 5 ifAlias = eth3 ifDescr =
Nope, I was talking about completionHelper, which is not implemented - same as constraint nodes for udp/tcp regex.
Nov 27 2019
@c-po I used the 1.2.3 iso from the download portal and can't reproduce the issue. The help message was also already there since it was (re)implemented, could it be an issue with your installation?
@Merijn I will build and run a sanity check, and then we can merge into rolling for testing; I'll confirm when done. Thanks again for the offer to test.
@jestabro i am not able to build the vyos-1x package because of dependencies on other packages.
Can we include them in rolling so i can test tomorrow?
@jestabro i have encountered the first situation in my networks where i really need RFC-Complaint VRRP
(Some devices do not learn the MAC-address on the VRRP gateway, it works for some time and then stops).
Nov 26 2019
If we cancel reboot, it also write about shutdown.
The merged fix addressed the problem as it occurs in configuration mode, however, the same issue can occur during the running of migration scripts. A solution to cover all cases has been tested, and is pending.
Notice: When we run restar vrrp on MASTER, files with VRRP interfaces states stored in /run/vyos/vrrp/ don't deleted. Next time scripts not running, because already have some state.
We need review this task with T1350
This appears to be fixed in 1.2.4 EPA1.
Nov 25 2019
This is still broken for me on the most recent 1.3 rolling releases:
how can this be invalid and closed? The error is still there on a Crux build of this week...