Page MenuHomePhabricator

hagbard (burkhard)
User

Projects

User Details

User Since
May 25 2018, 2:31 AM (28 w, 4 d)

Recent Activity

Today

hagbard changed the status of T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses from Needs testing to Blocked.

pending ci integration

Tue, Dec 11, 6:22 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Yesterday

hagbard added a comment to T1087: Firewall on Wireguard Interface.

I've tested that I can utilize the existing firewall functions/scripts which work, so I need to write a wrapper for it, but that will solve the issue. Shouldn't take too long.

Mon, Dec 10, 11:45 PM · VyOS 1.2.x
hagbard changed the status of T1087: Firewall on Wireguard Interface from Open to In progress.
Mon, Dec 10, 11:18 PM · VyOS 1.2.x
hagbard triaged T1087: Firewall on Wireguard Interface as Normal priority.
Mon, Dec 10, 10:39 PM · VyOS 1.2.x
hagbard added a comment to T1065: PPPoE MTU on boot up.

can you please do the following and post the result:

Mon, Dec 10, 9:45 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1065: PPPoE MTU on boot up.

All right. First of all MTU != MRU. (MTU - 8 byte IP header = MRU). I used your config example and I see a difference. The conf request has to come from your side, that happens durig the discovery pahase (PADI). I see that it is not being sent before you reconnect.

Mon, Dec 10, 6:20 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Fri, Dec 7

hagbard updated subscribers of T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses.

