• Viacheslav (Viacheslav Hletenko) <phabricator@mg.vyos.io> [2024-06-24 :46:46]:

Great, maybe we can use jool to build it!

We can add guidelines about running vyos on LXC/LXD in the documentation

Must run in physical NIC pass-through mode
It is recommended to execute the container in privileged mode
This is currently only an initial implementation!

@c-po How is the review and discussion on this feature going?

I'm not free now. I'll check it when I'm free

As a first step, we need a wrapper script to control the start, stop and restart of socat, because socat sometimes exits automatically

As a first step, we need a wrapper script to control the start, stop and restart of socat, because socat sometimes exits automatically

@sdev @Netboy3 I'll test if the new implementation is done and if the bug is fixed I'll close this PR, thanks

PR: https://github.com/vyos/vyos-1x/pull/1550

@Netboy3 Let me modify the template to support

Maybe we should add check to NAT66 to enforce the given address

PR: https://github.com/vyos/vyos-1x/pull/1542

I re-reviewed this PR and the following commit from @c-po

https://github.com/vyos/vyos-1x/pull/1535

PR: https://github.com/vyos/vyos-1x/pull/1533

When the interface of the bridge registers VLANs, the bridge itself must register the same VLANs at the same time, otherwise the bridge will not forward VLANs

https://github.com/vyos/vyos-1x/pull/1511

hi, you can set this to a subtask of my task

@hensur You haven't dealt with this for a long time

It sounds like people prefer jool, and in my personal opinion, if there is a package that is still active up to now, like jool, then jool is probably better. But whatever it is, it's foreign to me

@ajgnet If you have a way to limit the dynamic prefix to a known prefix, then using 1:1 NAT66 prefix translation should work (only the host segment is dynamic)

@c-po You haven't replied for a long time, please let me know if you have any other questions

Should I make improvements to the remaining revisions in the PR?

Sorry I just saw it now, I'll test it. But because of limited conditions, I may test in the future, please forgive me

In T3435#115394, @n.fort wrote:

Error still present on VyOS 1.4-rolling-202201020317

vyos@vyos:~$ show nat source rules 
Traceback (most recent call last):
  File "/usr/libexec/vyos/op_mode/show_nat_rules.py", line 114, in <module>
    print(format_nat_rule.format(rule, srcdests[0], tran_addr, interface))
IndexError: list index out of range
Rule       Source                                             Translation                                        Outbound Interface
----       ------                                             -----------                                        ------------------
vyos@vyos:~$ show ver

Version:          VyOS 1.4-rolling-202201020317
Release train:    sagitta

Nat config in this example:

vyos@vyos:~$ show config comm | grep nat
set nat source rule 10 description 'Masquerade to NAT'
set nat source rule 10 outbound-interface 'eth0'
set nat source rule 10 translation address 'masquerade'

@hensur See PR, I implemented a merge script and provided three solutions.

@hensur I'm glad you reimplemented this feature. Come on

• The problem about DHCPv6 has been solved
• The communication problem has been solved

It seems that the problem is related to IPv6 MSS. When I set IPv6 MSS to 1280 and IPv4 MSS to 1452, the problem seems to disappear

Merging this PR can fix this problem. Due to the complexity of the JSON parsing of NFT by the operation mode script, this task still needs to be tested, and the local test passes

@raphielscape Are there still problems after updating PR? Please provide the configuration and I'll take the time to check it

PR: https://github.com/vyos/vyos-1x/pull/951