Delete set interfaces pppoe pppoe0 no-default-route will let it works. it is the same issue.

In T6140#180604, @Apachez wrote:

Also since dynamic and not static IP is being used it would be handy if the DHCP exchange can be captured using tcpdump and do this both on the 1.3 where this works and on 1.4/1.5 where this doesnt work.

This way we can find out what the difference is in the request flow (from the client) but also in the response flow (from the server) - in case DHCP would be to be blamed on this behaviour.

In T6140#180242, @pepe wrote:

Show this commands output if that happens:

show interfaces pppoe pppoe0
show ip route
show log pppoe

Show performance test results from versions 1.3 and 1.4

https://forum.vyos.io/t/static-routes-not-working-with-pppoe-and-vyos-1-4/14102

Can we let local-route support group options both in destination and source ?

set policy local-route rule 10 destination
Possible completions:
+  address              IPv4 address or prefix
   port                 Port number used by connection

Would you please backport this feature to VyOS 1.3.x?

VyOS 1.3.3 Still have such an issue. Any plan to fix it on VyOS 1.3?

why don't we chang unbound to coredns ? Coredns will be more stronger thant unbound.

In T125#51628, @Dmitry wrote:

I propose in this case use set vpn l2tp remote-access outside-address 0.0.0.0. It works in current rolling.

In T2036#53376, @c-po wrote:

Hello @dongjunbo what are the benefits of ocserv over the other VPN Solutions already in place?

• WireGuard
• OpenVPN
• L2TP/IPSec
• PPTP
• SSTP
• IKEv2 road warrior (not yet implemented, only site2site)

@sync Is that possible merge it to vyos mainline ?

@TriJetScud @syncer We really need this feature to replace pfsense with vyos in our production environment.

@TriJetScud Would please make it works on vyos latest version ?

@TriJetScud How about this feature request? Will it works on vyos 1.3 ?

In T1376#38816, @zsdc wrote:

In T1416#38750, @dongjunbo wrote:

Seem like static counting still not right

@dongjunbo, show please the configuration of this router so we could check why gcdomestic pool does not count correctly.

Dear， Developers
Seem like the bug still there in vyos 1.2.3 release version

@jjakob @syncer @cpopa Is that possible to let vyos support to do dyn-dns hostnames from dhcp to windows dns server in an active directory environment?

In T1416#38770, @jjakob wrote:

I think this is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810971
Fixed in isc-dhcp 4.3.4-1 so pulling in newer isc-dhcp should fix it.

@dongjunbo I don't understand the question. If you mean hostname and IP sync for DHCP leases, then yes, it should already do that via failover (except for hostname sync, which should work but doesn't due to this bug). Vyos uses isc-dhcp, so whatever it supports can be done in vyos (read isc-dhcp version 4.3.1 documentation).

As for the show statistics bug, please open a separate task and provide some more info (most useful would be /config/dhcpd.leases so we can test the code locally).
I think show_dhcp.py could do with some overhaul in the spirit of my recent show_dhcpv6.py additions, with better handling of different lease states etc.

Another request: Is that easy to may host-update sync hostname and ip address with 2 vyos ?

In T1416#38611, @zsdc wrote:

Hello, @dongjunbo!
Have you tried current rolling releases to check if leases information view work correctly now?

Seem like static counting still not right

display dhcp lease should works, right?
How about dhcp work in failover mode. Should 2 dhcp server got hostname and sync match of hostname and ip address in 2 vyos ?

In T1416#37376, @c-po wrote:

Unfortunately this was a miss understanding between @zsdc and me, but the provided fix targeted the same direction.

In T1416#37304, @c-po wrote:

Please test and verify with latest rolling

Seem like this issue still in vyos 1.2. Would please check it and fix it ?

I met this issue before. But I can save firewall group to a txt then use ipset to load the firewall groups when system boot. It works well. Vyos boot quickly and firewall policy updated well.

Hi, @rob
It works! Thanks a lot. This case can be closed now.

I met the same prolem with vyos 1.2.0. EPA2

Sorry, It's my cable was broken.

No ISP problems. Vyos always has the problem that when i install a new vyos on a server with a intel network adapter which has 4 ports. Every time i need to change the mac address of each network interface. I'm sure it's a bug that got the wrong mac address of each interface(eth0-eth4, not pppope interface).

Dear, Hagbard
Seem like that i found the problem that mac address of each interfaces had been switched randomly after upgrade rc7 to rc8.

Sorry. When i upgrade rc7 to rc9 is okay. but when i reboot to rc8 and then reboot to rc9. it failed again.

In T1031#26684, @hagbard wrote:

@dongjunbo Perfect. So it looks like that you have a valid ppp session established (session id 0x5d58). Does 'sudo ip sh a' show you a ppp0 interface or something similar? I tested the ppp client shipped in rc7 and rc8 and it appears it works as expected, so we need to find out what's going wrong on your side.

If you want to me run the command on rc8, I need to do it on Monday. Because When i reboot it. my lan connect to vyos will be lost.

Sorry for late responding.
I run the command on vyos 1.2 rc7 :
Here are the output:

In T1031#26490, @syncer wrote:

@hagbard it's not really about server, but about client
wondering if we may need ppp for client part