I don't think That I use netplugd for now. I have just a check in the script how an address had been setup on the system, if it's been dhcp then I send a release (suspend doesn't do that) and a new dhcp request. I have to chat with @c-po about T894 first.
If netplugd is being introduced to the OS, I can simply remove an else clause.

Fri, Dec 7, 7:20 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses.

I will add the dhcp functionality too. The problem is that the network config is very different from the approach within the OS and additional software is written the way to work with whatever has the OS, it doesn't know about vyos and it's cli etc.
Thanks for testing, I will integrate the dhcp functionality asap and see that I can quickly get it into the rolling branch.

Fri, Dec 7, 6:14 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1026: Removing tunnel deletes all tunnels?.

Bug confirmed, I can reproduce it. I can't tell you how long it takes to fix it, it's all old code base.

Fri, Dec 7, 12:18 AM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses from Open to Needs testing.
Fri, Dec 7, 12:08 AM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses.

Hey @yun, could you test it under vmware, I just used the scripts to trigger resume and suspend.

Fri, Dec 7, 12:05 AM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Thu, Dec 6

hagbard claimed T1087: Firewall on Wireguard Interface.
Thu, Dec 6, 10:08 PM · VyOS 1.2.x
hagbard added a comment to T1026: Removing tunnel deletes all tunnels?.

Could you please do it via: 'show config command'. thx.

Thu, Dec 6, 9:19 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses.

Ok, so I think I know how to attack that. either we use the tools then from debian directly and add an extra package with the user scripts, ot we do it directly in the tools package which is forked anyway. I would personally lean torwards option 2, since debian would take care of patching.

Thu, Dec 6, 9:17 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1026: Removing tunnel deletes all tunnels?.

@Barrysdca Can you please share your config? At least the tunnel parts.

Thu, Dec 6, 8:56 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T834: accel-ppp: l2tp implementation, a subtask of T833: accel-ppp: pptp implementation, from In progress to On hold.
Thu, Dec 6, 7:17 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T834: accel-ppp: l2tp implementation from In progress to On hold.
Thu, Dec 6, 7:17 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T989: accel-ppp: IPoE implementation from In progress to On hold.
Thu, Dec 6, 7:16 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T989: accel-ppp: IPoE implementation, a subtask of T742: Implement accel-ppp in VyOS, from In progress to On hold.
Thu, Dec 6, 7:16 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T1048: [IPSec] Protocol all does not work in IPSec Tunnel from In progress to Needs testing.
Thu, Dec 6, 7:14 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1048: [IPSec] Protocol all does not work in IPSec Tunnel.

you can test it in the rolling release of Dec 7th. or manually install http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-vpn/vyatta-cfg-vpn_0.12.105+vyos2+current4_all.deb. Please let me know if it works like expected.

Thu, Dec 6, 7:14 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Wed, Dec 5

hagbard added a comment to T1075: Unable to build the ISO for VyOS 1.2.0.

So, I can reproduce the missing initrd issue now as well, but I have no idea why it happens. It doesn't happen in ci, so I assume some local pacakge or command is missing. I did chroot into the chroot before squashfs is being packed and did a live-update-initramfs, which worked with no issues. So a missing driver can be ruled out here.
but I get then an issued that the arch isn't supported :D.

Wed, Dec 5, 10:39 PM · VyOS 1.2.x
hagbard added a comment to T1075: Unable to build the ISO for VyOS 1.2.0.

That looks liek a similar f'up. The correct ddclient version is 3.8.2+vyos2+current1, no idea where lithium6 comes from. The correct pkg is within the repo: http://dev.packages.vyos.net/repositories/current/vyos/pool/main/d/ddclient/ddclient_3.8.2+vyos2+current1_all.deb and the current vyatta-cfg-system has no dependency to vyatta-dhcp3-client (https://github.com/vyos/vyatta-cfg-system/blob/current/debian/control).

Wed, Dec 5, 6:18 PM · VyOS 1.2.x
hagbard added a comment to T1075: Unable to build the ISO for VyOS 1.2.0.

I see, I have a look.

Wed, Dec 5, 5:50 PM · VyOS 1.2.x
hagbard added a comment to T1065: PPPoE MTU on boot up.

Can you record the PADI requests when the router reboots? It's plain text anyway, important question is if it sends "PPP-Max-Payload 1500", which it does in all my tests. I was only able to reproduce your issue when the sends a max mtu 1492 or even lower, then the client (depending on mru) negotiates the highest possible mtu and sets it on the pppoe interface. But it's also possible that my tests are different from what you see. I used accel-ppp to use as pppoe server.

Wed, Dec 5, 5:49 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1075: Unable to build the ISO for VyOS 1.2.0.

@kroy please make sure that you do it from a clean build tree. I run it now locally from home and everything is working well. You can also do a ./configure --debug && make iso, which is more verbose.

Wed, Dec 5, 2:49 AM · VyOS 1.2.x
hagbard updated subscribers of T1075: Unable to build the ISO for VyOS 1.2.0.

@kroy or @runar
Can please one of you test if the build outside ci is working again too? Shouldn't make any difference, but before I close this bug I'd like to have confirmation (and happy faces) from one of you as well.

Wed, Dec 5, 12:01 AM · VyOS 1.2.x

Tue, Dec 4

hagbard changed the status of T1075: Unable to build the ISO for VyOS 1.2.0 from Open to In progress.
Tue, Dec 4, 11:54 PM · VyOS 1.2.x
hagbard claimed T1075: Unable to build the ISO for VyOS 1.2.0.

I rebuilt the package (vyatta-cfg-quagga) which removed the old one from the repo and re-published the correct version. I tested with apt that the correct packages is being queried/installed. Looks all good now from my point of view.

Tue, Dec 4, 11:35 PM · VyOS 1.2.x
hagbard added a comment to T1075: Unable to build the ISO for VyOS 1.2.0.

http://dev.packages.vyos.net/repositories/current/vyos/dists/unstable/main/binary-amd64/Packages contains the wrong package.
faulty one: http://dev.packages.vyos.net/repositories/current/vyos/pool/main/v/vyatta-cfg-quagga/vyatta-cfg-quagga_0.18.172_amd64.deb

Tue, Dec 4, 9:10 PM · VyOS 1.2.x
hagbard added a comment to T1063: Wireguard: Unable to add wireguard interface to a routing protocol (eg. ospf) .

@runar How do you set it on other interfaces?

Tue, Dec 4, 7:06 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1065: PPPoE MTU on boot up.

@SteveP Can you please test if the pppoe server supports a mtu of 1500? In my tests an mtu of 1500 is requested by the client, I just send from the server back 1492 which is then used on the interface.

Tue, Dec 4, 6:43 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Mon, Dec 3

hagbard added a comment to T1065: PPPoE MTU on boot up.

<<<<<<< HEAD

#define RCSID "$Id: tty.c,v 1.25 2006/06/04 07:04:57 paulus Exp $"

#define RCSID "$Id: tty.c,v 1.27 2008/07/01 12:27:56 paulus Exp $"

ppp-2.4.7

Mon, Dec 3, 9:06 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1065: PPPoE MTU on boot up.

It's actually a ppp bug, it simply ignores mtu when setup in the peers config. I'm about to update pppd, since a new version from backports is working however it creates instead of pppoe interfaces a ppp interface, which may break something else.
Maybe its now the time to rewrite the pppoe client from scratch.

Mon, Dec 3, 9:04 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1065: PPPoE MTU on boot up.

Bug confirmed, but not easy to fix.

Mon, Dec 3, 6:49 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T1065: PPPoE MTU on boot up from Open to In progress.
Mon, Dec 3, 5:03 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1028: Suspending and resuming VyOS in VMware will result in loss of static ip addresses.

The vmware tools scripts work as expected, they are stopping and starting the network config as they are supposed to do, but are using debian defaults. So they are not executing the config. I'm going to check of we can extend it a little somewhere to execute the config again when 'resume' happens. In general that won't be an easy fix.

Mon, Dec 3, 5:00 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Sat, Dec 1

hagbard added a comment to T1063: Wireguard: Unable to add wireguard interface to a routing protocol (eg. ospf) .

Implementation doesn't take long, testing it will take a little.

Sat, Dec 1, 6:13 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard closed T1071: Squid log directory missing as Invalid.

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

Sat, Dec 1, 4:46 PM · Rejected

Fri, Nov 30

hagbard closed T1061: Wireguard: Missing option to administrativly shutdown interface as Resolved.

https://github.com/vyos/vyos-1x/commit/a29898b2ea15b7d9cea7fade1b27d38967c52d52, will be available with the next latest rolling.

Fri, Nov 30, 6:32 PM · VyOS-1.2.0-LTS, VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard changed the status of T1061: Wireguard: Missing option to administrativly shutdown interface from Open to In progress.
Fri, Nov 30, 4:55 PM · VyOS-1.2.0-LTS, VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard claimed T1061: Wireguard: Missing option to administrativly shutdown interface.
Fri, Nov 30, 4:28 PM · VyOS-1.2.0-LTS, VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard added a comment to T742: Implement accel-ppp in VyOS.

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.

Fri, Nov 30, 4:27 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T742: Implement accel-ppp in VyOS.

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.

Fri, Nov 30, 4:11 AM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard assigned T1055: Duplicate Address Detection happens on interfaces other than eth0, too to dmbaturin.
Fri, Nov 30, 12:16 AM · VyOS 1.3.x

Thu, Nov 29

hagbard added a comment to T1048: [IPSec] Protocol all does not work in IPSec Tunnel.

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]) .

