any idea about an alternative CLI? This is beta functionality in VyOS 1.4 and we can change it arround
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 19 2021
As an option it is possible this workaround:
Install tshark and use this script https://george.mibloving.net/nivex/d6rm/raw/commit/701d49cce3a308aed0c3d89d47be7601178ea4c4/d6rm.py
All subnets that share the same physical network should be declared within a shared-network declaration
Oct 18 22:24:01 r1-roll dhcpd[4985]: Interface eth2 matches multiple shared networks
Of course, external services with the same port is not available
This is what you should expect from NAT rules (110)
Works exactly as configured
Oct 18 2021
Have you confirmed that you can access an external service(i.e. in the 192.168.0.20/24 network) hosted on port 22, and it is not being redirected to 172.24.33.33:22 after applying the rules above?
This can easily be reproduced using ESXi and UEFI bios. Looks like an issue with live-boot.
rVYOSONEX47261d051759: bgp: evpn: T1513: VNI rt and rd are only supported under EVPN VRF.
Other test.
In same lab, pool for LAN subnet was modified:
More tests where done on version 1.3.0-epa1.
First, dhcp_server.py was modified as indicated.
@mickvav You can use ". Can you re-check it?
Tested on node VyOS 1.4-rolling-202110130217
Resolved using
Oct 17 2021
Hi Viacheslav,
As I know, iptables works only in UTC time. And any workaround with recalculate Datetime will be affected incorrect behavior.
Tests were done using 1.2.8 and 1.3.0-rc6 version.
Same inconvenient present as described.
Problems is that a default route is added in table 220
As for me we shouldn’t allow to downgrade images. So there are no “downgrade migration scripts”. Each downgrade - good point to get a brick.
At least we should generate a warning.
PR for "crux": https://github.com/vyos/vyos-1x/pull/1029
Can you please retry with the latest 1.4 image as the EUI64 address generation changed and is now "stable/predictive" like on ethernet interfaces
@jestabro I will suggest a move from certbot
to https://github.com/go-acme/lego
This will give us some more flexibility with LE provision
let's do it but not in syslog section