I think its outside our scope. vyos is a network appliance. it provides services to transfer network traffic or services essential to transfer traffic (dns, dhcp). nfs does touch this aspect at all. Neighter would a radius service but that would enable pppoe-server or hostapd,... to move traffic. Nfs is not a requirement for any deamon to move traffic. ergo outside thhe scope.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 21 2016
Apr 19 2016
Could you give an example of an use-case? Because I think this choice was very much by-design.
Apr 13 2016
Can you make new tasks be assigned into some group 'triage' as for questions now is. The groups for questions should be kept simple as NAT, PBR, WLB, OPENVPN, IPSEC, DRIVER, KERNEL, ... because users will mostly interact with this part.
Apr 10 2016
Apr 9 2016
I ran the scenario 'on a stick' and was unable to reproduce. Please post more debug output using the commands described earlier.
recap from irc: one fix would be to negate the vpn-subnet in the source part of your dnat rule.
It will be possible once you can set the fail-over listen/target port. The problem is that it tries to listen on the same port using multiple sockets (if my memory is correct).
Apr 2 2016
Apr 1 2016
How about making firewall groups IPvAgnostic and have VyOS figure out which the correct IPvN is (depending on where you use it) in a somewhat systematic way. In FW it would be both in parallel, etc. The user would still be able to setup groups per IPvN as-is currently.
Mar 30 2016
I'm haven't looked into it but since I failovered my setup I have:
Mar 21 2016
I haven't been able to reproduce so far. The only difference would be I've used two seperate interfaces instead of 'on-a-stick', I don't think this should matter but will run on-a-stick tomorrow. Is there any NAT involved in your setup?
Mar 19 2016
By duplicate address detection you mean (examples cases):
- eth0 address 192.168.1.1/24 and eth0 address 192.168.1.1/25
- as 1) but between eth0 and eth1
- duplicate IP address on connected segment of interface (you share an IP with another node)
- as 3) but with all connected-segments
- as 4) but additionally in connected routes unique
Can you deploy the advanced ova on free products? Because iirc there are some restraints (eg. single node ESXi)?