Added code received via Slack ;) extreme programming.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jun 21 2020
Jun 20 2020
@thomas-mangin I hope you can have a look here. Thanks!
Picking up on the build issue
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.
Jun 19 2020
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.
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
Hi @fmertz, this is a more or less common "issue" during peak development times.
Documentation is here: https://docs.vyos.io/en/latest/services/console-server.html
I'm no fan of the raw options from dhcp and openvpn and think we should not add more of those. Unfortunately they have been inherited from Vyatta. ISC DHCP could never be replaced by any other DHCP server due to this fact which is IMHO a super bad CLI design.
I'd go with option 1 to have a well known list of working and supported LCD displays. Each will have it's own configuration template which is used when implementing. I'm not a fan of "power user options" as this usually causes more harm then good - also users tend to be overwhelmed by the number of CLI options. We rather should make adding new display types super easy with proper documentation.
Jun 18 2020
Works as expected!
This does not work in VyOS 1.2.5 either.
Jun 17 2020
Perfect. Thank You! I was against this feature the first time bit now I need it, too ;)
The boot config load mechanism has been changed by @jestabro which possibly led to resolution of this bug
@Dmitry I accidently merged this to quick. Now every RADIUS instance has a peiority node bit irs only evaluates foe system login. Can dou please fix the XML definitions to only have this for system login?
Feature now also in crux version ob libpam-radius.
Jun 16 2020
Jun 15 2020
My fault. defaultValue must pe placed outside of properties
@alexandrestein can I assume you‘re using NPTv6 on VyOS 1.2 series? If so you mind sharing an example/configuration so we can also improve our documentation?
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
dum0 172.18.254.201/32 u/u
eth0 - u/u
eth0.5 - u/u
eth0.10 - u/u
eth0.15 - u/u
eth0.201 172.18.201.10/24 u/u
eth0.202 2001:affe::201/64 u/u
eth1 fd00::ffff/64 u/u
eth2 - A/D
lo 127.0.0.1/8 u/u
::1/128vyos@vyos:~$ show config commands | grep traffic set interfaces pppoe pppoe0 traffic-policy out 'QoS' set traffic-policy shaper QoS bandwidth '50mbit' set traffic-policy shaper QoS default bandwidth '100%' set traffic-policy shaper QoS default queue-type 'fq-codel' vyos@vyos:~$ tc class show dev pppoe0 vyos@vyos:~$
Please also share your NAT configuration
Jun 14 2020
Probably is can be set in a curlrc file which is populated from CLI options