I believe I resolved his issue, but I'm no longer at that location and don't have the same set up, but I do recall being able to access the cable modem.

show ports local <--- show opened ports on a local host

@lbv2rus Can you re-test it on VyOS 1.4?

I've just testd 40+ policies (with 40+ dedicated routing tables) on VyOS 1.4 - everything works fine.

The WPA-EAP for wireless station mode is feature is implemented in T6496.

@c-po, can you see if it's still actual, and if not, close it
Thanks!

@dmbaturin can you take a look and close if it's obsolete?

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

@a.apostoliuk this one should be resolved in the current rolling release, if you're able to check it out?

I've created a PR for this that fixed a mistake with my original patch: https://github.com/vyos/vyos-1x/pull/3570

We will bind the code to a new command in operating mode (for example show ports). This will allow you to use the nmap command from operating mode. Just a convenient feature.

Just dont, please see my comment fro april 2024.

@sever what about it?

New source release, not in Debian yet: https://github.com/acassen/keepalived/releases/tag/v2.3.1

As far as I can tell the test will always error if the remote matches and neither source-interface and source-address are configured differently, including the case where they're both blank (source-interface == None on both tunnels triggers this particular case).

Yes, @c-po that would be a reasonable explanation; the timeout was added for Equuleus by 1.3.4. Without a reporting user to ask; other reports on later version; or further information, I would vote to close ...

@jestabro It was a report from the user; unfortunately, I do not have more details.

I remember there was an ancient bug where the commit-archive rewrite did not come with a timeout. As routing might not have been converged during boot, that could explain the lock.

Naive attempts to reproduce on 1.3.3 are not successful, yet (Vmware; KVM), but will continue to investigate; any other information is welcome @Viacheslav, should you recall ...

I can't test it in 1.3. I've tried to build the latest 1.3 from repository, but it looks like the build process is broken and does not allow contributors to build following the documentation guide any more.
That's sad :(

@jestabro assigning to you but feel free to pass it to another team member

This is a known issue as explained in detail in T4628. You're best choice is to remove the whitespace prior to upgrading. Thanks for reporting this anyways!