Thu, Nov 29, 11:50 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T1048: [IPSec] Protocol all does not work in IPSec Tunnel from Open to In progress.
Thu, Nov 29, 10:53 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1053: Error when re-configuring an interface from DHCP to static IP.

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.

Thu, Nov 29, 10:41 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard closed T1053: Error when re-configuring an interface from DHCP to static IP as Resolved.
Thu, Nov 29, 10:37 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard added a comment to T1053: Error when re-configuring an interface from DHCP to static IP.

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.

Thu, Nov 29, 9:11 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard changed the status of T1053: Error when re-configuring an interface from DHCP to static IP from Open to In progress.
Thu, Nov 29, 8:36 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard lowered the priority of T1040: rc.local is executed too early from Normal to Low.
Thu, Nov 29, 8:25 PM · VyOS 1.3.x
hagbard added a comment to T1057: PPPoE Server not working.

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.

Thu, Nov 29, 8:23 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard added a comment to T742: Implement accel-ppp in VyOS.

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

Thu, Nov 29, 7:56 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard moved T1040: rc.local is executed too early from Need Triage to Backlog on the VyOS 1.2.x board.
Thu, Nov 29, 12:12 AM · VyOS 1.3.x
hagbard triaged T1040: rc.local is executed too early as Normal priority.
Thu, Nov 29, 12:10 AM · VyOS 1.3.x
hagbard claimed T1040: rc.local is executed too early.

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.

Thu, Nov 29, 12:09 AM · VyOS 1.3.x

Wed, Nov 28

hagbard closed T1054: Webproxy commit failed: Can't touch /var/log/squid/blacklist.log: No such file or directory as Resolved.

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.

Wed, Nov 28, 11:31 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard claimed T1054: Webproxy commit failed: Can't touch /var/log/squid/blacklist.log: No such file or directory.
Wed, Nov 28, 9:36 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard closed T1031: Upgraded vyos1.2rc7 to vyos1.2rc8, interface is down and pppoe is not working. as Resolved.

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.

Wed, Nov 28, 8:26 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard closed T1049: 1.2.0-rc9 Wireguard config disappears as Resolved.
Wed, Nov 28, 8:24 PM · VyOS 1.2.x
hagbard added a comment to T1057: PPPoE Server not working.

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]

Wed, Nov 28, 8:11 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard closed T1057: PPPoE Server not working as Invalid.

Tested functionality, no issues found:

Wed, Nov 28, 6:14 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard claimed T1057: PPPoE Server not working.

Your client (68:05:ca:01:6d:9d ) 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]

Wed, Nov 28, 4:22 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)

Tue, Nov 27

hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

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

Tue, Nov 27, 12:02 AM · VyOS 1.2.x

Mon, Nov 26

hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

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

Mon, Nov 26, 10:09 PM · VyOS 1.2.x
hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

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

Mon, Nov 26, 10:01 PM · VyOS 1.2.x
hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

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.

Mon, Nov 26, 9:57 PM · VyOS 1.2.x
hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

Hmm, ok I gotta check on that.

Mon, Nov 26, 9:53 PM · VyOS 1.2.x
hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

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

Mon, Nov 26, 9:50 PM · VyOS 1.2.x
hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

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>'.

