1. Vyos Router <-> Switch <-> Multiple Computers

I am having this exact problem and it evidently has been a problem for quite a few years.

I've been running TAYGA inside VyOS with absolutely no problems for the last several years.

I downloaded

After doing some research, it appears this is a known bug in PowerDNS Recursor 4.7 (amazing to me).

Confirmed working on "current" branch.

Is anyone else seeing this same problem? It is keeping me from being able to use VyOS in an IPv6-only environment.

OK, I just noticed the merge to "current" branch.

I'd be glad to help test it, but I checked the repos and didn't see where it got merged in?

Confirmed that issue is resolved.

Or probably better:

Oh, if you are asking for an example of what the VyOS config setting would look like?

I've been manually adding TAYGA to VyOS (See T160) for my NAT64 capability.

Sorry for the noise.

No, I saw no other errors that looked related to the DHCPv6 WAN client.

adminuser@vyos:~$ show interfaces ethernet eth2
eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

link/ether 52:54:00:bf:64:0b brd ff:ff:ff:ff:ff:ff
inet XX.XXX.XXX.210/28 brd 98.187.179.223 scope global eth2
   valid_lft forever preferred_lft forever
inet XX.XXX.XXX.212/28 brd 98.187.179.223 scope global secondary eth2
   valid_lft forever preferred_lft forever
inet XX.XXX.XXX.213/28 brd 98.187.179.223 scope global secondary eth2
   valid_lft forever preferred_lft forever
inet XX.XXX.XXX.217/28 brd 98.187.179.223 scope global secondary eth2
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:febf:640b/64 scope link 
   valid_lft forever preferred_lft forever
Description: WAN Network Interface

I was hoping to get that as well (and have in the past). What could be causing the problem?

OK, I now tried vyos-1.3-rolling-202012192139 and am happy to report that something since the previous version I tried and this version has now fixed the problem.

Problem confirmed fixed as of 2020-07-24.

@elianora Email me at [email protected]

Also on delete:

Here is the iptables-save output for Vyos-1.3-rolling-202006260117:

Is this related to T2619? It sure looks like it to me.

EDIT: EDITED from original for clarity

I can confirm that your change as of VyOS 1.3-rolling-202006200117 fixed the problem.

I will do that tonight.

Version: VyOS 1.2.5+
Release Train: crux

T2551 has now been fixed and confirmed working.

@c-po I can now confirm that as of vyos-1.3-rolling-20200607117 this issue is now fixed!

@c-po Woops, as of vyos-1.3-rolling-202006052325 now the problem has switched.

@richardpowellus Yes, your work around fixed my problem and I'm now for the first time able to receive a /56 from my ISP and divvy it up between my interfaces.

@richardpowellus Yes, your work around fixed my problem and I'm now for the first time able to receive a /56 from my ISP and divvy it up between my interfaces.

In T421 @richardpowellus mentioned:

@richardpowellus I've noted the exact same issue in T2551.

Yes, I've been seeing those messages.

@jack9603301 As I already stated in the first comment in T2510 and in T421, this is not configuring DHCPv6-PD.

@jack9603301 As stated a couple of times above, please see T2510 for my configuration.

@gadams Thanks for your reply.

Is this new DHCPv6-PD feature supposed to be working on Ethernet interfaces?

I tried out DHCPv6-PD but so far no luck (but for a separate reason).

I'm would like to try out the new VyOS 1.3 DHCPv6-PD feature.

From comments, it looks like this feature is now available?

Does this mean it can now listen on "outer" transport IPv6 addresses now that it is using 2.4.0 (even if it is just a special "option" and not yet in the VyOS CLI)?

A user on the forum informed me that a temporary work around that gets one step closer with the current code base is:

I just wanted to mention that the two problems I mentioned earlier had nothing to do with this issue.

Wiki instructions for system package settings now seem to be gone.

@suto.norbert I don't recall ever seeing any error about duplex or speed when setting vyos pre 1.2.0 versions.
Hope that helps.

I am having a few strange problems with 2-3 production pre vyos-1.2.0 systems as well.

I tested with VyOS 999.201803020337.

The last nine months or so I've been running Tayga on VyOS Beta 1.2 (latest versions) in my production network.

I'm attempting to go all IPv6 internally so this would be nice to have if it doesn't currently work.

"unbound" is also another good recursor.

I tested with vyos.999.201802100337 and the original problem is solved.....However....

Sorry, I just now came across this fixed issue by random chance.

IPv6 firewall works fine on VyOS 1.1.X and 1.2.X, it is just that you can't use the GROUPS on IPv6 like you can on IPv4.

Latest version of OpenVPN is 2.4.4 and has multiple new features.

I checked on 2017-09-04 and I am not able to put in IPv6 address into the OpenVPN interfaces.

Agreed. I just re-tried it as of 2017-09-05 and it now saves the OpenVPN configuration file in the /config/config.boot file.

I've been running Tayga on a debian box for the last year or so and have not noticed any performance problems, but I haven't compared Tayga with Jool.

I've just tested TAYGA installed on VyoS 1.2 (Beta) and it seems to work fine even though there is no configuration for it in VyOS.

Added information to WIKI.

Oh, OK, great! I didn't know that.

I was able to boot the 1.2 BETA with no problem. Is it stable enough to use?

I just tried to boot VyOS 1.1.7 64-bit from PCENGINES APU2C4 and got the exact same error message when installing from a USB key.