PR for 1.3 https://github.com/vyos/vyos-1x/pull/1410
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 12 2022
Hi, but one more thing related NAT and VRF in 1.4 rolling. As you know it uses NF MAP, to isolate conntrack tables, so we need to create some design to fix this moment. Matbe with adding some mark
set interfaces bonding bond0 member interface 'eth1' set interfaces bonding bond0 member interface 'eth2' set interfaces bonding bond0 vif 10
Jul 11 2022
I've re-tested this issues with the initial configuration, nat source / mesquered/ destination , it seems to work as @Dmitry said. The conntrack doesn't show the connection as [UNREPLIED] , it's established :
Prototype PR using Tayga: https://github.com/vyos/vyos-1x/pull/1408
Similar task T3810 points 5, 8
PR https://github.com/vyos/vyos-1x/pull/1407
vyos@r14# run show conntrack table ipv4 Id Original src Original dst Reply src Reply dst Protocol State Timeout Mark Zone ---------- ------------------- ----------------- ----------------- ------------------- ---------- ----------- --------- ------ ------ 3529842617 192.168.122.1:53508 192.168.122.14:22 192.168.122.14:22 192.168.122.1:53508 tcp ESTABLISHED 431999 0 4102830655 192.0.2.10 1.0.0.1 1.0.0.1 192.168.122.14 icmp 18 0 59651 179791316 192.0.2.10 1.1.1.1 1.1.1.1 192.168.122.14 icmp 12 0 59651 [edit] vyos@r14#
Today I tested VRF route leaking and NAT. It works on 1.3.1-S1. Simple configuration:
Jul 10 2022
The same task T4511
@raphielscape Could you re-test it?
vyos@r14# set interfaces ethernet eth0 ip adjust-mss Possible completions: clamp-mss-to-pmtu Automatically sets the MSS to the proper value <500-65535> TCP Maximum segment size in bytes
Fixed
S>* 0.0.0.0/0 [210/0] via 192.0.2.1, eth1, weight 1, 00:02:31 C>* 192.0.2.0/24 is directly connected, eth1, 00:02:31 C>* 192.168.122.0/24 is directly connected, eth0, 00:04:09
Jul 9 2022
@Viacheslav, thanks.
Already fixed in roling
vyos@vyos# set service pppoe-server interface eth0 vlan-range Possible completions: start-end VLAN monitor range for the automatic creation of vlans (e.g. 1-4094)
Any chance you can test this on 1.4 rolling image?
(07:27) vyos_bld 8214ca94b6bc:/vyos/telegraf # ls -alh telegraf -rwxr-xr-x 1 vyos_bld vyos_bld 157M Jul 9 07:08 telegraf
Jul 8 2022
I've been running TAYGA inside VyOS with absolutely no problems for the last several years.
I would suggest going with tayga if this feature is planned to be implemented.
Jul 7 2022
Output plugins that we use in 1.4
"github.com/influxdata/telegraf/plugins/outputs/azure_data_explorer" "github.com/influxdata/telegraf/plugins/outputs/influxdb_v2" "github.com/influxdata/telegraf/plugins/outputs/prometheus_client" "github.com/influxdata/telegraf/plugins/outputs/http"
Feature backport: https://github.com/vyos/vyos-1x/pull/1400
Jul 6 2022
This feature would be very helpfull for hairpin nat as we can see from the mentions.
Might also be helpfull for ipv6 as well.
I am aware its a different product but edgeos from ubiquiti does something like this (looks to be a managed address group that populates dynamically) for nat and fw: