- User Since
- Apr 29 2018, 3:43 PM (72 w, 6 d)
Jul 13 2019
Looking at the Jenkinsfile it seems that missing sudo is the only difference:
May 20 2019
The place that limits it to only ethernet devices seems to be: https://github.com/vyos/vyatta-cfg-system/blob/crux/templates/interfaces/pseudo-ethernet/node.tag/link/node.def (the checking itself happens at https://github.com/vyos/vyatta-cfg-system/blob/current/scripts/vyatta-interfaces.pl#L377)
Mar 11 2019
I managed to reproduce this earlier. These were the generated iptables rules and pinging from any source IP except the first one did not work. https://phabricator.vyos.net/P66
I could see the responses in tcpdump but they were getting blocked (so I assume. They did not reach the running ping program)
From the man page:
You can put the server into the PARTNER-DOWN state either by using the omshell (1) command or by stopping the server, editing the last peer state declaration in the lease file, and restarting the server.
Mar 8 2019
Mar 5 2019
Mar 4 2019
The way ISC DHCP Relay works you need to give it both the upstream and downstream interfaces (e.g. where it will listen to requests and ones where it will talk to the DHCP server). It is also shown (while not explicitly said) in the documentation: https://wiki.vyos.net/wiki/DHCP_relay
For those of you with issues with DHCP relay and VLANs, have you:
- Added the interface that the DHCP server is reachable on to the service dhcp-relay interface <interface> list?
- Added the sub-interface (e.g. eth0.20) to the interfaces instead of the parent interface (eth0)?
I was asked to test with VRRP, still works fine.
I did not manage to reproduce the issue.
Feb 28 2019
I should note that this is not my issue/task nor am I personally affected by it. I just pointed out that part of the original issue should be solved by my PR which originated from elsewhere and left my two cents about how to handle the other case here.
What comes to the quoting of openvpn-option --push "xxx", if we do not want to introduce nested quotes to the parser, maybe we should have a second configuration option dedicated to --push?
Feb 27 2019
In T1246 I noticed that while my fix makes the syntax correct enough that OpenVPN starts, it is actually missing the $variables inside the quotes as the patch changed double quotes to single quotes.
That means that instead of --push "dhcp-option DNS 18.104.22.168" or --push "route 192.168.0.0 255.255.255.0" it started with --push "dhcp-option " and --push "route "
e.g. could indeed be tested to make sure that it works
I think the issue you found might still be a valid one, even though it was not the same one that was originally talked about on IRC.
Feb 21 2019
Produced command seems to be:
Also managed to reproduce, some set-commands to help reproduction:
Jul 10 2018
Above was on 1.1.7, the same thing happens on 1.1.8:
I don't think the alphabetic order is even relevant (or ansible for that matter). Once you delete a user it frees up the UID but leaves the home directory around with the now unused UID. If you re-create users in a different order the UIDs that still own the home directories no longer match the corresponding users.