FYI: https://git.zx2c4.com/wg-dynamic/about/docs/idea.md

reverted the commit. I'm not sure if a daemon would be a good idea. Another option is to allow only IP's entered via cli or checking the name whenever wg is executed, resolve the name and send it to hostd to get it written to /etc/host. That would solve at least the issue at reboot and in most cases the correct IP should be in /etc/hosts.

http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb or next rolling release should fix the issue.

@kroy You can quickly test it via setting Priority to 999 in /opt/vyatta/share/vyatta-cfg/templates/interfaces/wireguard/node.def. It's currently 459. Let me know your results, please.

https://github.com/vyos/vyatta-cfg-op-pppoe/commit/195a478b7d826ec7ff1652b99abc75d49161a882

There is not really an up or down, there is only a verified handshake and the transferred bytes. If you haven't sent and received anything, the interface is in 'unknown' state in terms of wireguard, even if it's 'up' if you look via iproute2. All can could do it checking if the endpoint resolves and if it does, send a packet and see if the handshake completes.

Can you please clarify. What is Vif mode dialing and what has a vlan id to do with multiple physical lines? Does that mean your problem is solved?

@sunser Did you try: set interfaces ethernet eth1 vif <vlanid> ... already?

https://phabricator.vyos.net/T1635 needs to be done first

yes, you need to be either able to resolve your endpoints name or have it in /etc/hosts mapped. The name is being resolved (or tried) when the wg command configures the tunnel. There is unfortunately not too much I can do against, unless implementing a probe service or something like that ( could be as simple as ping).

https://github.com/vyos/vyos-1x/commit/9b55f7c7b9ecc49e6efe075ad24a54baff719e8e

https://github.com/vyos/vyos-1x/commit/6956bfe0620638adbad36f8cdf6d312884ba82ff
https://github.com/vyos/vyos-1x/commit/0c6faf26823fb984b3e0a77ee014e20661163e44

I've tested it and can't reproduce. There are a few issues in the debian files and autoreconf, but other than that everything seems to work just fine.

There is no such thing like separate identities. You can either decrypt a package or you can't, that's about it. You basically have to hand out more public keys, you have to maintain more keys. As I mentioned before I only see currently disadvantages so far. However the user can chose what way to go and multiple options are always good. If it helps you, well that's nice to hear.

https://github.com/vyos/vyos-1x/commit/c6e9285262ddd762aac96ad3fa30d63cdeb2c6f2

https://downloads.vyos.io/rolling/current/amd64/vyos-1.2-rolling-201909231545-amd64.iso

It's in 1.2 rolling too, but the iso has to rebuild. You can alternatively download and manually install http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.3.0-16_all.deb.

https://github.com/vyos/vyos-1x/commit/eed2ba5379067ba3ef3a7b9eef72b8252958e766

Would be very nice, I tested with an old one already, but want to make sure I haven't uncovered side effects.

PR merged https://github.com/vyos/vyos-1x/pull/131

https://github.com/vyos/vyos-1x/commit/eb9c6ff745fc5d4e23c224a441874ae6fcf97ac5
@mb300sd Tomorrows rolling will have the fix applied.

https://phabricator.vyos.net/T1499

Thanks for testing.

@sever I see that the new package hasn't been autobuild in our CI, I see to get that fixed. If you are in urgent need of the change, please build and install vyos-1x manually.

Tomorrows rolling ISO will have the patch applied.
Please test and let me know how it goes.

@sever Issue found and working on a patch.

ifname  | called-sid |    calling-sid    |     ip      | ip6 | ip6-dp | rate-limit | state  |  uptime  |        sid       
----------+------------+-------------------+-------------+-----+--------+------------+--------+----------+------------------
 bond0.51 | bond0.51   | 08:00:27:82:43:ae | 192.168.0.2 |     |        |            | active | 00:01:03 | d060220ce77252a9

Auto creation of vlans failed.

@rcit Lot's of development underway and since I wasn't able to reproduce it anymoe, I thought I ask, Feel free to reopen if the issue re-occurs.

everything works without issue as far a I see.

@sever Yeah, sorry about the typo. You need to define an IP pool and an authentication method if you are not using a RADIUS server for that.
(I have bond0 in my lab so you need to change that to bond1 if you copy).

@sever Can you please try: set service pppoe-server interface bond0 vlan-id 55. And have a look into /var/log/messages what accel is reporting there once the dhcp reply arrives. I'm going to lab up your config and test as well.
Also you need to define an IP pool a client can get an IP address from.
https://vyos.readthedocs.io/en/latest/services/ipoe-server.html
(btw: show config comands gives you a nicer config overview)

@sever Can you please also share your pppoe-server config?

pushed to current too and rebuilt kernel in CI successfully.

@runar
I just cross compiled it successfully. CI uses a sed right now to correct it, all paths are now generic.
What I currently can't do is actually testing the binaries on a real device, I would appreciate it if you can do that.