Page MenuHomeVyOS Platform

jack9603301 (JACK)
User

Projects

User does not belong to any projects.

User Details

User Since
Mar 19 2020, 5:57 AM (11 w, 1 d)

Recent Activity

Yesterday

jack9603301 added a comment to T2510: 1.3 DHCPv6 Ethernet not working.

@dsummers Obviously, this kind of output belongs to error report, prompt dhcp6c@eth0 Unable to start normally, measures should be taken to eliminate them. I once submitted a PR (not yet passed) that can try to restart when the service fails. The original intention is to recover from the failure when the first load fails after the restart (because some interfaces are not initialized). I don't know if this patch can help temporarily dhcp6c@eth0 Restart, and complete the startup normally after 10 seconds of failure. However, you can try it. In a word, you should take measures to eliminate such errors.

Fri, Jun 5, 3:51 PM
jack9603301 added a comment to T2510: 1.3 DHCPv6 Ethernet not working.

As required by the DHCPv6 PD function, the IPv6 part seems to be migrated from ISC DHCPv6 to wide-dhcpv6. According to your error log analysis, dhcp6c@eth0 Start failed.

Fri, Jun 5, 7:03 AM
jack9603301 added a comment to T2510: 1.3 DHCPv6 Ethernet not working.

Strange, I didn't test this problem again, but according to the t2449 problem I submitted before, DHCPv6 of IPv6 can get the address and route normally (the route depends on SLAAC). Isn't it ok now?

Fri, Jun 5, 7:02 AM
jack9603301 added a comment to T2510: 1.3 DHCPv6 Ethernet not working.

Where do you configure DHCPv6 PD?

Fri, Jun 5, 4:30 AM
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@dsummers How is it possible, please give a configuration to facilitate others to check (this is a good habit)

Fri, Jun 5, 3:21 AM · VyOS 1.3 Equuleus

Wed, Jun 3

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

When I'm done with the reboot dhcp6c@pppoe0 Another strange problem that may be found after startup failure is that every once in a while, the IPv6 route assigned by DHCPv6 PD will fail, and I can't find the reason yet. Can you help me find the reason?

Wed, Jun 3, 9:43 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Strangely, I found that under my use case dhcp6c@pppoe0 The prefix obtained cannot be routed the next day.

Wed, Jun 3, 4:46 AM · VyOS 1.3 Equuleus

Tue, Jun 2

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po After thinking about it, maybe the only thing I can think of is the word limit of a single line. I submitted another commit.

Tue, Jun 2, 7:59 AM · VyOS 1.3 Equuleus

Sat, May 30

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Please merge the following PR, if there is a problem, please let me modify it.

Sat, May 30, 2:31 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2518: Support nptv6.

If so, it's better to consider porting the 1.2 NPT implementation instead of using a new solution. Can they coexist? I'm just a suggestion.

Sat, May 30, 1:54 PM · VyOS 1.3 Equuleus

Fri, May 29

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

If you think it's possible to delay dhcp6c, I'll start making patches.

Fri, May 29, 4:57 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po @gadams I have a remedy in mind. Can I use the delay command to execute the delay startup in the startup service file?

Fri, May 29, 4:54 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@CRCinAU @c-po I have already submitted a PR, to repair the problems caused by the failure to initialize the interface when it was first loaded after boot, but this completely depends on the automatic restart of systemctl for fault recovery. I don't think this is enough to recover from the failure, but if there is a mechanism and processing, it would be better to postpone it until all interfaces have been initialized.

Fri, May 29, 2:40 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@gadams Is there any way to dynamically increase the dependency list in vyos's current configuration?

Fri, May 29, 2:36 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

There is no error in the configuration itself, and the key is the first boot load when rebooting. In this case, some of the interfaces are not initialized.

Fri, May 29, 2:20 AM · VyOS 1.3 Equuleus

Thu, May 28

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

I've been trying to find the ultimate solution to this problem, and it seems that the best solution is to postpone dhcp6c until the end of all interfaces to start it. Before that. I have done enough testing, and the previous comments in the error log have been released.

