ahh.. looking at it now it looks like the new upstream DTB uses lanX for all "lan" switchports..
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Nov 18 2023
Enumaration order and names are specified here:
DSA switch ports: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts#L408-L459
CPU Ethernet ports: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts#L171-L198
@Apachez no, they are not mapped by hw-id, all mapping of DSA ports are done by the DTB file (Hardware Device Tree) loaded into the kernel. also the enumeration order of cpu ethX interfaces are specified by the DTB file
Does all the interfaces at bananapi represent a hw-id which can be used to map to the ethX syntax of VyOS?
Nov 17 2023
Nov 16 2023
Re-Opening. this need to be extended to bridge firewall
>>> from vyos.ifconfig import Interface
>>> Interface('tun0').get_mac()
'192.0.2.1'I would like to contribute with a PR about this. At the same, time I would need some guidance on identifying the conditions requiring the onlink option to be added.
I have a similar setup where I have two VyOS VMs used as VPN routers with some firewalling enabled. Since I use OSPF for dynamic routing I am not able to synchronize the sessions between both routers so in case one VPN router fails the other one can't take over flawlessly. Having conntrack-sync configuration separated from VRRP would be a great benefit.
This can be done in other areas such as firewall rules already:
Nov 15 2023
PR https://github.com/vyos/vyos-1x/pull/2491
vyos@r4# run show interfaces summary
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address MAC VRF MTU S/L Description
----------- ----------------- ----------------- ------- ----- ----- -------------
dum0 203.0.113.1/32 96:44:ad:c5:a1:a5 default 1500 u/u
eth0 192.168.122.14/24 52:54:00:f1:fd:77 default 1500 u/u WAN
eth1 192.0.2.1/24 52:54:00:04:33:2b foo 1500 u/u LAN-eth1
eth1v10v4 10.10.10.10/24 00:00:5e:00:01:0a foo 1500 u/u
eth2 - 52:54:00:40:2e:af default 1504 u/u LAN-eth2
eth3 - 52:54:00:09:a4:b4 default 1500 A/D
eth4 - 52:54:00:2c:51:09 default 1500 A/D
eth5 - 52:54:00:f3:1d:e8 default 1500 A/D
lo 127.0.0.1/8 00:00:00:00:00:00 default 65536 u/u
::1/128looks great from my perspective (I've just updated our nodes. Tested on Community Edition client on windows and Connect V3 client on windows and Tunnelblick on Mac all working as expected. (I tested with; 1.5-rolling-202311150738).
nice work!
Created a related feature request but for VRRP here
https://vyos.dev/T5745
Fix was merged into 1.4 and 1.5.
I had entered the command as you have suggested and I think it's working somehow.
PR for 1.5
https://github.com/vyos/vyos-1x/pull/2483
@JeffWDH looks good to me. It definitely should fix this.
Nov 14 2023
The country-code item in the config_dict is type list and gets skipped by the convert_to_set_commands function.
I wonder if we should use permanent API call queries that don't depend on the path.
@watson.ash Will be fixed in the next rolling release. Could you check it (after 2023-11-14)
And we can backport it to 1.4 if all works fine.
Thanks.