Had been resolved already via https://phabricator.vyos.net/T1054 and is available via latest rolling release.

https://github.com/vyos/vyos-1x/commit/a29898b2ea15b7d9cea7fade1b27d38967c52d52, will be available with the next latest rolling or via: http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyos-1x/vyos-1x_1.2.0-7_all.deb

Yes it will be implemented as soon as it turns out that the switch from the old implementation was successful. We have seen kernel crashes every now and then with the shaper enabled, so I would be keen to know if that happens to you as well to investigate the root cause.

That is already the case if you don't configure a SN on the server side. So I'm not sure if this setting is not more of a pain instead of a help.

left|rightprotoport has been removed from strongswan since version 5.1. %.6 is running on the latest rolling. Protocols can now be defined via left|rightsubnet (leftsubnet=fec1::1[udp/%any],10.0.0.0/16[%any/53]) .

Ooops X-fire. I grab the IP and prefix from the interface, that way I know it exists and can be removed and won't have to many test cycles. The subsystem needs to be rewritten at one point, but as you can imagine that is quite a task. DHCPv6 won't be affected since it uses always IP/prefix, but I haven't tested it yet.

Actually it returns the IP allocated via DHCP, however the ip-normalize script needs a prefix for the regex, which is not set when dhcp was set.

Hi @andersonpcazm,
I'd suggest to open a ticket with mikrotik in that case (https://mikrotik.com/support).
The source code fro accel in the version we use in the OS can be found here: https://github.com/vyos/vyos-accel-ppp.
Feel free to contact me any time if you or mikrotek support need further details, but so far, as you found out as well, your client side (the mikrotek device) has a faulty pppoe implementation or is just misconfigured.

can you please let me know from where you have that flag? It dosn't exist in the accel-ppp documentation.

It's triggered by systemd, so it will happen before the config is fully loaded. It might be better to move that into the cli config and execute with prio 999, that way it will be definitely the last script running.

fixed and available in the next rolling release or via http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-webproxy/vyatta-webproxy_0.2.110+vyos2+current2_all.deb.

Your ISP uses mac filters then as part of AAA. No ideas why mac addresses would change, they are directly read from the NIC, the config just overwrites it then.

Nov 28 20:09:18 rc9 accel-pppoe: eth1: recv [PPPoE PADI 08:00:27:fa:3e:50 => ff:ff:ff:ff:ff:ff sid=0000 <Service-Name > <Host-Uniq 390c0000>]
Nov 28 20:09:18 rc9 accel-pppoe: eth1: send [PPPoE PADO 08:00:27:c8:4a:32 => 08:00:27:fa:3e:50 sid=0000 <AC-Name vyos-ac> <Service-Name > <AC-Cookie ca898c164463d5ae46b694ff9e09c27d61efcc897802c91b> <Host-Uniq 390c0000>]
Nov 28 20:09:18 rc9 accel-pppoe: eth1: recv [PPPoE PADR 08:00:27:fa:3e:50 => 08:00:27:c8:4a:32 sid=0000 <Service-Name > <Host-Uniq 390c0000> <AC-Cookie ca898c164463d5ae46b694ff9e09c27d61efcc897802c91b>]
Nov 28 20:09:18 rc9 accel-pppoe: eth1: send [PPPoE PADS 08:00:27:c8:4a:32 => 08:00:27:fa:3e:50 sid=0001 <AC-Name vyos-ac> <Service-Name > <Host-Uniq 390c0000>]
Nov 28 20:09:18 rc9 accel-pppoe: eth1:: send [LCP ConfReq id=1 <auth PAP> <mru 1492> <magic 6b8b4567>]
Nov 28 20:09:18 rc9 accel-pppoe: eth1:: recv [LCP ConfReq id=1 <mru 1492> <magic 5624ae46>]
Nov 28 20:09:18 rc9 accel-pppoe: eth1:: send [LCP ConfAck id=1 ]
Nov 28 20:09:21 rc9 accel-pppoe: eth1:: send [LCP ConfReq id=1 <auth PAP> <mru 1492> <magic 6b8b4567>]
Nov 28 20:09:21 rc9 accel-pppoe: eth1:: recv [LCP ConfAck id=1 <auth PAP> <mru 1492> <magic 6b8b4567>]
Nov 28 20:09:21 rc9 accel-pppoe: eth1:: recv [PAP AuthReq id=1]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: connect: ppp0 <--> pppoe(08:00:27:fa:3e:50)
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: send [PAP AuthAck id=1 "Authentication succeeded"]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: send [CCP ConfReq id=1 <mppe +H -M +S -L -D -C>]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: test: authentication succeeded
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: recv [IPCP ConfReq id=1 <addr 0.0.0.0> <dns1 0.0.0.0> <dns2 0.0.0.0>]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: send [IPCP ConfReq id=1 <addr 179.109.80.55>]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: send [IPCP ConfNak id=1 <addr 100.64.0.1> <dns1 179.109.80.19> <dns2 179.109.80.20>]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: recv [CCP ConfReq id=1]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: send [CCP ConfAck id=1]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: recv [CCP ConfRej id=1]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: send [CCP ConfReq id=2]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: recv [IPCP ConfAck id=1 <addr 179.109.80.55>]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: recv [IPCP ConfReq id=2 <addr 100.64.0.1> <dns1 179.109.80.19> <dns2 179.109.80.20>]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: send [IPCP TermAck id=2]
Nov 28 20:09:21 rc9 accel-pppoe: ppp0:test: recv [CCP ConfAck id=2]
Nov 28 20:09:24 rc9 accel-pppoe: ppp0:test: recv [IPCP ConfReq id=2 <addr 100.64.0.1> <dns1 179.109.80.19> <dns2 179.109.80.20>]
Nov 28 20:09:24 rc9 accel-pppoe: ppp0:test: send [IPCP ConfAck id=2]

