- User Since
- May 25 2018, 2:31 AM (65 w, 2 d)
Wed, Aug 21
moved get functions into properties, for ifalias, macaddr and mtu to see how it works. If the old get_ function is being used, it prints a message to the console but still works. Will see how well that works.
Thu, Aug 15
[e]ach network interface has a private key [...]
Fri, Aug 9
I don't think it's a good idea, for several reasons.
Thu, Aug 8
While documentation is on its way, below is a very small example on how to use it:
dhcp can be done via systemd or the traditional isc-dhcp client, which way should we go? systemd.networkd does link detection too and stops dhcp if the link is lost and starts it again when the link returns to state up.
Wed, Aug 7
@Dmitry PR merged in, you can test it in the next rolling tomorrow.
I have almost all requested stuff implemented, plus some more like setting mtu, mac address etc. I'm planning to include that into vyos-1x after testing.
diff --git a/scripts/build-command-templates b/scripts/build-command-templates
index a7312f7..ba80ead 100755
@@ -227,7 +227,7 @@ def make_node_def(props):
Tue, Aug 6
I'd like to make it more generic anyway, so basically it will be come a wrapper for the ip commands plus some check/find function maybe (like what mac belongs to what interface, bonding etc).
Mon, Aug 5
Thanks for the info.
Sun, Aug 4
Fri, Aug 2
I started with a few line of example code, if that would have something we wanna go with, I'll take the task. comments always welcome.
disable (up/down) is required too.
Thu, Aug 1
Wed, Jul 31
Tue, Jul 30
Mon, Jul 29
Sun, Jul 28
Fri, Jul 26
prototype successfully tested
That error will disappear once https://github.com/vyos/ppp-upstream/pull/1 has been merged in. You can meanwhile try to remove the route option and see if it makes any difference.
Jul 25 2019
@mustard Any updates?
Jul 24 2019
currently testing internally, will be released soon to the current branch.
Tested rolling from yesterday and 1.2.2, no issues.
@mustard Your ppp session looks just fine. The removal of your default route doesn't terminate the pppoe connection, at least there was no termination request in the dump. Your icmp echo request time out since you don't have a default gateway, so we need to find out why the default gateway gets removed. When you see the icmp timeouts for 220.127.116.11 your pppoe session is still alive and is answering the LCP requests successful, so I think we need to focus on frr and why it is removing the efault route.
Jul 23 2019
personally I like the below most. it will require quite an amount of work for migration.
has been fixed by reverting to 4.1 since pdns stopped supporting debian jessie.
Jul 22 2019
We may have to migrate to networkd to have that functionality, since netplug seems to cause issues with interfaces which are up and running.
@dienac any results to share?
I can't reproduce your issue, so I suspect no issues with the pppoe client we ship in vyos.
Your filter was a bit to tight, all I see are the LCP echos. I' more interested in the PAD packets, in particular what sides sends a PADT and if PADS is clean.
Jul 21 2019
your are confused with client and server commands.
Jul 19 2019
https://github.com/vyos/vyos-netplug/commit/81fd74bfbfa6daed506693ecc20deff09042bc71 broke it, I have to find out why he commited it.
Jul 18 2019
fixed via https://phabricator.vyos.net/T1065