https://vyos.readthedocs.io/en/latest/services/snmp.html#snmp-extensions
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 15 2019
I created a pull request to fix it. @guertinf has already test the fix
Oh I just noticed: "set src" in a route-mao only works for ipv4 addresses in vyos, according to a friend FRR does support ipv6 though...
I'm no vyos expert but something along these lines should do it:
https://github.com/vyos/vyatta-cfg-quagga/pull/30
@dienac Any results to share?
You need to upload your script to /config/user-data, once done you can configure it via 'set service snmp script-extensions extension-name <extensionname> script <script_name>'
Noticed this today. Possibly another related bug, seems to have appeared the same time the previous ones were fixed. Hostname in bgp is showing up as 'debian', the hostname command, /etc/hostname, /etc/resolv.conf show the correct hostname.
Thanks! Here you go!
Jul 14 2019
"cheat link here"
I tested and it works for me as expected. I also have a test record on the internal DNS server not in name space '.intern', so I checked everything not '.intern' goes to the DNS server 1.1.1.1. It seems the more specific wins.
It will be definately a Kernel issue. I will close this now as it seems to be resolved. Please re-open when the issue re-appears on a new update of the kernel.
Woah hang on.... we actually consulted the documentation on this?! That’s cheating
Is this what you expect?
strange, I just have to reboot again with same software version and now it looks good!!
I tested again with vyos-1.2.0-rolling+201907141109 but in recursor.conf the domain forwarding is missing (VyOS config is the same as in tests before):
The new implementation will behave as follows:
After reading the PowerDNS docs this should be correct: forward-zones-recurse=.=1.1.1.1,intern=172.16.10.1 I will take a look.
Jul 13 2019
Looking at the Jenkinsfile it seems that missing sudo is the only difference:
Hello, @ekim! I see now. This is more looks like the waiting due to I/O. Do, please, the next:
- Run sudo atop -w /tmp/atop-mon.log -a 5 60 in dedicated terminal.
- Try to work several minutes in the terminal. It must freezing at this moment, otherwise, collected test data will be wrong.
- Wait until atop finish its work (~ 5 min from the start).
- Copy the file /tmp/atop-mon.log from the router and send to us for analysis.
Jul 12 2019
Same issue present in 1.3
@bmtauer is this still a problem for you?
test config looks like this:
Jul 11 2019
Neither have configurations on them. However, CLI response time when a configuration is loaded is even slower on 1.2.1-s2. Of course, no perceptible impact on 1.1.8.
From the slack discussion, we found there should be a single forward-zones-recurse line as the last one takes precedence
Can you share your configuration and the actual /etc/powerdns/recursor.conf file? And an expected /etc/powerdns/recursor.conf?
It worked as it looked like this:
A check is already present when configuring the firewall name.
How should the config look like?
As long as its allowed but not working its a bug.. :)
recursor.conf looks like this:
The problem is back in 1.2.0-rolling+201907110337 :-(
The line with the forwarders in recursor.conf is missing again.
@c-po
How can I reopen this task here?