Okay, and the reason you have not indicated your VyOS reason is because of?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Jul 18 2020
Jul 18 2020
Your log is not very helpful - a full log would be much better, that'
s why we have those show interfaces .... log commands
Then I guess you have not tested the latest version. Closing as Invalid.
I still don't get it - about which address you are talking about? 10.64.64.64 is pppd "hisaddr" which is 0x0a404040 + ppp unit number.
I have no clue what you are talking about
Issue can not be reproduced:
Jul 15 2020
Jul 15 2020
this implementation would ba an operational mode command. THose are deinfed here: https://github.com/vyos/vyos-1x/blob/current/op-mode-definitions/wireguard.xml and package dependencies life here https://github.com/vyos/vyos-1x/blob/current/debian/control
c-po closed T2596: Allow specifying source IP for 'add system image', a subtask of T2651: Generate CLI abstraction for options passed to CURL and SSH client, as Resolved.
Implemented as of T2651
Jul 14 2020
Jul 14 2020
c-po updated subscribers of T2704: connect/disconnect Missing newline in op-mode tab completion helper.
@dmbaturin was there anything changed on the handling of op-mode? As I remember that this used to work.
Jul 12 2020
Jul 12 2020
@jack9603301 the approach from @banditos13 is perfectly fine. Despite the fact that a PR would be the non plus ultra - a problem was identified and a fix was provided - works for me.
Are you familiar with that codebase @jack9603301? As I see no real answer in your posting which does not help at all :(
I feel more like abandoning that daemon and use a python based implementation.
New ISO build triggered with fix - also an MD5 smoketest was added
Bug in the library is confirmed - id completely ignores MD5
Problem seems to be in the 3rd party hash library - when upgrading from 1.2.5 to 1.3 rolling settings persist and work:
MD5 should be supported as it works in VyOS 1.2 - let me have a look.
It is stated in the documentation - that is why I passed it to you
The following rules are now installed after the fix:
Your above ruleset should be tralnsated into thie NFT syntax:
There i no community in SNMPv3 - please read https://docs.vyos.io/en/latest/services/snmp.html#snmpv3
Jul 11 2020
Jul 11 2020
@linuxgemini we do not support DKMS.
c-po changed the status of T2698: Current vyos-build for crux does not include wireguard.ko from Open to In progress.
Jul 10 2020
Jul 10 2020
Well a bit more verbosity would be good. As usual:
- provide config
- logfiles
- routing table
- interface ip list
Jul 8 2020
Jul 8 2020
There is a basic test for this which should be expanded.
A very fast look on the source indicated wrong dictionary keys which have bewn missed out during migration to get_config_dict() - please try next rolling.
c-po triaged T2585: Unable to access the Internet after opening PPPoE on-demand dialing as Low priority.
My guess is this will be resolved by the full BGP rewrite - I also do not like the current behavior.
Jul 7 2020
Jul 7 2020
c-po changed the status of T2687: SNMP: change logic on v3 password encryption from Open to In progress.
Using the mentioned defaults in https://tools.ietf.org/html/rfc3414#appendix-A.3.2
c-po updated the task description for T2651: Generate CLI abstraction for options passed to CURL and SSH client.
This somehow relates to T2651
c-po added a comment to T2691: Upgrade from 1.2.5 to 1.3-rolling-202007040117 results in broken config due to case mismatch.
The reason this is failing is VyOS 1.2 lacks proper input validation on the loglevel nodes.
c-po moved T2663: SNMP does not listen on the specified address from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2671: SNMP failed to start after the system was rebooted from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2680: dhcp6c service cannot recover when it fails from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2682: VRF aware services - connection no longer possible after system reboot from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2676: NTP: migrate to get_config_dict() implementation from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2685: Update Accel-PPP to fix SSTP client issues from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2684: Update Linux Kernel to v4.19.131 from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2681: PPPoE stops negotiating IPv6 from Need Triage to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2599: "show interfaces" does not list VIF interfaces in ascending order from Backlog to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2321: VRF support for SSH, NTP, SNMP service from Backlog to Finished on the VyOS 1.3 Equuleus board.
c-po moved T2389: BGP community-list unknown command from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.6) board.
c-po changed the status of T2389: BGP community-list unknown command from Unknown Status to Resolved.
c-po changed the status of T2686: FRR: BGP: large-community configuration is not applied properly after upgrading FRR to 7.3.x series from Unknown Status to Resolved.
Jul 6 2020
Jul 6 2020
c-po added a comment to T2686: FRR: BGP: large-community configuration is not applied properly after upgrading FRR to 7.3.x series.
So should be cherry-pick this to 1.2.6?
Jul 5 2020
Jul 5 2020
Just digging around I found this:
There is already a new build containing the fix.
c-po added a comment to T2686: FRR: BGP: large-community configuration is not applied properly after upgrading FRR to 7.3.x series.
@Viacheslav could you please check if this probably should make it into 1.2.6 in addition?
Problem was introduced by porting PPPoE to the get_config_dict() implementation T2653 commit https://github.com/vyos/vyos-1x/commit/65fa21f5
c-po closed T2685: Update Accel-PPP to fix SSTP client issues, a subtask of T2684: Update Linux Kernel to v4.19.131, as Resolved.
c-po added a comment to T2678: High RAM usage on SSH logins with lots of IPv6 routes in the routing table..
Does DNS static-host-mapping still work with the nssswich.conf change? I‘m just curious about the side effects.
Jul 4 2020
Jul 4 2020
c-po renamed T2682: VRF aware services - connection no longer possible after system reboot from SSH: VRF: connection no longer possible after system reboot to VRF aware services - connection no longer possible after system reboot.