Fixed as part of T2486
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 22 2020
Fixed as part of T2486
The above PR419 did not fix the issue as a wrong pdns-recursor process name was used (its real name is 'pdns-rec/worker'). It was fixed as part of T2486.
That's great, I like the config syntax. What does the interface alias do regarding the display? Maybe it could be read from the interface description? Then again the display name needs to be short as the displays are small and the interface description can be longer. Maybe default to reading the alias from the interface description and override it with the display alias.
For starting services in 1.3 we use systemd, it's simple to create new service files in src/systemd that will be put in /lib/systemd/system. Just make sure they're started manually by the config script and not as part of a target (just creating a service file without the Install section should ensure that).
FWIW, this integration package is coming along nicely. I was able to create the XML CLI. The python code is kept to a minimum by passing a dictionary of the Config to the template engine "render". At this point, I can generate the proper LCDd.conf and lcdproc.conf based on the CLI. I now need to work on start/stop/restart as well as (basic) config validation. I have nothing for lcdexec/menu this far.
OK, another approach question.
Jun 21 2020
I feel @Dmitry has more experience here from past topics. I hope you do not mind the reassignment.
Or use a VRF T31, closing - feel free to reopen if you think this was done wrongly.
Should be resolved via T2569
Resolved via T2569
Works as expected, tested on 1.3-rolling-202006201113
EDIT: EDITED from original for clarity
Jun 20 2020
LOL - I could have commited :-) Thanks !
Added code received via Slack ;) extreme programming.
@thomas-mangin I hope you can have a look here. Thanks!
Picking up on the build issue
EDIT: See simplified configuration below
VyOS 1.3 uses nftables for performing NAT operations. It might be possible that there is a bug in the new code. It would be interesting to get a copy of your sudo iptables-save -t nat and sudo iptables-save output on 1.2 so we can check it in 1.3.
Version: VyOS 1.3-rolling-202006200117 Release Train: equuleus
I can confirm that your change as of VyOS 1.3-rolling-202006200117 fixed the problem.
Jun 19 2020
I will do that tonight.
The next rolling ISO will have a fix for the migrations script. It would be nice if you could re-upgrade from 1.2 to additionally verify the fix besides me.
set interfaces ethernet eth0 address '2001:XXXX:YYYY:10::1/64' set interfaces ethernet eth0 address '10.0.10.1/24' set interfaces ethernet eth0 description 'Management Network' set interfaces ethernet eth0 duplex 'auto' set interfaces ethernet eth0 hw-id '52:54:00:c4:7f:61' set interfaces ethernet eth0 ipv6 dup-addr-detect-transmits '1' set interfaces ethernet eth0 ipv6 router-advert cur-hop-limit '64' set interfaces ethernet eth0 ipv6 router-advert link-mtu '0' set interfaces ethernet eth0 ipv6 router-advert managed-flag 'true' set interfaces ethernet eth0 ipv6 router-advert max-interval '600' set interfaces ethernet eth0 ipv6 router-advert other-config-flag 'true' set interfaces ethernet eth0 ipv6 router-advert prefix 2001:XXXX:YYYY:10::/64 autonomous-flag 'false' set interfaces ethernet eth0 ipv6 router-advert prefix 2001:XXXX:YYYY:10::/64 on-link-flag 'true' set interfaces ethernet eth0 ipv6 router-advert prefix 2001:XXXX:YYYY:10::/64 valid-lifetime '2592000' set interfaces ethernet eth0 ipv6 router-advert reachable-time '0' set interfaces ethernet eth0 ipv6 router-advert retrans-timer '0' set interfaces ethernet eth0 ipv6 router-advert send-advert 'true' set interfaces ethernet eth0 smp-affinity 'auto' set interfaces ethernet eth0 speed 'auto'
Version: VyOS 1.2.5+
Release Train: crux
Can you please share which 1.2 version was used and also a show configuration commands output so the issue can be reproduced easily.
@fmertz for easier developing I have a bunch of BASH aliases which are also mapped into my docker container.
Added a basic test so this issue does not re-appear on ISO build https://github.com/vyos/vyos-smoketest/commit/b38a42d9d4ab302b44d48844fae49bb0a0817d04
Fair point. In that case I agree with not including a raw config option.
As for the errors when installing vyos-1x, c-po already pointed out why this occurs.For this reason I don't rebase on upstream while working on a set of changes locally, I always try to keep the installed iso and local git state as much together as possible. I also run docker from the vyos-build repo and have the vyos-1x repo dir in vyos-build/packages/vyos-1x (where the included scripts/build-packages would put it) so I can just docker run and build without having to copy any files anywhere, just scp the built deb into the VM.
Hi @fmertz, this is a more or less common "issue" during peak development times.
At this point, i could use a couple of wise words for the development process.