Thu, May 28, 9:19 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@jjakob I understand what you mean, so let me explain to you carefully. Over the past two days, I have been trying to find out why the first automatic startup of dhcp6c fails (this is usually due to the automatic call when vyos automatically loads the configuration). At present, the root cause has been determined. I just call dhcp6c manually by the script of vyos, and I also understand this process, but because of the particularity of prefix delegation, such as my case, When pppoe completes the call to execute dhcp6c@pppoe0 execution prefix delegation, I give the prefix to br1 and br2, respectively, which are not created at the startup of their pppoe0 and dhcp6c@pppoe0, so the dhcp6c launcher will fail. I currently have a pudding configuration that when the vyos script manually invokes and starts dhcp6c and fails, it restarts at regular intervals until the service runs or the user stops it manually. But this is far from enough, it only depends on the recovery from the failure of the systemctl startup service to complete the recovery operation. As @gadams said, due to the particularity of dhcp6c's configuration file, when its prefix is delegated, its dependency will change from configuration to change, and its behavior allows it to depend on all interfaces. Therefore, it is a good idea to postpone the startup of dhcp6c to the last call (please note that fault exploration has been completed, the root cause of this failure has been determined, and its temporary patch configuration has been tested in the local environment. Therefore, we can first approve the patch configuration merge, and then discuss the issues related to the postponement of dhcp6c)

Thu, May 28, 9:09 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Of course, if there is a better way to solve this problem, you are welcome to put forward

Thu, May 28, 8:17 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

When using dhcp6c for prefix delegation fetch, it can rely on any interface and should be called after all interfaces have finished starting

Thu, May 28, 8:09 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Because it is impossible to determine the user's dependence on the configuration interface of dhcp6c, the dependency problem has already occurred, which will cause the startup program of dhcp6c to fail after rebooting the system. I have made a patch configuration so that dhcp6c, can be restarted indefinitely in the event of failure, but this is still not the best way. Of course, the best solution may be to postpone the startup priority of dhcp6c.

Thu, May 28, 8:06 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Because I need to recover the fault first, so I made a patch. After all, I don't have a good way to postpone its processing.

Thu, May 28, 7:40 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

I think this problem can consider setting up a new task list and studying how to postpone the processing of this. Fault recovery is usually desirable, but we should not push all possible priority-induced failures to recovery in the fault.

Thu, May 28, 7:39 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

I still think the failure recovery mechanism needs to exist, but I agree with you. I think we should postpone the startup mechanism of dhcp6c until all interfaces have been initialized. A better idea is to execute dhcp6c processing uniformly after all interfaces have been initialized.

Thu, May 28, 7:35 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Please merge this fix.

Thu, May 28, 4:47 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

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

Thu, May 28, 4:47 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

The repair settings take effect on tests in the local environment.

Thu, May 28, 4:37 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@gadams Yes, I thought that since the system CTL automatic restart failed, I might need to write a script to perform the automatic recovery. Now it doesn't seem necessary. I will modify its service file.

Thu, May 28, 4:36 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

OK, I have found the best recovery. I will submit PR immediately. I will modify the service settings of systemctl and use its failure to restart automatically to fix the problem. When dhcp6c service fails to start, it will restart according to the preset settings.

Thu, May 28, 4:35 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

In general, there are several solutions:
a) Add the CLI option of auto repair daemons, and rely on cron to execute the repair program. In case of service failure, the service can be restarted automatically
b) Find the only way to solve the problem thoroughly
Generally, I prefer a + B, so that when the service fails to start in a single time, the daemons can complete the recovery execution.
But it's just an idea. If you have any other suggestions, please let me know.

Thu, May 28, 2:05 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

