https://github.com/vyos/vyatta-cfg-system/pull/79
I test it tomorrow after the CI rebuild before I close this task.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 15 2018
@syncer we have this patch in the kernel (commit 16032be56c1f66770da15cb94f0eb366c37aff6e ++). I think ethtool just doesn't use it, which is what I'm gonna check next.
@syncer gonna have a look today.
With less powerfull hardware (as this Atom D525) I'm fine with this change request.
Oct 14 2018
Here's what my dynamic dns config looks like:
I also experienced this problem with a custom ddclient config. Adding server= manually to my config fixed it.
The relevant Debian bug is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834928
From this report, the issue is in ifupdown and is supposedly fixed in 0.8.11. Unfortunately, this version is not available in Jessie without resorting to backports.
Can you provide your configuration, please?
Oct 13 2018
requires testing on the latest rolling
please retest on the latest rolling
requires testing on the latest rolling
@Tiberius please retest on the latest rolling
requires testing on the latest rolling
@hagbard want to investigate?
basically somewhere in interfaces scripts it tries to get
Speed: and Duplex: but virtio drivers just not report that
@c-po what we do with this ?
requires testing on the latest rolling
requires testing since w moved to frr
please retest
please retest on the latest rolling
@UnicronNL
please add htop, iotop and bmon
@rps what about 1.2 ?
@hagbard can you merge this please
must set interface route to single gw ip and use it after as default gateway
@Penguin your input is required
@syncer if there is an actual issue we need more input from the user to continue. ONHOLD for me (or ARCHIVE).
Design-wise this is the right choice. Other platforms have adopted this mantra. The only thing we need to think about is the default policy for intra-zone traffic (allow, drop, reject). My personal preference would be to set the default-intra-zone policy to allow-all within the upgrade scripts, otherwise drop for new configs.
If you want have a better NAT64 solution take a look to jool. (http://jool.mx/en/index.html).
Now that we can add user-pass authenticaton so the configuration is accepted without cert and keyfile we can fool the configuration to make it accept and work with pkcs11 settings:
requires testing on the latest rolling
since we moved to frr, this requires testing with latest rolling
requires testing on latest rolling
requires testing with latest rolling