Mon, Nov 26, 9:42 PM · VyOS 1.2.x
hagbard added a comment to T1049: 1.2.0-rc9 Wireguard config disappears.

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.

Mon, Nov 26, 9:40 PM · VyOS 1.2.x
hagbard claimed T1049: 1.2.0-rc9 Wireguard config disappears.

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

Mon, Nov 26, 9:32 PM · VyOS 1.2.x
hagbard added a comment to T989: accel-ppp: IPoE implementation.

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.

Mon, Nov 26, 6:41 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Sat, Nov 24

hagbard added a comment to T1031: Upgraded vyos1.2rc7 to vyos1.2rc8, interface is down and pppoe is not working..

@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.

Sat, Nov 24, 4:25 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)

Fri, Nov 23

hagbard added a comment to T1029: vyos 1.2rc8 snmp set error.

@patrickbrandao Your input is required.

Fri, Nov 23, 11:16 PM · Invalid
hagbard added a comment to T1031: Upgraded vyos1.2rc7 to vyos1.2rc8, interface is down and pppoe is not working..

@dongjunbo Your input is needed.

Fri, Nov 23, 11:02 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard closed T835: accel-ppp: pppoe implementation as Resolved.
Fri, Nov 23, 11:01 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard closed T835: accel-ppp: pppoe implementation, a subtask of T742: Implement accel-ppp in VyOS, as Resolved.
Fri, Nov 23, 11:01 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard closed T1038: Write documentation for setting up a pppoe server as Resolved.

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

Fri, Nov 23, 11:01 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard closed T1038: Write documentation for setting up a pppoe server, a subtask of T835: accel-ppp: pppoe implementation, as Resolved.
Fri, Nov 23, 11:01 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard changed the status of T1038: Write documentation for setting up a pppoe server from Open to In progress.
Fri, Nov 23, 9:10 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard changed the status of T1038: Write documentation for setting up a pppoe server, a subtask of T835: accel-ppp: pppoe implementation, from Open to In progress.
Fri, Nov 23, 9:10 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard triaged T1038: Write documentation for setting up a pppoe server as Normal priority.
Fri, Nov 23, 9:00 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard added a comment to T1037: BGP exchanged prefixes are shown as incative.

run sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,

O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP,
F - PBR, f - OpenFabric,
> - selected route, * - FIB route
Fri, Nov 23, 7:52 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard created T1037: BGP exchanged prefixes are shown as incative.
Fri, Nov 23, 7:47 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)

Thu, Nov 22

hagbard added a comment to T989: accel-ppp: IPoE implementation.

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

Thu, Nov 22, 8:52 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard closed T957: Add xenserver tools as Resolved.

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

Thu, Nov 22, 8:22 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard added a comment to T957: Add xenserver tools.

CI integration pending.

Thu, Nov 22, 7:04 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)
hagbard added a comment to T1029: vyos 1.2rc8 snmp set error.

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

Thu, Nov 22, 7:03 PM · Invalid
hagbard added a comment to T835: accel-ppp: pppoe implementation.

note to myself:

  • implement verify for mode so that either local or radius is set.
Thu, Nov 22, 4:25 PM · VyOS 1.2.x (VyOS 1.2.0-rc9)

Wed, Nov 21

hagbard added a comment to T1031: Upgraded vyos1.2rc7 to vyos1.2rc8, interface is down and pppoe is not working..

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

Wed, Nov 21, 6:42 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard added a comment to T1031: Upgraded vyos1.2rc7 to vyos1.2rc8, interface is down and pppoe is not working..
Wed, Nov 21, 4:22 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard added a comment to T1031: Upgraded vyos1.2rc7 to vyos1.2rc8, interface is down and pppoe is not working..

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.

Wed, Nov 21, 4:18 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)
hagbard added a comment to T1031: Upgraded vyos1.2rc7 to vyos1.2rc8, interface is down and pppoe is not working..

@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.

Wed, Nov 21, 3:39 PM · VyOS 1.2.x (VyOS 1.2.0-rc10)

Tue, Nov 20

hagbard changed the status of T834: accel-ppp: l2tp implementation, a subtask of T833: accel-ppp: pptp implementation, from Open to In progress.
Tue, Nov 20, 11:49 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard changed the status of T834: accel-ppp: l2tp implementation from Open to In progress.
Tue, Nov 20, 11:49 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)
hagbard added a comment to T1029: vyos 1.2rc8 snmp set error.

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

Tue, Nov 20, 10:11 PM · Invalid
hagbard changed the status of T1029: vyos 1.2rc8 snmp set error from Open to In progress.
Tue, Nov 20, 9:15 PM · Invalid
hagbard added a comment to T742: Implement accel-ppp in VyOS.

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

Tue, Nov 20, 5:57 PM · VyOS 1.2.x ( VyOS 1.2.0-rc11)