Many thanks. I think it was actually fixed earlier than 1.3.7 - I've been using VRF to allow SSH access only from a separate private management network, on a router that routes only public IP addresses (BGP, OSPF, PPPoE) otherwise, since about 1.3.5 or so.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
May 13 2024
Thanks for the comment! I'm responding on the github page so we aren't in two places at once.
As already commented in the PR itself:
Hard agree with the points Apachez made above, the packages should be added. I tried adding the packages to vyos-1x/debian/control and vyos-build/data/live-build-config/archives/trixie.list.chroot + vyos-build/data/live-build-config/archives/trixie.pref.chroot without any luck. Perhaps it was an issue with my docker setup or something similarly silly (I am very new to VyOS) but I am not sure how to add these packages. Any ideas?
@dmbaturin, I propose removal of upnp stuff from 1.5 and 1.4
(commenting as the root cause of this issue ;) While one could argue that you could configure the other FRR not to use multi-topology, some devices might use IS-IS multi-topology as the default setting, so it would be nice to have it tunable.
The original feature/bug is solved
The stop script executed is executing.
The locks are a separate task/bug.
I changed the stop script to this:
#!/bin/vbash
Any update on this PR? (thanks for the work put into this!!)
Since some of the required children are other node or tagnode types I belive it would be better to change the schema to the following:
Checking a recent 1.5 build (1.5-rolling-202405090225), I do not see the discrepancy mentioned in the description: the result for 1.5 is also (just) missing vif entries, and one can observe that the syntax error in vif 2 causes cascading syntax errors in the other vif sections.
The following script recreates the effect of the XorpConfigParser:
May 12 2024
This PR merged. Closing the issue