as soon as I did
set interfaces ethernet eth3 pppoe 0 enable-ipv6 set interfaces ethernet eth3 pppoe 0 ipv6 address autoconf
as soon as I did
set interfaces ethernet eth3 pppoe 0 enable-ipv6 set interfaces ethernet eth3 pppoe 0 ipv6 address autoconf
Is it really required to only update the QLogic part? I ather propose that we drop all firmware-* packages and include the "real" matching firmware packages from git.kernel.org
I‘m on Telekom FTTH (Germany) and could test an ISO, too.
Why not use a combination of two?
No further complaints - seems to be resolved.
okay - then I kindly close this one.
cpo@LR1:~$ netstat -an | grep 69 udp 0 0 172.18.201.10:69 0.0.0.0:* udp6 0 0 2001:db8::ffff:69 :::*
@thinkl33t any updates?
Root cause is the inability of tftpd to listen on multiple addresses.
Added the above snipped to vyos-1x and the latest rolling releases
Unfortunately this is not implemented in ntpqc. The reason it worked for me was my firewall blocking everything else.
As there is no recorded bug in this behavior on 1.2 we only would increase the risk on the LTS versions without legitimate benefit.
Please test with a rolling relase build date newer than 20120220 - Drivers have been replaced with the ones provided by Intel
Please test with a rolling relase build date newer than 20120220 - Drivers have been replaced with the ones provided by Intel
[ 227.874683] dca service started, version 1.12.1 [ 228.282193] ixgbe: loading out-of-tree module taints kernel. [ 228.288861] Intel(R) 10GbE PCI Express Linux Network Driver - version 5.5.3 [ 228.288863] Copyright(c) 1999 - 2018 Intel Corporation. [ 295.462589] e1000e: Intel(R) PRO/1000 Network Driver - 3.4.2.1-NAPI [ 295.462592] e1000e: Copyright(c) 1999 - 2018 Intel Corporation. [ 299.685648] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 2.7.29 [ 299.685651] i40e: Copyright(c) 2013 - 2018 Intel Corporation. [ 303.095404] i40evf: Intel(R) 40-10 Gigabit Virtual Function Network Driver - version 3.6.15 [ 303.095406] Copyright(c) 2013 - 2018 Intel Corporation. [ 306.534477] Intel(R) Gigabit Ethernet Linux Driver - version 5.3.5.22 [ 306.534480] Copyright(c) 2007 - 2018 Intel Corporation. [ 313.059333] ixgbevf: Intel(R) 10GbE PCI Express Virtual Function Driver - version 4.5.2 [ 313.059336] Copyright(c) 1999 - 2019 Intel Corporation.
We should NOT backport this to VyOS 1.2 crux
Yes, please migrate that function, too. One more migrated command.
/var/log/messages
can you edit /usr/libexec/vyos/system/on-dhcp-event.sh
@thinkl33t can you please also provide a "faulty" /etc/hosts file?
Latest rolling should autoload the module
br_netfilter should already be compuled as a module. Can you sudo modprobe br_netfilter? To see if it fits your purpose? If so we can autoload it on system bootup
This will be part of a bigger workpackage when the whole firewalling is rewritten. There is yet no ETA.
Your second command does kot specify any output interface whereas the first command speciefies tun0. Especially on ESXi you see almost no difference compared ro a vietual Box.
Maybe if hostname is empty, we can prepend the mac address to the fqdn which will be stored in /etc/hosts
Something seems to be totally off with set system domain-name and set system domain-search domain
Interface name is ppp0 but will later be renamed to pppoe0
cpo@BR1# set interfaces ethernet eth1 pppoe 0 ipv6 address autoconf
[edit]
cpo@BR1# commit
[ interfaces ethernet eth1 pppoe 0 ipv6 address autoconf ]
cp: cannot create regular file ‘/etc/ppp/ipv6-up.d/50-vyos-pppoe0-autoconf’: No such file or directory
sed: can't read /etc/ppp/ipv6-up.d/50-vyos-pppoe0-autoconf: No such file or dire ctory
chmod: cannot access ‘/etc/ppp/ipv6-up.d/50-vyos-pppoe0-autoconf’: No such file or directory
Warning: IPv6 forwarding is currently enabled.
IPv6 address auto-configuration will not be performed
unless IPv6 forwarding is disabled.@fromport how to reproduce? Is this possible with VMWare ESXi? If now, which virtualisation tool to use for testing?
Your given example can thus be enabled via set service dns forwarding domain microsoft.com server 127.0.0.1
Okay, a wildcard as in * does not work and is not supported by our underlying pdns-recursor.
@oliveriandrea can you please retest with latest rolling release if it already works?