I added a log rule to:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 24 2019
why do we use fwmark in this case? As far as I can see ip rule give us all needed selectors:
Feb 18 2019
@TriJetScud please see :
Jan 24 2019
can reproduce ob EPA3:
Jan 21 2019
Can't reproduce with EPA3
Jan 18 2019
Jan 11 2019
@syncer @dmbaturin Please do not remove use current code!
@syncer thats not true:
Jan 10 2019
Was it not RC6 which got 4.19.0? If I read the kernel changelog right there where some other problems with igb fixed in this area ....
Also I found https://ubuntuforums.org/showthread.php?t=2404431.
Jan 8 2019
Please unbreak now. The next test date was announced!!
Jan 6 2019
Jan 5 2019
@merjin @c-po please have a look to the debian wiki page especially to the mibs-downloader.
Jan 4 2019
We should have an eye on https://community.openvpn.net/openvpn/ticket/208 cause this will change the config logic again completly.
It is not a bug in VyOS self. If you look inside the description of this oid:
Thx for the feedback indeed it runs much better with the virtio-net driver. Bit the e1000 is the default if you choose Debian as OS in Virtualbox.
VyOS is not available in Virtualbox as OS Template. I think we should try to get an own template with nice defaults into Virtualbox. Should I open a case
in Virtualbox for it? Do we have a list of settings that would be optimal for an VyOS vm?
Jan 3 2019
Dec 12 2018
Please go direct to version 1.0.3 cause:
Oct 20 2018
pdns recursor is from the same people who writes dnsdist.
There are three products wirh diffrent scopes:
There is no way to signal DOH (DNS over HTTP/S) via dhcp.
DOH and DOT is supported in latest dnsdist packages see https://dnsdist.org/ and https://mailman.powerdns.com/pipermail/dnsdist/2018-August/000466.html.
Oct 19 2018
As far as I can see it is enabled by default in recent frr:
Oct 18 2018
I will bring this up again. We have now in 1.2 all we need.
Have you seen this: https://github.com/reubenhwk/radvd/issues/45 ??
I have take a look and the todo would be:
this is now fixed in 201810180337. Please test!
On my system ist runs without problems
Oct 17 2018
I have the same problem here with 201810170747.
My router is without this firmware complete unuseable.
Oct 13 2018
If you want have a better NAT64 solution take a look to jool. (http://jool.mx/en/index.html).
<dmbaturin> Hi! If you are ready to help with testing it, I'll be happy to make a CLI.
<dmbaturin> I think it should be orthogonal with all other features indeed, so a perfec candidate for RC3.
<dmbaturin> It would be perfect if you make a small write-up on setting it up by hand in FRR because I haven't used RPKI yet.
<dmbaturin> Hi! If you are ready to help with testing it, I'll be happy to make a CLI.
<dmbaturin> I think it should be orthogonal with all other features indeed, so a perfec candidate for RC3.
Oct 12 2018
It would be nice to have it in 1.2 .x cause in the moment most poviders start enforcing it.
FRR is now included in 1.2.0rc but no large communities. It would be very nice to have support for it cause people like me got only 32bit ASN.....