In T2505#64889, @c-po wrote:

There is no newer kernel then 4.19.124 on the 4.19x train. Newer Kernels do not work as the out-of-tree Intel drivers for the NICs and QAT won‘t compile for Kernel >5.3 and that is bot an LTS one.

Cool, thanks for pointing this out; I will take T2501, and will probably rename for clarity.

There is no newer kernel then 4.19.124 on the 4.19x train. Newer Kernels do not work as the out-of-tree Intel drivers for the NICs and QAT won‘t compile for Kernel >5.3 and that is bot an LTS one.

Welcome - need to make a prefix-hint CLI node for the future

https://phabricator.vyos.net/T935 Here’s the same thing happening in the past. I think it was resolved by doing kernel updates? Can someone do a kernel update in the rolling build?

@jestabro thanks for that tip, vyos-config-debug helped me track down the failing code. At least I can continue working until T2501 is fixed.

@jjakob, yes I see the issue there; but firstly, did you try debugging with boot parameter 'vyos-config-debug' ? cf.

Yup, sorry. Just figured that out too after reading https://blog.kylemanna.com/ipv6/using-native-ipv6-via-comcast-in-san-francisco/.

@jjakob yes, thanks for pointing this out ...

No, its just an ID. Please read my comments above and inser the prefix ::/60 infinity; line and reboot

Appreciate it. Sorry, I had assumed VyOS was using dhclient, not DHCP6c.

You only receive a /64 prefix, try adjusting the template then change sla-len to 4

In T421#64836, @c-po wrote:

sla-len should be 12 in your case then.

If that does not work, it could be that you need to hint comcast you want to have a /60 PD, by addin prefix ::/60 infinity; here into line 26

https://github.com/vyos/vyos-1x/blob/current/data/templates/dhcp-client/ipv6.tmpl#L26

or on the router itself you find the file here: /usr/share/vyos/templates/dhcp-client/ipv6.tmpl

@jestabro I think T2501 is related to this - can you take a look?

Thanks, @fetzerms !

sla-len should be 12 in your case then.

In T421#63911, @c-po wrote:

From the Git commit:

commit faa85accc99d6ff777f12f5dd9e43a6dd8f7e7a2 (origin/ipv6-pd)
Author: Christian Poessinger <[email protected]>
Date:   Sun May 17 20:15:45 2020 +0200

    pppoe: dhcpv6-pd: T421: initial support

    The following configuration will assign a /64 prefix out of a /56 delegation
    to eth0. The IPv6 address assigned to eth0 will be <prefix>::ffff/64.
    If you do not know the prefix size delegated to you, start with sla-len 0.

      pppoe pppoe0 {
          authentication {
              password vyos
              user vyos
          }
          description sadfas
          dhcpv6-options {
              delegate eth0 {
                  interface-id 65535
                  sla-id 0
                  sla-len 8
              }
          }
          ipv6 {
              address {
                  autoconf
              }
              enable
          }
          source-interface eth1
      }

      vyos@vyos:~$ show interfaces
      Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
      Interface        IP Address                        S/L  Description
      ---------        ----------                        ---  -----------
      eth0             2001:db8:8003:400::ffff/64        u/u

This is a proof of concept. What is not working?

• IPv6 address is not removed from delegated interface
• router-advertisements? Not tested yet!

In T2457#63617, @jjakob wrote:

Why not just use the OS's ping command? It does address resolution. Resolving a IP address as hostname would leak the IP via DNS as well.

That patch is invalid as ping.py does not exist under vyos-1x package, its in vyatta-op.

@c-po I suspect that the problem has been found, but after I executed the restart PPPoE command, the default travel was lost. My configuration name wrote the following static route:

interface-route 0.0.0.0/0 {

next-hop-interface pppoe0 {
}

}
interface-route6 ::/0 {

next-hop-interface pppoe0 {
}

}
table 150 {

interface-route 0.0.0.0/0 {
    next-hop-interface pppoe0 {
    }
}
interface-route6 ::/0 {
    next-hop-interface pppoe0 {
    }
}

}

But it disappeared after disconnect interface pppoe0.

Just thought I'd say that this implementation has worked for my DHCPv6-PD enabled ISP in Australia :)

@jestabro Sorry for the delay, I did not find a proper maintenance window... Today I verified the fix and it seems to work. My automation scripts run through just fine, without the error.

https://github.com/vyos/vyos-1x/pull/422/files

low-brow caching:

A friend also thought about set service nettty for network tty (which it is infact)

Maybe set service serial-bridge?

Who can write a python handler?
XML is ready.

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

It causes this:

9140 ?        Ss     0:00 /bin/bash /usr/libexec/vyos/init/vyos-router start
 9427 ?        S      0:00  \_ /bin/bash /usr/libexec/vyos/init/vyos-router start
 9428 ?        S      0:00      \_ python3 /usr/libexec/vyos/vyos-boot-config-loader.py /opt/vyatta/etc/config/config.boot
 9451 ?        S      0:00          \_ /opt/vyatta/sbin/my_commit
 9522 ?        S      0:00              \_ sudo sh -c VYOS_TAGNODE_VALUE='eth0' /usr/libexec/vyos/conf_mode/interfaces-ethernet.py
 9523 ?        Sl     0:00                  \_ python3 /usr/libexec/vyos/conf_mode/interfaces-ethernet.py
 9531 ?        R      0:00                      \_ /bin/cli-shell-api --show-active-only --show-show-defaults --show-ignore-edit showConfig