Page MenuHomeVyOS Platform

jack9603301 (JACK)
User

Projects

User does not belong to any projects.

User Details

User Since
Mar 19 2020, 5:57 AM (31 w, 4 h)

Recent Activity

Yesterday

jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

It has passed the GNS test, and the test cases are as follows:

Wed, Oct 21, 8:20 AM · VyOS 1.3 Equuleus

Tue, Oct 20

jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

What content of "conf-path" ?

Tue, Oct 20, 10:59 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

Hello everyone, I am integrating tinc. At present, I have passed the basic test in a simple virtual machine. The command line is simplified. Examples are as follows:

Tue, Oct 20, 10:31 AM · VyOS 1.3 Equuleus

Sun, Oct 18

jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

I agree. Therefore, if someone understands the code structure of FRR, we can modify the implementation from within FRR according to Prometheus protocol framework, implement the exporter integration, and then generate a patch file. Set the automatic compilation script and automatically package it into DEB

Sun, Oct 18, 6:25 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

It is true, but I just want to record it to avoid forgetting that another solution is to redevelop FRR and promote it in parallel with the official version of FRR (in other words, we can patch FRR or maintain a branch separately, then compile a version of our own, and get the indication directly from its code, but this work needs someone to do.)

Sun, Oct 18, 3:57 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

I think I understand what you mean. Don't worry. I'm also a user of Prometheus. I know how Prometheus works.

Sun, Oct 18, 3:51 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

Most of Prometheus data is generated from the exporter. It is not collected and pushed in real time. When Prometheus queries, it can query relevant indications through the port exposed by the exporter. Therefore, I don't think it is possible to create thousands of sub processes/threads. What do you think?

Sun, Oct 18, 3:30 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