Tested functionality, no issues found:

Your client (00:0c:42:bd:02:05) disconnects.
PADT = Active Discovery Termination
Nov 27 18:16:43 vyos accel-pppoe: eth1: recv [PPPoE PADT 00:0c:42:bd:02:05 => 68:05:ca:01:6d:9d sid=1f80]

@kroy can you please use the rolling release. I checked the module does work in rolling.

I was thinking about swatting. Draws the most attention. (We(s)tcoast Canada)

@Line2 He will be in bed right now. It's 11pm in Germany.

Well not really, the ones who rebuilt the new kernel didn't know about those. I'm working on IPoE integration (similar like a PPPoE server but without the PPP =), They won't do anything.

Hmm, ok I gotta check on that.

Hmm. looks strange. 4.19.0-amd64-vyos isn't required as you are running on 4.19.4-amd64-vyos. Can you load the module manually? (sudo modprobe wireguard).

Please download http://dev.packages.vyos.net/repositories/current/vyos/pool/main/w/wireguard/wireguard-modules_0.0.20181018-1_amd64.deb and install via 'dpkg -i <pkg name>'.

Kernel module hasn't been rebuilt on our side. The current package will put that under /lib/modules/4.19.0-amd64-vyos/extra/ and your kernel is 4.19.4 and won't find it. I have a look into the package right now.

Can you please send me the output of 'uname -a'. Thx.

It seems that local auth is impossible, all I found is to configure it against radius, user should check abills as billing system. (https://sourceforge.net/projects/abills/)
If anyone knows how to use local authentication like chap or pap or anything, let me know please. Otherwise IPoE seems a real nice option, not as robust as ppp, but quite nice.

@dongjunbo Perfect. So it looks like that you have a valid ppp session established (session id 0x5d58). Does 'sudo ip sh a' show you a ppp0 interface or something similar? I tested the ppp client shipped in rc7 and rc8 and it appears it works as expected, so we need to find out what's going wrong on your side.

@patrickbrandao Your input is required.

@dongjunbo Your input is required.

https://vyos.readthedocs.io/en/latest/services.html#pppoe-server

run sh ip route

For the ones who want to follow or having an early glimpse: https://github.com/hagbard-01/vyos-1x/tree/IPoE

Will be in the next rolling release.
https://github.com/vyos/vyos-world/commit/fb3c399ffad359ec11660e723fb72b9864710029

CI integration pending.

@patrickbrandao Can you please let me know how I can reproduce your issue?

note to myself:

• implement verify for auth mode so that either local or radius is set. :done:

I tested everything, pppoe client is working correctly. @dongjunbo Can you please do the following:

I tested all is fine. So it must be something else. I found an issue in the pppoe-server code which was supposed to be released, but weren't. (local auth isn't working, rolling release has the latest code already in).
Other than that, the ppp client in rc8 is just fine, I created a pppoe server (vyos rc8) and used another vyos box (rc8) as client, no issues at all.

@dongjunbo , @syncer
The ppp client hasn't been removed, the old pppoe-server packages was a bunch of scripts utilizing rp-pppoe. I have a look into rc8, the rolling images have the client on board (ipsec l2tp would otherwise fail as well).
I'm gonna test a fresh install and have a look into your config.

I can't reproduce it @patrickbrandao. can you please detail out of what you did?

I'm going to keep this task still open till the end of the week to catch eventual bugs.

@sokrates No problem at all, whenever you have time.

@sokrates Can you please test with the latest rolling release?

In case someone else finds it helpful:
http://telecomsite.ru/upload/news/using_pppoe_and_ipoe.pdf
Gonna start shortly with IPoE implementation.

https://github.com/vyos/vyatta-netflow/commit/3562ed47b5f897d09ba01c5d2cdc3bfbb1ee253b

Ahh crap. I'll fix that right away.

https://github.com/vyos/vyatta-netflow/commit/07abd7362b12a8a3c988d223113f6ec7c082638f

bug confirmed in 1.2.0-rolling+201811150337.

Hmm, it works for me flawlessly. Can you try https://downloads.vyos.io/testing/1.2.0-rc7/vyos-1.2.0-rc7-amd64.iso please?

For everyone who wants to test, this version is in rolling releases. If you find any bugs, please post it here.
https://downloads.vyos.io/?dir=rolling/current/amd64

What are the parameters you connect on rs232? Have you tried to switch to 115200 baud after grub started?

feature release for rc8: https://github.com/vyos/vyos-1x/commit/93c9199589cca87321f1f0577d16099dbe78842b

sh version
Version: VyOS 1.2.0-rc6
Built by: maintainers@vyos.net
Built on: Tue 06 Nov 2018 01:28 UTC
Build ID: c5283369-3c07-4539-97fb-76e701e97a77

What's the problem @sokrates ?

Options added. Maybe I should make a node for dns and have then all dns settings in there for better visibility.
set service pppoe-server dnsv6-servers
Possible completions:

server-1     Primary DNS server
server-2     Secondary DNS server
server-3     Tertiary DNS server

IPv6 pppoe options added.

feature below added: