Hi @alainlamar how should the generated configuration look like?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Apr 4 2020
Apr 4 2020
c-po moved T2213: vyos-1x: WiFi mode ieee80211ac should also activate ieee80211n from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po changed the status of T2213: vyos-1x: WiFi mode ieee80211ac should also activate ieee80211n from Open to In progress.
c-po changed the status of T2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table from Open to In progress.
Apr 3 2020
Apr 3 2020
c-po changed the status of T2206: Split WireGuard endpoint into proper host and port nodes from Open to In progress.
Apr 2 2020
Apr 2 2020
c-po closed T2200: Add VRF support on wirelessmodem interfaces, a subtask of T1988: Migrate wirelessmodem to new XML/Python style interface, as Resolved.
c-po moved T2200: Add VRF support on wirelessmodem interfaces from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po moved T2202: Update PowerDNS recursor to 4.2 series from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po changed the status of T2200: Add VRF support on wirelessmodem interfaces, a subtask of T1988: Migrate wirelessmodem to new XML/Python style interface, from Open to In progress.
c-po changed the status of T2200: Add VRF support on wirelessmodem interfaces from Open to In progress.
c-po closed T1823: l2tpv3 interface migration fails, a subtask of T1556: Rewrite Bridge in new style XML syntax, as Resolved.
Both Routers running VyOS 1.2.3
Apr 1 2020
Apr 1 2020
c-po added a comment to T1875: Add the ability to use network address as BGP neighbor (bgp listen range).
I tried adding it but failed miserably. This should best be done with the entire BGP rewrite.
Mar 31 2020
Mar 31 2020
c-po updated the task description for T2189: Adding a large port-range will take ~ 20 minutes to commit.
Why must the operstate be up? I't rather check if the tunnel is configured (/opt/vyatta/etc/openvpn/status/vtun1.something) exists and then run the commands.
Thus if the tunnel is down due to remote end beeing offline it would not report it as operstate is down (if operstate is properly implemented in OpenVPN)
Mar 30 2020
Mar 30 2020
In IPv6 the next-hop interface is simply called interface to mimic the default IPv6 behavior of the Vyatta code.
Mar 29 2020
Mar 29 2020
vyos@vyos# show interfaces ethernet eth3 address 192.168.3.1/24 vrf red
vyos@vyos# show protocols static route 192.168.3.0/24
next-hop 192.168.3.1 {
next-hop-interface eth3
next-hop-vrf red
}vyos@vyos# run show ip route | match 192.168.3.0 S>* 192.168.3.0/24 [1/0] via 192.168.3.1, eth3(vrf red), 00:01:05
c-po committed rVYOSONEX782e98934547: ifconfig: T2057: remove useless circual import (authored by thomas-mangin).
Mar 28 2020
Mar 28 2020
c-po changed the status of T2028: Convert "interfaces tunnel" to new XML/Python representation from In progress to Needs testing.
c-po changed the status of T2028: Convert "interfaces tunnel" to new XML/Python representation, a subtask of T1579: Rewrite all interface types in new XML/Python style, from In progress to Needs testing.
c-po closed T1988: Migrate wirelessmodem to new XML/Python style interface, a subtask of T1579: Rewrite all interface types in new XML/Python style, as Resolved.
c-po updated the task description for T1988: Migrate wirelessmodem to new XML/Python style interface.
Well - making all IPv6 stuff a noop is not coded into VyOS. Can you show real life examples of increased attack surface?
Actually why do you wan't to disbale IPv6 on the system? I think this is a huge workpackage.