remote.py declaring support for TFTP and HTTP(S) might complicate things further. Since it's only for downloading, the latter shouldn't be too complicated to handle with urllib but if we need HTTP(S) uploading capabilities, an external library like requests would be preferable. As for TFTP, there's no support for it in the standard library, but instead of pulling in a third-party library for TFTP alone, we can just write an ad hoc wrapper for curl dedicated to TFTP. It wouldn't be as complicated since TFTP has no form of authentication so there's no need to worry about host keys and such.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Mar 1 2021
Mar 1 2021
erkin renamed T936: Reimplementation of tech-support diagnostic file generation from Reimplementaion of tech-support diagnostic file generation to Reimplementation of tech-support diagnostic file generation.
I will try the latest
Unknown Object (User) added a comment to T3353: PPPoE server wrong vlan-range generating config.
Yes, sure. It will work only if one vlan-id defined, e.g. if you configure a couple vlan-id you will get wrong syntax"
set service pppoe-server interface eth1 vlan-id '50' set service pppoe-server interface eth1 vlan-id '60'
In generated config
vlan-mon=eth1,50,60 interface=eth1.50,60
Expected:
vlan-mon=eth1,50,60 interface=eth1.50 interface=eth1.60
PR https://github.com/vyos/vyos-1x/pull/755
@Dmitry Can you check/review PR?
Feb 28 2021
Feb 28 2021
Unknown Object (User) added a comment to T3353: PPPoE server wrong vlan-range generating config.
Good job! I think there exists one remark. If we set set service pppoe-server interface eth1 vlan-id '50' that means you want to listen to pppoe client on eth1.50, but in config you have
vlan-mon=eth1,50 interface=re:eth1\.\d+
e.g. eth1\.\d+ mean all vlans in eth1, even eth1.50.50.50 will fit for this regular expression
I propose do not to use a regular expression for vlan-id, as an example:
- set service pppoe-server interface eth1 vlan-id '50'
vlan-mon=eth1,50 interface=eth1.50
Unknown Object (User) added a comment to T3360: Op command 'show interfaces' does not display VRRP VIP.
Yes, agree it works by show interfaces vrrp, but behavior in 1.2.x also displayed VIP by command show interfaces
I think this is a bug and need to fix it.
c-po moved T3349: Ethernet: "disable" flag is not honored after a reboot for VIF interfaces from Open to Finished on the VyOS 1.4 Sagitta board.
Viacheslav closed T3320: Bgp neighbor peer-group without peer-group fail, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
Viacheslav changed the status of T3353: PPPoE server wrong vlan-range generating config from Confirmed to Needs testing.
sever-sever <v.gletenko@vyos.io> committed rVYOSONEXcf93fec3b38a: pppoe: T3353: Modify template for vlan-mon and interface.
GitHub <noreply@github.com> committed rVYOSONEXf585fd497ad0: Merge pull request #754 from sever-sever/T3353 (authored by c-po).
You can use <x.x.x.x>-<x.x.x.x>
Or you need "multi" addresses not in "range"? Something like
set nat destination rule 5 translation member 203.0.113.1 set nat destination rule 5 translation member 203.0.113.14 set nat destination rule 5 translation member 203.0.113.240
c-po edited projects for T3349: Ethernet: "disable" flag is not honored after a reboot for VIF interfaces, added: VyOS 1.2 Crux (VyOS 1.2.7); removed Restricted Project.
c-po moved T3371: Replace netplugd by udev rules from Open to Backlog on the VyOS 1.4 Sagitta board.
Temporary workaround for the VyOS 1.3-rc1 users:
c-po moved T3370: dhcp: Invalid domain name "private" from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po moved T3370: dhcp: Invalid domain name "private" from Open to In Progress on the VyOS 1.4 Sagitta board.
I agree we should just check if it starts with a letter and doesn't include characters that an FQDN cannot have.
c-po closed T3369: VXLAN: add IPv6 underlay support, a subtask of T1636: Rewrite VXLAN in new style XML/Python, as Resolved.
c-po moved T3369: VXLAN: add IPv6 underlay support from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
Feb 27 2021
Feb 27 2021
c-po reopened T2947: Nat translation many-many with prefix does not map 1-1., a subtask of T3092: nat: migrate to get_config_dict(), as On hold.
Backport is complete - It will "work" once the 1.3 kernel is updated to 5.10 series
c-po changed the status of T3173: Need 'nopmtudisc' option for tunnel interface from Unknown Status to Resolved.
c-po closed T3368: macsec: add support for gcm-aes-256 cipher, a subtask of T2023: Add support for 802.1ae MACsec, as Resolved.
c-po closed T3364: tunnel: cleanup/rename CLI nodes, a subtask of T3072: Migrate tunnel interfaces to new get_config_dict() approach, as Resolved.
GitHub <noreply@github.com> committed rVYOSONEX9cf165145489: Merge pull request #747 from c-po/vxlan-tunnel-parameters (authored by c-po).
rps closed T2291: Bad hostnames in /etc/hosts with static-mapping in dhcp server config as Resolved.
A work-around for this was added in 1.2.6 and I verified it's working in 1.3.0-rc1
starcraft66 added a comment to T2623: Creating sit tunnel fails with “Can not set “local” for tunnel sit tun1 at tunnel creation”.
Just chiming back in to let you guys know I installed the latest vyos rolling release after all this time and the issue seems to have been fixed!
c-po changed the status of T3368: macsec: add support for gcm-aes-256 cipher from Open to In progress.
c-po changed the status of T3368: macsec: add support for gcm-aes-256 cipher, a subtask of T2023: Add support for 802.1ae MACsec, from Open to In progress.
c-po closed T3366: tunnel: can not change local / remote ip address for gre-bridge tunnel, a subtask of T2028: Convert "interfaces tunnel" to new XML/Python representation, as Resolved.
c-po closed T3366: tunnel: can not change local / remote ip address for gre-bridge tunnel as Resolved.
Viacheslav closed T3365: Bgp neighbor interface ordering for remote-as, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Resolved.
@craterman Thanks.
@Viacheslav, tested on VyOS 1.3-beta-202102270443. It works
Node "protocols" in 1.4 also doesn't have a description
c-po renamed T3364: tunnel: cleanup/rename CLI nodes from tunnel: cleanup/rename encapsulation modes to tunnel: cleanup/rename CLI nodes.
c-po moved T3364: tunnel: cleanup/rename CLI nodes from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po moved T3366: tunnel: can not change local / remote ip address for gre-bridge tunnel from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
c-po added a comment to T3366: tunnel: can not change local / remote ip address for gre-bridge tunnel.
This is not applicable to VyOS 1.4 because of T3364.
c-po changed the status of T3366: tunnel: can not change local / remote ip address for gre-bridge tunnel from Open to In progress.
c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.99 / 5.10.17 to Update Linux Kernel to v5.4.101 / 5.10.19.
sever-sever <v.gletenko@vyos.io> committed rVYOSONEXe9733cc1f790: bgp: T3365: After commit bf9c914 config interface become out of the check.
GitHub <noreply@github.com> committed rVYOSONEX46af54fe7545: Merge pull request #753 from sever-sever/T3365 (authored by c-po).
PR https://github.com/vyos/vyos-1x/pull/753
Additional checks for "neighbor interface" configuration.
Viacheslav reopened T3365: Bgp neighbor interface ordering for remote-as, a subtask of T2174: Rewrite protocol BGP to new XML/Python style, as Needs testing.