vyos@nat-lb-july# run show config comm | grep nat set nat destination rule 10 destination port '443' set nat destination rule 10 inbound-interface 'eth3' set nat destination rule 10 protocol 'tcp' set nat destination rule 10 translation load-balance mode 'round-robin' set nat destination rule 10 translation load-balance translation-address 1.1.1.1 hash-value '0' set nat destination rule 10 translation load-balance translation-address 2.2.2.2 hash-value '1' set nat destination rule 10 translation load-balance translation-address 3.3.3.3 hash-value '2' set nat destination rule 10 translation load-balance upper-limit '3' set nat destination rule 20 destination port '53' set nat destination rule 20 inbound-interface 'eth3' set nat destination rule 20 protocol 'udp' set nat destination rule 20 translation load-balance mode 'random' set nat destination rule 20 translation load-balance translation-address 1.1.1.1 hash-value '0-24' set nat destination rule 20 translation load-balance translation-address 2.2.2.2 hash-value '25-49' set nat destination rule 20 translation load-balance translation-address 3.3.3.3 hash-value '50-99' set nat destination rule 20 translation load-balance upper-limit '100' set system host-name 'nat-lb-july' [edit]
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 21 2023
Proposed syntax one of them
set system option time-format 12|24 set system option time-format 12-hour|24-hour set system option time-format us|gb
Actually, it should configure:
sudo localectl set-locale LC_TIME="en_GB.UTF-8" sudo localectl set-locale LC_TIME="en_US.UTF-8"
Hmm, fair enough. Maybe just executing the stop script and then committing set high-availability disable is enough for maintenance periods.
One general question though out of curiosity: What are the circumstances in which the stop script is executed in the first place?
PR for 1.3: https://github.com/vyos/vyos-1x/pull/2106
Maybe it is the wrong way. I think it shouldn't touch anything in the disable state.
To reproduce the problem:
PR https://github.com/vyos/vyos-1x/pull/2105
set system sflow interface 'eth0' set system sflow interface 'eth1' set system sflow server 127.0.0.1
Jul 20 2023
- I want to have something like minikube on my VyOS router joining my k8s with my services so data is replicated and I can "balance" the services to my home.
- Coming from my R&D journey of https://causal-rt.org I'm trying to further rethink a few things including social networking, one goal would be to get a communication service for "convergent/consent-forging human swarm interaction" https://dory-swarm.org onto the edge, rather than relying on central or semi-decentral services for relaying communication.
That is challenging task :)
What is your goal?
I think this feature must then be modified with:
no it's the PPPOE server configuration
Actualy is just exports TMOUT option per login
In T5364#153398, @troggie wrote:In T5364#153397, @Viacheslav wrote:I'm wondering about the syntax
Will it be enough?set service pppoe-server pado-delay 0I think we should include the sessions incase there multiple PPPOE services and people want to spread the load across multiple devices?
Or maybe an option to allow without sessions as well as allow with sessions - make the system versatile ?
Tested in the latest rolling release with both ipsec configured as tunnel and transport mode . As suggested in the above comment, with the correct close-action setting configured in both the initiator and responder side, then no duplicate child_sa are noticed.
In T5364#153397, @Viacheslav wrote:I'm wondering about the syntax
Will it be enough?set service pppoe-server pado-delay 0
I'm wondering about the syntax
Will it be enough?
set service pppoe-server pado-delay 0
Will be fixed in the next rolling release.
Oh ok.
In T5363#153177, @Apachez wrote:I think this should be configured through a config option if bash-history should be retained or not (by default it shouldnt for regular users and equal to root).
It can for security reasons be argued that history should only exist in current session but when user logs out it should be removed.
This way in a multiuser environment one user cannot steal potential sensitive data from another user.
If security logging (what a particular user have done to the system when logged in) is needed this should be done remotely through syslog or similar.
Dear Viacheslav
Can I get compiled binary suitable for dell VEP4600 wich will retain the bash history.
I can confirm by removing the incorrect update-check url like so:
Ooh, I thought update-check should point to the iso-file like so:
Something wrong with this template https://github.com/vyos/vyos-1x/blob/d2540ac4c6fc05991b18cf0e2434fbb6d5f3c2cf/data/templates/lldp/vyos.conf.j2#L7
It should be configurable as an option but not by default.
It is not fully implemented.
You have to set the URL to a JSON file with System versions, which not exists for now (there is no permanent URL for it), so it will be in the future developments.
FRR does not support it
Allows only full multicast table
r11# clear ip ... mroute IP multicast routing table
Just want to jump onto the train and say that I too like the proposal of having "lo" as the main linux kernel loopback and loN as the networking loopback who is VRF-aware aswell.
Jul 19 2023
I have experienced this myself several years ago where "Green Ethernet" aka "Energy-Efficient Ethernet mode" was the cause that HPE Comware switches/routers had issues with cable based Apple devices.
This could be considred as duplicate task for: https://vyos.dev/T5116
Changes on documentation don't need a task here.
Already fixed:
https://vyos.dev/T5340