@runar Some interesting commands, such as ` tinc - n netname join URL, seem to be supported in tinc1.1

Sun, Oct 18, 2:37 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

The frr_exporter linked uses os/exec to run an external binray, /usr/bin/vtysh. This is not a great way to build an exporter, as it can lead to a fork bomb. There is also the overhead of calling the external binary to gather data.

Sun, Oct 18, 2:27 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

Tinc 1.1 supports rereading a lot of the configuration without resetarting the daemon, i've compiled a version of 1.1 for you from the debian salsa repository: https://salsa.debian.org/guus/tinc/-/tree/1.1/debian (this is whats available in the experimental debian branch) the deb is available her for now: https://borge.nu/vyos/tinc_1.1~pre17-1.1_amd64.deb. just put it in the packages directory when you're generating the iso or dpkg -i it into a image that have tinc-1.0 allready.

Sun, Oct 18, 1:59 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

Do you know of a version of that FRR exporter that doesn't fork sub processes?

Sun, Oct 18, 1:41 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

What information do you need access to from within op-mode?

Sun, Oct 18, 1:35 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

I hope to implement an operation mode command, but too many interface parameters are generated according to the configuration in the interface. I don't know how to call these existing configurations. Can I call the user's configuration information through config in operation mode?

Sun, Oct 18, 1:28 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

To prevent forgetting, write the address of the exporter to task

Sun, Oct 18, 11:53 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

I updated pr. so far, tinc VPN cli will automatically generate the local node key file, such as the following code:

Sun, Oct 18, 9:53 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T160: Support NAT64.

Isn't anyone implementing this feature right now?

Sun, Oct 18, 4:35 AM · VyOS 1.3 Equuleus

Sat, Oct 17

jack9603301 added a comment to T2986: Unable to build qemu.

Must this command be executed from docker now?

Sat, Oct 17, 11:55 AM · VyOS 1.3 Equuleus
jack9603301 updated the task description for T2986: Unable to build qemu.
Sat, Oct 17, 10:52 AM · VyOS 1.3 Equuleus
jack9603301 created T2986: Unable to build qemu.
Sat, Oct 17, 10:51 AM · VyOS 1.3 Equuleus

Fri, Oct 16

jack9603301 added a comment to T973: Create Prometheus Exporter for VyOS .

Quite interesting, support, in fact some information can not be captured from SNMP very well

Fri, Oct 16, 6:36 PM · VyOS 1.3 Equuleus

Thu, Oct 15

jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

@runar The preliminary integration of tinc is basically completed, please see

Thu, Oct 15, 12:52 PM · VyOS 1.3 Equuleus

Tue, Oct 13

jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

I am implementing tinc, but there is a problem I haven't figured out. Normally, in order for tinc to run, it must have a public key and a private key, and it happens that there will be a prompt for this generation command (ask where to save, etc), and it happens that the public key of the local node in the hosts directory is usually used together with some host configuration options. Is there a better way to implement it?

Tue, Oct 13, 4:07 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

I wrote a preliminary CLI configuration file rule. This is the first step in tinc implementation. For details, please read: https://github.com/jack9603301/vyos-1x/blob/T766/interface-definitions/interfaces-tinc .xml.in

Tue, Oct 13, 3:45 AM · VyOS 1.3 Equuleus

Mon, Oct 12

jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

Another option is to compile and package by yourself, but the location of the repository is the problem

Mon, Oct 12, 7:17 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T766: Implement support for the Tinc VPN daemon.

I don't think it's necessary to compile DEB packages because they can be obtained directly from apt

Mon, Oct 12, 2:57 AM · VyOS 1.3 Equuleus

Fri, Oct 2

jack9603301 added a comment to T2898: Support NDP proxy.

At this stage, I can't realize the automatic configuration of NDP proxy. On the other hand, although I don't know what additional application scenarios will be in addition to NDP, I hope to give full play to the full potential of NDP proxy, so I don't want to bind it to nat66 artificially.

Fri, Oct 2, 2:22 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Thu, Oct 1

jack9603301 added a comment to T2898: Support NDP proxy.

@c-po Request merge https://github.com/vyos/vyos-1x/pull/556

Thu, Oct 1, 2:22 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Wed, Sep 30

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

NDP Proxy has been implemented in T2898. For nat66 to work normally, proxy-ndp must be operated in static mode.

Wed, Sep 30, 2:19 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

Already basically ready to merge

Wed, Sep 30, 2:15 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Wed, Sep 30, 1:31 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T597: Code testing on sonarcloud.com.

I accidentally found sonarcloud, vyos now uses this system for quality control?

Wed, Sep 30, 10:30 AM · VyOS 1.3 Equuleus

Tue, Sep 29

jack9603301 updated the task description for T2898: Support NDP proxy.
Tue, Sep 29, 6:27 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Tue, Sep 29, 5:12 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

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

Tue, Sep 29, 8:50 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Mon, Sep 28

jack9603301 updated the task description for T2898: Support NDP proxy.
Mon, Sep 28, 2:02 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Mon, Sep 28, 9:15 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Mon, Sep 28, 3:39 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Sun, Sep 27

jack9603301 added a comment to T2898: Support NDP proxy.

Write redundant and intrusive code for all interface types, which may introduce unknown errors (I can’t guarantee 100% accuracy without testing)

Sun, Sep 27, 4:30 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

@c-po I am thinking about a problem. Placing proxy-ndp under the child node of interface may generate redundant implementation code and is intrusive. In fact, for proxy-ndp, only one configuration file is needed. Is this Reasonably, I don't even know how to test the intrusive code comprehensively without affecting the basic functions of the router.

Sun, Sep 27, 4:26 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Fri, Sep 25

jack9603301 updated the task description for T2898: Support NDP proxy.
Fri, Sep 25, 9:12 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Thu, Sep 24

jack9603301 updated the task description for T2518: Support NAT for ipv6(NPT).
Thu, Sep 24, 6:06 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

Also come back to this question?

Thu, Sep 24, 2:15 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

In linux kernel version 5.8 and above, you can start symmetric translation of ipv6 address prefix by changing snat to to snat prefix to in the policy (without changing the interface identifier), but this function cannot be used before vyos upgrade 5.9 , This patch is not a back-portable patch, so this feature cannot be used in 4.9. There are now 3 solutions:

Thu, Sep 24, 11:36 AM · VyOS 1.3 Equuleus

Wed, Sep 23

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

Hi, everyone, I have been looking for a way to handle the 1-to-1 address peer-to-peer mapping. I contacted the IRC channel of the official community. According to the official information, it seems to be resolved in the 5.8 kernel version, otherwise the patch needs to be backported To 4.19.

Wed, Sep 23, 1:49 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

@c-po The map66 solution last released on July 25th, 2015 does not seem to have been explored. It can work with iptables. I am not sure if it has stopped maintenance. I am considering whether to consider it, but it means that it needs to be compiled, installed and generated , Otherwise vyos cannot install it

Wed, Sep 23, 9:11 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

Thank you for your suggestion. I am considering how to implement peer-to-peer translation without modifying the interface identifier. According to some information on the Internet, the support of ipv6 nat is divided into peer address and non-equivalent address, the standard https://tools.ietf The display of .org/html/rfc6296#page-11 does not indicate that the interface identifier cannot be modified, but only stipulates that the address mapping conforms to the unary linear equation relationship (that is, an address mapping is unique)

Wed, Sep 23, 9:03 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

nftables nat66 seems to be the best solution that can be done now, I am still exploring a better implementation, do you have any suggestions?

Wed, Sep 23, 3:57 AM · VyOS 1.3 Equuleus

Tue, Sep 22

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

Well, at present, the nat66 prefix conversion of nftables has not found a way to not change the interface identifier. Maybe other people in the community can provide some suggestions?

Tue, Sep 22, 6:50 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

With NFT SNAT prefix translation, the address is not a 1:1 mapping. For example, if we have source prefix 2001:db8:1::/64 and translation prefix of 2001:db8:2::/64, the source address 2001:db8:1::1 will not translate to 2001:db8::2::1. The nftables translation calculates a new address which prevents the 1:1 host address mapping.

Tue, Sep 22, 6:42 PM · VyOS 1.3 Equuleus

Sep 21 2020

jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 21 2020, 6:41 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 21 2020, 5:58 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 21 2020, 5:58 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Sep 20 2020

jack9603301 added a comment to T2898: Support NDP proxy.

@c-po If I want to be an interface-ethernet.xml.in Add custom configuration actions (such as proxy NDP) with certain extensibility (its configuration can be extended in other places). What should I do?

Sep 20 2020, 3:19 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Sep 19 2020

jack9603301 moved T2898: Support NDP proxy from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
Sep 19 2020, 6:12 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 moved T2518: Support NAT for ipv6(NPT) from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
Sep 19 2020, 6:12 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

I also take into account the specific situation of the ndp proxy, the configuration of this link prompts, the configuration format of the ndp proxy is like this.

Sep 19 2020, 6:06 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 19 2020, 5:51 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 19 2020, 5:51 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

No arp proxy option is found in the configuration path, ndp proxy can manage multiple address rules under one interface

vyos@vyos# set interfaces ethernet eth0 ip 
Possible completions:
   arp-cache-timeout
                ARP cache entry timeout in seconds
   disable-arp-filter
                Disable ARP filter on this interface
   enable-arp-accept
                Enable ARP accept on this interface
   enable-arp-announce
                Enable ARP announce on this interface
   enable-arp-ignore
                Enable ARP ignore on this interface
   enable-proxy-arp
                Enable proxy-arp on this interface
 > ospf         Open Shortest Path First (OSPF) parameters
   proxy-arp-pvlan
                Enable private VLAN proxy ARP on this interface
 > rip          Routing Information Protocol (RIP)
   source-validation
                Policy for source validation by reversed path, as specified in RFC3704
Sep 19 2020, 5:46 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

Although I intended to think that it is easier to write scripts under the protocol, but from an intuitive point of view, it seems that this path is also a good choice (users can use the same command line as the arp proxy to configure) I have written it A sample, then only need to decide how to modify the cli

Sep 19 2020, 5:24 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

set interfaces ethernet eth0 ip proxy-arp

The more suitable position may be set protocol ndp-proxy

I...really would like to not put it under "protocols" but to put it under the interface. It's *much* easier and more intuitive to see it under the interface/sub-interface than to see it in its' own stanza under "protocol" node.

Also, I'd argue it would be reasonable to separate ARP proxy and NDP proxy. That way one can pick and choose. Of course ARP proxy can't work without an IP address configured. NDP proxy can't be configured without an IPv6 address configured (those could be used as checks against configuring it on an empty interface).

Sep 19 2020, 5:21 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

If possible, give your suggested cli path for my reference

Sep 19 2020, 5:18 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 19 2020, 1:34 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 changed the status of T2898: Support NDP proxy, a subtask of T2518: Support NAT for ipv6(NPT), from Open to In progress.
Sep 19 2020, 9:39 AM · VyOS 1.3 Equuleus
jack9603301 changed the status of T2898: Support NDP proxy from Open to In progress.
Sep 19 2020, 9:39 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 19 2020, 7:21 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

I can't find how to enable ipv6 connection tracking. Recompiling and modifying the linux kernel switch does not seem to see the module loaded. I think the current nat66 has completed 90%, and only need to implement ndp proxy to make it work normally.

Sep 19 2020, 7:20 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

set interfaces ethernet eth0 ip proxy-arp

Sep 19 2020, 7:17 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

I think we do need it, we can’t let users manage all IP manually unless we implement stateful NAT66

Sep 19 2020, 7:15 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 triaged T2898: Support NDP proxy as Normal priority.
Sep 19 2020, 6:41 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 claimed T2898: Support NDP proxy.
Sep 19 2020, 6:40 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 updated the task description for T2898: Support NDP proxy.
Sep 19 2020, 6:30 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a project to T2898: Support NDP proxy: VyOS 1.2 Crux.
Sep 19 2020, 6:29 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 added a comment to T2898: Support NDP proxy.

Beeing stateless or statefull both should work. We can add a CLI node for the proxy.ndp option like we have for proxy arp on ipv4, no big deal.

Sep 19 2020, 5:29 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus
jack9603301 created T2898: Support NDP proxy.
Sep 19 2020, 3:59 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Sep 18 2020

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).
In T2518#75586, @c-po wrote:

Beeing stateless or statefull both should work. We can add a CLI node for the proxy.ndp option like we have for proxy arp on ipv4, no big deal.

Sep 18 2020, 2:56 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

This is a milestone, which means we have to decide whether to use stateful or stateless

Sep 18 2020, 1:58 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

It is confirmed that there is a bug in the implementation, but no solution has been found yet. In the nat66 rule, the prefix translation is indeed performed in the expected behavior, but the upstream device cannot return the data packet from the specific prefix. If the community has a good solution, please let me know

Sep 18 2020, 11:45 AM · VyOS 1.3 Equuleus
jack9603301 changed the status of T2518: Support NAT for ipv6(NPT) from On hold to In progress.
Sep 18 2020, 10:50 AM · VyOS 1.3 Equuleus

Sep 17 2020

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).
Sep 17 2020, 5:03 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

Please give the configuration of R1 so that I can immediately test your topology in the simulation environment

Sep 17 2020, 2:50 AM · VyOS 1.3 Equuleus

Sep 15 2020

jack9603301 added a comment to T2884: Upstream Kernel Patches from Semper Victus Linux Hardened Tree.

It’s best to provide links to related descriptions instead of asking everyone to search for the related details and patch implementations you describe

Sep 15 2020, 3:13 PM · VyOS 1.3 Equuleus

Sep 14 2020

jack9603301 added a comment to T2880: Update Linux Kernel to v4.19.145.

Isn't it upgraded to 5.x? Why 4.x?

Sep 14 2020, 1:05 AM · VyOS 1.3 Equuleus

Sep 10 2020

jack9603301 awarded T2874: Add MTU and TCP-MSS discovery tool a Like token.
Sep 10 2020, 3:41 PM · VyOS 1.3 Equuleus

Sep 2 2020

jack9603301 changed the status of T2518: Support NAT for ipv6(NPT) from Blocked to On hold.
Sep 2 2020, 11:39 AM · VyOS 1.3 Equuleus
jack9603301 changed the status of T2518: Support NAT for ipv6(NPT) from On hold to Blocked.
Sep 2 2020, 11:34 AM · VyOS 1.3 Equuleus

Aug 31 2020

jack9603301 updated the task description for T2518: Support NAT for ipv6(NPT).
Aug 31 2020, 11:09 AM · VyOS 1.3 Equuleus
jack9603301 renamed T2518: Support NAT for ipv6(NPT) from Support nptv6 to Support NAT for ipv6(NPT).
Aug 31 2020, 10:50 AM · VyOS 1.3 Equuleus

Aug 29 2020

jack9603301 added a comment to T291: support for Predictable Network Interface Names.

We look forward to the solution of this problem

Aug 29 2020, 8:10 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T291: support for Predictable Network Interface Names.

Is this problem solved at present?

Aug 29 2020, 7:59 AM · VyOS 1.3 Equuleus

Aug 24 2020

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

The updated code was successfully tested on the virtual machine, and 5.1 has not been tested yet, waiting for the release of kernel 5.1

Aug 24 2020, 3:53 AM · VyOS 1.3 Equuleus

Aug 23 2020

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

As described in T2814, under 5.1, nft_chain_nat_ipv6 will be merged into nft_chain_nat, I have updated pr to support this change, but like T2814, it has not been tested

Aug 23 2020, 10:10 AM · VyOS 1.3 Equuleus

Aug 22 2020

jack9603301 added a comment to T2518: Support NAT for ipv6(NPT).

The SNPT and DNPT functions are basically implemented, but because they have not been reviewed and approved for the time being, they enter the hold state, waiting for processing and discussion

Aug 22 2020, 2:12 PM · VyOS 1.3 Equuleus
jack9603301 changed the status of T2518: Support NAT for ipv6(NPT) from In progress to On hold.
Aug 22 2020, 2:09 PM · VyOS 1.3 Equuleus

Aug 20 2020

jack9603301 awarded T439: local PBR support a Like token.
Aug 20 2020, 10:32 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2814: kernel 5.1+ : NAT : module `nft_chain_nat_ipv4` renamed.

Thanks

Aug 20 2020, 4:50 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2814: kernel 5.1+ : NAT : module `nft_chain_nat_ipv4` renamed.

Although nat66 (NPT) is not currently incorporated into the mainline, I may need to modify my implementation if it is also modified

Aug 20 2020, 2:07 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2814: kernel 5.1+ : NAT : module `nft_chain_nat_ipv4` renamed.

Hello, here is a request beyond the outline. Please help me check whether the NAT kernel module of IPv6 has also changed? It turned out to be nft_chain_nat_ipv6

Aug 20 2020, 2:01 AM · VyOS 1.3 Equuleus

Aug 17 2020

jack9603301 updated the task description for T2518: Support NAT for ipv6(NPT).
Aug 17 2020, 1:27 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2694: The information provided by SNMP is incomplete.

Sorry, I don't understand what you mean. Can you tell me more about it? What is using net-snmp to submit feature requests?

Aug 17 2020, 4:09 AM · VyOS 1.3 Equuleus