Please test with a rolling relase build date newer than 20120220 - Drivers have been replaced with the ones provided by Intel
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 20 2019
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.
Feb 18 2019
/var/log/messages
can you edit /usr/libexec/vyos/system/on-dhcp-event.sh
Feb 17 2019
@thinkl33t can you please also provide a "faulty" /etc/hosts file?
Feb 16 2019
Feb 15 2019
Feb 13 2019
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.
Feb 12 2019
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
Feb 10 2019
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?
Implemented in latest rolling and backported to Crux branch for 1.2.1
An easier solution is to wrap the test in ' like use-web='this is your IP'
After some digging this is what I found out with VyOS 1.2.0-epa3:
Feb 9 2019
Feb 8 2019
Handled in/with T484, hopefully
Please retest with a new rolling release tomorrow
Patch does not apply cleanly, need to backport it but will do
Yes
Feb 5 2019
Feb 4 2019
So this problem still exists but I have no clue where to add it in our source @dmbaturin @UnicronNL
Feb 3 2019
Ah, there was a similar issue with dhcp last couple of weeks where quotes broke the config (T1129). Can you try using   instead of your whitespace?
Feb 2 2019
Con you provide a configuration to reproduce the issue?
I can confirm this. 1.2.0-EPA3 does not have thisbissue but 1.2.0 has it.
Jan 31 2019
Package needs to be build from source. There are already some packages which we build that way like libyang or librtr so not a big deal.
Jan 30 2019
Sounds more reasonable (enable than disable). Will this affect backwards compatibility or will there be a migrator?
Jan 29 2019
@danhusan is this your expected behavior?
can you share your DHCP configuration with us for reproducibility?
Jan 28 2019
IMHO this is a general CLI design issue.
Jan 23 2019
Nope, I used:
@hagbard I replaced vyos user with another one. Also image corporate setups where RADIUS is used for authing and there are no local users.
Jan 22 2019
There are no disadvantages in doing so. Any contribution is welcome.
Depending on the task which needs to be executed a script might need to be run as root.
Jan 12 2019
Jan 11 2019
lsmod output from 4.18.6-1 (all 4 NICs working) please. We already have a lsmod output of the other versions.
Please place your code snippets inside a Code section as mentioned above, this makes it easier to read.
Jan 10 2019
No reply from the vendor so far
Latest is fine
Jan 9 2019
No issue known but it eases reproducibility
@alexandrestein can you share your complete dns forwarding config node please?