I try to manually modify the contents of `/etc/ppp/ipv6-up.d/1000-vyos-pppoe-pppoe0 ', and change the following commands:

Thu, May 28, 10:54 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@gadams In my environment, oddly enough, after a reboot dhcp6c@pppoe0 Restart PPPoE 0 by using the vyos command or use systemctl to query and find that the service is manually restarted dhcp6c@pppoe0 Before that, the service was in a failed state and the Restart field of the service did not work. During the configuration loading process after system restart, I cannot make it start normally

Thu, May 28, 5:44 AM · VyOS 1.3 Equuleus

Wed, May 27

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po It has to be said that this is really a troublesome problem. I'm still stuck in fault exploration, rather than making patches. Therefore, there may be some assumptions and verification processes, but it's really troublesome. When the system is restarted, the automatic operation of the service will fail, and I have to restart the service manually.

Wed, May 27, 4:21 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po Strangely, after rebooting the system, I specifically dhcp6c@pppoe0 Query and find that this service is manually restarted by using the vyos command to restart PPPoE 0 or by using systemctl dhcp6c@pppoe0 Before, this service was in failure status, and your Restart field of the service didn't work. I can't make it start normally during the configuration loading process after the system is restarted 。

Wed, May 27, 4:18 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po Trace the problem that the system cannot automatically perform prefix delegation after restarting:

Wed, May 27, 11:36 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po I didn't find out where to call using wide DHCP. I intend to analyze the reason why restart can't automatically start allocating prefix in the 20200523 image.

Wed, May 27, 11:08 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po @gadams In 20200523, I found several bug, although it will not affect my use too much (anyway, it can be restarted). For example, when pppoe is rebooted many times, the prefix will be reassigned, but the old prefix that has been assigned has not been deleted. Although I can keep it working, I still don't know how to solve it. I wonder whether restarting its interface can solve the problem when the current prefix allocation request is restarted.

Wed, May 27, 3:03 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

I will track and test whether the dhcpv6-pd is functioning properly to see if the previous problems still exist in my environment.

Wed, May 27, 2:43 AM · VyOS 1.3 Equuleus

Tue, May 26

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Thank you @c-po. It's very good. I fully understand you. Like you, most of the open-source contributors are amateurs. I don't mean anything else. I think you may have misunderstood my remarks. Please don't be too sensitive. Anyway, thank you. In addition, you can take a look at the comments above and the two questions I raised. I don't know how to solve it for the time being. If you or someone else has a good solution, thank you.
Thanks again

Tue, May 26, 3:24 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

However, there will still be other problems, such as those described in the comments above, and two small problems I have raised. For the moment, I can only guarantee that there will be no py syntax interpretation errors.

Tue, May 26, 2:51 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

I have fixed the following error and submitted PR request for it, but it has not been passed yet.

Tue, May 26, 2:49 PM · VyOS 1.3 Equuleus
jack9603301 created T2518: Support nptv6.
Tue, May 26, 1:30 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

it will be converted by some CPE to regular old ethernet,

Tue, May 26, 7:38 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@gadams Therefore, in order to use SLAAC and DHCPv6 PD in this case, the router needs to receive RA from the superior router or CPE device in this case?

Tue, May 26, 6:58 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Come on, I think I've got a patch for py error reporting ready before @c-po. I'll launch PR directly.

Tue, May 26, 5:39 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

I should note that in setups for some very large ISPs in the US, and probably elsewhere, there is no need for a DHCPv6 client at all, except for doing DHCPv6-PD. The directly-connected IPv6 network gets its assignment via RA, and IPv4 addresses may be assigned statically.

Tue, May 26, 4:19 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Strange, in my environment, delegation requests are successful when PPPoE is used for dialing. When setting delegation on the non PPPoE interface, do you need the superior router to set DHCPv6 PD delegation and issue operations on the interface (this is not required here, I mainly obtain prefix delegation when ISP dials PPPoE)?

Tue, May 26, 4:07 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@gadams I am ready to fix the following problems. If @c-po doesn't understand what happened and solve it, I may submit PR request.

Tue, May 26, 4:03 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T1059: Support receiving IPv6 router advertisements.

You can consider submitting a PR request in a rolling branch that has requested a merge.

Tue, May 26, 3:55 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-EPA3)
jack9603301 added a comment to T1059: Support receiving IPv6 router advertisements.
Tue, May 26, 3:54 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-EPA3)
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

However, no prefix delegation request appears to be sent and no configuration of delegated interfaces appears to be done. Indeed, no dhcp client appears to be running.

Tue, May 26, 3:38 AM · VyOS 1.3 Equuleus

Mon, May 25

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Usually this bug should reopen a bug report. The project management system can create sub-projects, and you can usually consider opening a sub-project.

Mon, May 25, 9:49 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Of course, for the time being, I can only solve the specific code errors introduced by @c-po. Above, I have raised some of the existing minor problems of using delegation in pppoe. I think I may not know how to solve this problem for the time being. If you have this ability, you can consider solving it.

Mon, May 25, 9:46 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@gadams With regard to this question, I have specifically read the submission record of @c-po, and I think I have found out where the possible errors are (please read my comments above). Of course, I expect @ c-po to solve the errors introduced by itself, because it seems very simple, if the problem @c-po is not resolved for a long time, I may consider submitting a pr request.

Mon, May 25, 9:42 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

This work is done by @c-po, but according to my experiment, the current scrolling version is a 20200523 image, and dhcpv6-pd works basically fine in my ISP environment. But there may be some minor problems. Please read the comments on this list.

Mon, May 25, 8:37 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

What does it mean? I'm sorry, I may not understand.

Mon, May 25, 8:21 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

In addition, please pay attention to the previous question of another user feedback. I have read the relevant code you submitted, and you may have written it wrong.

Mon, May 25, 6:12 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

a) I know it's not supposed to be like this, but it does show up with me.

Mon, May 25, 6:08 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po In addition, I also feedback several questions (if this is not a problem, please tell me the correct understanding and use):

Mon, May 25, 5:27 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.
if eth['dhcpv6_pd']:
    e.dhcp.v6.options['dhcpv6_pd'] = e['dhcpv6_pd']
Mon, May 25, 4:50 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Prefix delegation is a very important function, which needs to be used to provide routable prefix segment allocation to users.

Mon, May 25, 3:54 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

You can download 20200523 and later scrolling images to use this feature

Mon, May 25, 3:52 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Dhcpv6-pd can be used normally at present, and it works well in my ISP.

Mon, May 25, 3:51 AM · VyOS 1.3 Equuleus

Sun, May 24

jack9603301 added a comment to T2506: DHCPv6-PD add prefix hint CLI option.

If this field is only the len, of prefix, there is no need to use prefix writing.

Sun, May 24, 8:49 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Thank you. Finally, RA was able to set and distribute all the new IPv6 64bits prefixes with the following instructions:

Sun, May 24, 9:18 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po At present, through DHCPv6 PD, IP can be obtained on the bridge, but cannot be distributed to the client through SLAAC. Is it my configuration error?

Sun, May 24, 7:21 AM · VyOS 1.3 Equuleus

Sat, May 23

jack9603301 updated subscribers of T2502: PPPoE default route not installed for IPv6 when "default-route auto".

@jjakob @c-po Execute the following command. Although the default route can be generated automatically, it may be a bug in the current PPPoE function. In a specific environment, restarting PPPoE dialing will not maintain dialing status!
set interfaces pppoe pppoe0 default-route force
Restart PPPoE dial command as follows:
disconnect interface pppoe0
connect interface pppoe0
Executing the above restart dialing command, a strange thing will happen, that is, the acquired IP cannot be reserved, and the dialing will be restarted continuously. I know that this problem may only occur in a specific environment, so the official recurrence is very difficult. Through the analysis of examples, I think the only valuable problem is the generation of a signal 15!

Sat, May 23, 5:07 PM · VyOS 1.3 Equuleus

Thu, May 21

jack9603301 added a comment to T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone.

Although I wanted to try it out, it seems the best way is to try to upgrade to the latest stable version. From the perspective of version management, the higher version often fixes some existing bugs, while the stable version ensures sufficient testing to avoid 0days.

Thu, May 21, 12:17 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone.

@jjakob I'm sorry, but I think you may have misunderstood me. I just summarized the problems that can be solved at present. Of course, this patch can finally be submitted to PDNS. Relatively speaking, the current solution to the problem may be the first priority, and there are only two main ways to solve the problem, either to solve it or to bypass it.

Thu, May 21, 11:41 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone.

I can summarize the following solutions, and maybe there are other solutions:
a) Fix the bug yourself
b) Use other storage mechanisms to resolve records to bypass
c) Self parsing hosts

Thu, May 21, 11:32 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone.

Alas, it's really a troublesome problem. If it's a bug, I haven't used pdns-recursor. I usually use ISC bind, but I have a solution different from the one you put forward. It is based on the independent maintenance of open source branches, looking for the code with problems and implementing the patch. @jjakob

Thu, May 21, 11:25 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone.

You mean that when pdns-recursor recursively forwards the request to the back-end recursive parsing service, the static entries in the query / etc / hosts will always return NXDOMAIN?

Thu, May 21, 11:00 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone.

via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone

Thu, May 21, 10:17 AM · VyOS 1.3 Equuleus

Wed, May 20

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

in full agreement

Wed, May 20, 10:48 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.
In T421#64197, @jjakob wrote:

That's a case where having the ability to assign addreses from the received prefix via DHCPv6 on the internal interface would allow internal hosts to get managed addresses from the prefix automatically without the use of NPT or SLAAC. But that isn't implemented yet AFAIK.

Wed, May 20, 10:32 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Even if dhcpv6-pd is now supported, nptv6 may still be needed, and as a user's choice, the application user may need to use the ula address. In particular, if you do not use ula addresses, in some environments, users may not be able to obtain fixed address prefixes, and when users need internal IPv6 address prefixes that can only be assigned by themselves, NPT may be necessary.

Wed, May 20, 9:52 AM · VyOS 1.3 Equuleus

Tue, May 19

jack9603301 added a comment to T2380: After PPPoE 0 is restarted, the default static route is lost.

No one to follow up? I know this problem may be strange, but it does happen to me!

Tue, May 19, 2:44 PM · VyOS 1.3 Equuleus

Mon, May 18

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.
In T421#63999, @Azayaka wrote:

@c-po What did you want? Configuration of DHCPv6 PD in vyos?? Didn't you update the document? How do you configure it?? I don't quite understand!

Please...This is just embarrassing. This comment might be off-topic, but it looks like our fellow Chinese user @jack9603301 need suggestions on how to use English in a proper manner. (Your current wording style can easily offend people.)
Here are my wording suggestions.

  • Avoid double or tripple question marks.
  • Avoid rhetorical questions.
  • Use "Sorry", "Please", "Could you...", etc. for questions and requests.
  • Avoid representing others if you are not entitled. For example, when *you* want some features, do not say "VyOS fans in China" want those features.

I can translated my points to Chinese if it can be better understood.
雖然你可能沒有意識到,但是你的英語行文很不禮貌,容易冒犯他人。以下是我的幾點建議:

  • 避免使用多個問號。
  • 避免反問他人。在中文語境下,反問也可以被認為是想吵架。
  • 多用 "Sorry", "Please", "Could you..." 這種緩和語氣、表示禮貌的詞彙,特別是在提問或請求他人的時候。
  • 不要輕易“代表”他人。
Mon, May 18, 9:25 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.
In T421#63999, @Azayaka wrote:

@c-po What did you want? Configuration of DHCPv6 PD in vyos?? Didn't you update the document? How do you configure it?? I don't quite understand!

Please...This is just embarrassing. This comment might be off-topic, but it looks like our fellow Chinese user @jack9603301 need suggestions on how to use English in a proper manner. (Your current wording style can easily offend people.)
Here are my wording suggestions.

  • Avoid double or tripple question marks.
  • Avoid rhetorical questions.
  • Use "Sorry", "Please", "Could you...", etc. for questions and requests.
  • Avoid representing others if you are not entitled. For example, when *you* want some features, do not say "VyOS fans in China" want those features.

I can translated my points to Chinese if it can be better understood.
雖然你可能沒有意識到,但是你的英語行文很不禮貌,容易冒犯他人。以下是我的幾點建議:

  • 避免使用多個問號。
  • 避免反問他人。在中文語境下,反問也可以被認為是想吵架。
  • 多用 "Sorry", "Please", "Could you..." 這種緩和語氣、表示禮貌的詞彙,特別是在提問或請求他人的時候。
  • 不要輕易“代表”他人。
Mon, May 18, 8:16 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

@c-po What did you want? Configuration of DHCPv6 PD in vyos?? Didn't you update the document? How do you configure it?? I don't quite understand!

Mon, May 18, 3:30 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.

Great, dhcpv6-pd is finally coming true!

Mon, May 18, 11:14 AM · VyOS 1.3 Equuleus

Sat, May 16

jack9603301 added a comment to T421: VyOS lacks DHCPv6-PD (Prefix delegation) length / IA_PD support.
In T421#63876, @Azayaka wrote:

Damn, I am so embarrassed by @jack9603301. From the avatar to the naive, rude comments... looks like a troll XD.
Another problem of the EdgeRouter-style configuration is that only one PD is possible at a time. Cisco IOS uses the concept of dhcp pool and pd name-tag to deal with multiple PDs (a possible scenario: 2 PDs from 2 different ISPs for redundancy). Not sure if it can be supported by dhclient though.
I prefer the IOS style, and here is an example.

ipv6 dhcp pool POOL-v6
 dns-server 2001:4860:4860::8888
interface GigabitEthernet0/0/0
 ipv6 address autoconfig default
 ipv6 enable
 ipv6 nd ra suppress all
 ipv6 dhcp client pd ISP-name
 ipv6 virtual-reassembly in
interface Vlan1
 ipv6 enable
 ipv6 address ISP-name ::1/64
 ipv6 nd other-config-flag
 ipv6 nd ra interval 180
 ipv6 dhcp server POOL-v6 rapid-commit
Sat, May 16, 6:09 PM · VyOS 1.3 Equuleus

Thu, May 14

jack9603301 awarded T2023: Add support for 802.1ae MACsec a Like token.
Thu, May 14, 1:59 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2380: After PPPoE 0 is restarted, the default static route is lost.

@jjakob @c-po Execute the following command. Although the default route can be generated automatically, it may be a bug in the current PPPoE function. In a specific environment, restarting PPPoE dialing will not maintain dialing status!

Thu, May 14, 12:17 PM · VyOS 1.3 Equuleus

Wed, May 13

jack9603301 lowered the priority of T2380: After PPPoE 0 is restarted, the default static route is lost from High to Normal.
Wed, May 13, 6:08 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2380: After PPPoE 0 is restarted, the default static route is lost.

I suspect that the problem has been found, but after I executed the restart PPPoE command, the default travel was lost. My configuration name wrote the following static route:

Wed, May 13, 5:57 PM · VyOS 1.3 Equuleus
jack9603301 renamed T2380: After PPPoE 0 is restarted, the default static route is lost from After setting PPPoE to obtain IPv6 from ISP, you must restart the system to take effect to After PPPoE 0 is restarted, the default static route is lost.
Wed, May 13, 5:55 PM · VyOS 1.3 Equuleus
jack9603301 awarded T118: Native Zabbix Support a Like token.
Wed, May 13, 4:01 PM · VyOS 1.3 Equuleus
jack9603301 awarded T365: OVS as replacement of Linux bridge a Like token.
Wed, May 13, 3:59 PM · VyOS 1.3 Equuleus
jack9603301 awarded T1797: Implement DPDK Fast-Path using FRR's Alternate Forwarding Planes and VPP a Like token.
Wed, May 13, 3:58 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2380: After PPPoE 0 is restarted, the default static route is lost.

There are still some problems about IPv6, even when I restart it, I can't get IPv6 immediately. I don't know when it has some impact on my ISP environment, but it may be a bug that is hard to find. In a previous version of 1.2, IPv6 was acquired normally. Is it necessary for the official to cross compare with the latest version of 1.2.3? (may be 1.2.3, I hope I remember correctly)

Wed, May 13, 12:02 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2380: After PPPoE 0 is restarted, the default static route is lost.

How does vyos timeout PPPoE?

Wed, May 13, 11:48 AM · VyOS 1.3 Equuleus

Mon, May 11

jack9603301 added a comment to T2449: 'ipv6 address autoconf' and 'address dhcpv6' don't work because interfaces have accept_ra=1 (they should have accept_ra=2 when forwarding=1).

My vyos2 virtual machine can only get a 128 prefix address without routing. What's the matter?

Mon, May 11, 1:06 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2449: 'ipv6 address autoconf' and 'address dhcpv6' don't work because interfaces have accept_ra=1 (they should have accept_ra=2 when forwarding=1).

Let me see if it works from the vyos2 virtual machine

Mon, May 11, 12:42 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2449: 'ipv6 address autoconf' and 'address dhcpv6' don't work because interfaces have accept_ra=1 (they should have accept_ra=2 when forwarding=1).

The configuration mode executes show service router advert result:

Mon, May 11, 11:22 AM · VyOS 1.3 Equuleus
jack9603301 updated the task description for T2449: 'ipv6 address autoconf' and 'address dhcpv6' don't work because interfaces have accept_ra=1 (they should have accept_ra=2 when forwarding=1).
Mon, May 11, 8:19 AM · VyOS 1.3 Equuleus
jack9603301 created T2449: 'ipv6 address autoconf' and 'address dhcpv6' don't work because interfaces have accept_ra=1 (they should have accept_ra=2 when forwarding=1).
Mon, May 11, 8:18 AM · VyOS 1.3 Equuleus

Sun, May 10

jack9603301 closed T2439: Configuration dependency problem, unable to load complex configuration after reboot as Resolved.
Sun, May 10, 2:46 AM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2439: Configuration dependency problem, unable to load complex configuration after reboot.

Test problem solved

Sun, May 10, 2:46 AM · VyOS 1.3 Equuleus

Fri, May 8

jack9603301 added a comment to T2439: Configuration dependency problem, unable to load complex configuration after reboot.

After relevant tests, it is highly suspected that the configuration dependency problem can be solved by manually loading the following instructions:

Fri, May 8, 1:28 PM · VyOS 1.3 Equuleus
jack9603301 added a comment to T2439: Configuration dependency problem, unable to load complex configuration after reboot.

Because the problem is that in the process of loading config.boot after the vyos system is restarted, the configuration dependency of the sequential application configuration is not considered, so the accurate error reporting information cannot be provided. You can use the above configuration structure to reproduce.

Fri, May 8, 1:26 PM · VyOS 1.3 Equuleus