I agree, even if its "odd" at first sight I like that all interfaces are named ethX within VyOS and then its a matter to map each to physical interface by hw-id (which is done automagically during first install but can be remapped if wanted).
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 18 2023
I am against this change, why not use eth0 everywhere? If it's a WAN or LAN port should be user decidable. Please use udev rules to rename those interfaces to eth0...ethXX
ahh.. looking at it now it looks like the new upstream DTB uses lanX for all "lan" switchports..
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
Hey @fernando - yes, I tested it with two routers in a test environment, with the following setup: https://docs.vyos.io/en/latest/configuration/vpn/site2site_ipsec.html
Do you tested it ? using our current rolling-release
This is on a virtio interface:
Simple reproducer - doesn't need to be an upgrade, just apply this to 1.4
Nov 16 2023
Things to note that I'm not sure if they play a part:
Re-Opening. this need to be extended to bridge firewall
>>> from vyos.ifconfig import Interface >>> Interface('tun0').get_mac() '192.0.2.1'