- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 17 2024
Sample config files here: https://github.com/networkupstools/nut/tree/master/conf
I think there are actually two aspects here.
Sure. I did some further testing and it looks like this is triggered if the client sends DHCP option 81 (FQDN). To reproduce:
Which user are you expecting? Hows to check from which user container was started?
Any idea for CLI?
1.4.0-rc2 also has opennhrp service stop after vyos startup. Can you please add a 1.4 tag to this issue?
@Daya @trae32566 Is it not the issue anymore?
I'd tag it as wontfix
Domain name was never configured for FRR in our templates
r4# conf t r4(config)# domainname WORD This system's domain name r4(config)#
Fixed for both VyOS 1.5-rolling-202401140026 and VyOS 1.4.0-rc2
@Nova_Logic Describe what exactly you want to do
Policy and firewalling are possible now
vyos@r4# set firewall ipv4 input filter rule 10 inbound-interface name eth1.v10 [edit] vyos@r4# set policy route foo interface eth1.v10 [edit] vyos@r4#
Personally I would prefer that the "automagic" firewall ruleset would be done optionally through method described in:
Good practise add a set of the commands to reproduce
Thanks
I've found some time to do some work on a fork of vyos-1x. I have a working patch to 1.5-rolling that does the following:
I am facing same issue here.
In my case, My laptop hostname is cn002472.xxx.com
Jan 16 2024
With 1.4.0-rc1 All OK, came up on reboot:
Jan 15 2024
Working on latest 1.4! 👍
Working on latest 1.4. 👍
It will be included after 1.4-rc2
In T5247#166517, @SrividyaA wrote:Now we receive this error in 1.5-rolling-202312060024 when the command is executed:
vyos@R1:~$ show interfaces system -vbash: /opt/vyatta/bin/vyatta-show-interfaces: No such file or directory
Just wanted to add that this error is also present in V1.4 RC1
Create a new feature request if you need some specific feature/features
For example, for offloads we use:
vyos@r4# set interfaces ethernet eth0 offload Possible completions: gro Enable Generic Receive Offload gso Enable Generic Segmentation Offload hw-tc-offload Enable Hardware Flow Offload lro Enable Large Receive Offload rfs Enable Receive Flow Steering rps Enable Receive Packet Steering sg Enable Scatter-Gather tso Enable TCP Segmentation Offloading
I was unable to duplicate the behavior with 1.4.0-rc1. Performed add system image https://cdn.vyos.io/1.4.0-rc1/vyos-1.4.0-rc1-amd64.iso) with above configuration, and nhrp came up on reboot. So it's common to 1.4 and 1.5, but only since sometime in December (post rc1)?
Removed
Merged
With the same config:
I'm seeing this on 1.4 as well, dockerized build 1.4-rolling-202401061915), configured following https://docs.vyos.io/en/sagitta/configuration/vpn/dmvpn.html with no other protocols/services.
Jan 14 2024
Can confirm, short term testing worked.
Oops, I didn't see T5647! Sorry! I guess this one can be closed as a duplicate.
Do static addresses/gateways work stable enough?
100% agree. I have submitted a similar feature request here:
In T5835#171322, @Viacheslav wrote:Another bug it that /config/upnp.leases is hardcoded, but there is no script who creates it https://github.com/vyos/vyos-1x/blob/aebb458262072457c6a3840d1b17031fbd780eca/data/templates/firewall/upnpd.conf.j2#L128
It cause of
Jan 10 21:16:03 r4 miniupnpd[9869]: Reloading rules from lease file Jan 10 21:16:03 r4 miniupnpd[9869]: could not open lease file: /config/upnp.leases
Did some more work on this.
Jan 13 2024
Hello, this task has a bug. Do I open a new task or comment here?
I've made some progress. I've been able to get miniupnpd to stop generating the mnl_cb_run() errors. It was as assumed; the lack of nft table / chains.