Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "update. \nyes procedure works as specified. one thing to remember is to add ssh key before vm gets deployed.", "name": "", "is_accepted": true } ]

[ { "text": "maybe do you mean 1.2.8?\n\nthis is bug described here [⚓ t3671 webproxy not functional in 1.2.8 update](https://phabricator.vyos.net/t3671)\n\nyou can find a .deb pkg, which you can to install for the fix.\n\ncan you check it?", "name": "", "is_accepted": true } ]

[ { "text": "i install the latest one, now working well, thanks!", "name": "", "is_accepted": true } ]

[ { "text": "the issue was resolved, it seemed to be an issue with my nacl where we had just allowed tcp on all ports rather than allowing udp too. thanks [@viacheslav](/u/viacheslav) for your support.", "name": "", "is_accepted": true } ]

[ { "text": "just as an fyi i was referring to the part in the user guide link that says:\n\n“when you set burst for parent class smaller than for some child then you should expect the parent class to get stuck sometimes (because child will drain more than parent can handle). htb will remember these negative bur…", "name": "", "is_accepted": true } ]

[ { "text": "i’m going to implement <https://phabricator.vyos.net/t1705> today for rolling.", "name": "", "is_accepted": true } ]

[ { "text": "yes - you’re right!\n\ni deleted the existing nat entry (which had outbound-interface set to eth0), and re-created it using pppoe0:\n\nset nat source rule 100 outbound-interface 'pppoe0'\n\nset nat source rule 100 source address '10.5.1.0/24'\n\nset nat source rule 100 translation address masquerade\n\nthank yo…", "name": "", "is_accepted": true } ]

[ { "text": "as dhcp packets bypass iptables, you can’t block those packets with iptables rules.\n\nto see what goes on:\n\nrun tcpdump sniffer on lan, filtered on dhcp ports\n\nand at the same time, use iptables allow rules for dhcp traffic, and enable logging on those rules.\n\nthen compare outputs", "name": "", "is_accepted": true } ]

[ { "text": "you can replace your named private key.\n\nvyos@r4-roll# run generate wireguard named-keypairs foo\n\n[edit]\n\nvyos@r4-roll#\n\n[edit]\n\nvyos@r4-roll# ls /config/auth/wireguard/foo/\n\nprivate.key public.key\n\nvyos@r4-roll# set interfaces wireguard wg0 private-key\n\npossible completions:\n\n<text> private ke…", "name": "", "is_accepted": true } ]

[ { "text": "ok, so i found the problem. using a vm, even on another network, after a few tries i was able to load dhcp. when loading the config.boot manually i saw an error with one static-mapping entry which mac-address was 0:0:0:1:1:1.\n\ni guess i have been expecting for the printer owner to send me the corre…", "name": "", "is_accepted": true } ]

[ { "text": "there is only one path\n\nis upgrade to 1.2\n\n1.1.x will not be updated", "name": "", "is_accepted": true } ]

[ { "text": "[image] mpsl:\n\noperation not permitted\n\nthese message generate firewall.", "name": "", "is_accepted": true } ]

[ { "text": "this has been fixed by commit <https://github.com/vyos/vyos-build/commit/290976bd7775986ff48661088c74b01c4cc82f12>\n\nplease update your local vyos-build repository.", "name": "", "is_accepted": true } ]

[ { "text": "i tested vyos-1.3-rolling-202002200217-amd64.iso\n\nit works now.\n\nthanks for help!", "name": "", "is_accepted": true } ]

[ { "text": "something along:\n\nset firewall group network-group privileged\\_source description 'put a meaningful description here'\n\nset firewall group network-group privileged\\_source network '10.1.1.0/24'\n\nset firewall group network-group privileged\\_source network '10.1.2.0/24'\n\nset firewall group network-group pri…", "name": "", "is_accepted": true } ]

[ { "text": "the bug was fixed in 1.3-rolling-202012230217", "name": "", "is_accepted": true } ]

[ { "text": "this is valid only for the rolling release. 1.2 does it differently. using the fake data provided you would configure like this.\n\nset interfaces wireguard wg0 address '10.0.0.5/24'\n\nset interfaces wireguard wg0 description 'fake-config'\n\nset interfaces wireguard wg0 mtu '1420'\n\nset interfaces wireguard…", "name": "", "is_accepted": true } ]

[ { "text": "you gotta call debug on the module and receive it then via dmesg/syslog.\n\necho module wireguard +p > /sys/kernel/debug/dynamic\\_debug/control\n\ndoes that dynamically for you.\n\ni’m about to set an option up for it, but i don’t know yet if that’s gonna be backported, i have to check the show option firs…", "name": "", "is_accepted": true } ]

[ { "text": "documentation is correct as is the help shown in the auto-completion, that you provided, and has been for quite some time. you’re just plain wrong on that one.\n\nspecify a port as required by wg (not vyos) and if you aren’t listening then don’t open the port at the firewall. however that is how wg wo…", "name": "", "is_accepted": true } ]

[ { "text": "it depends on which features do you needs.\n\n1.2.x or 1.3. the 1.3 enough stable to use it in production.", "name": "", "is_accepted": true } ]

[ { "text": "hello!\n\nby default, vyos supports following settings of l2tp under ipsec:\n\nike=aes256-sha1-modp1024,3des-sha1-modp1024,3des-sha1-modp1024!\n\nesp=aes256-sha1,3des-sha1!", "name": "", "is_accepted": true } ]

[ { "text": "[@sam\\_g](/u/sam_g)\n\nit’s doesn’t work because you ping from source ip address 192.168.57.192\n\nbut r2 doesn’t know anything about this network (192.168.57.x) but know network 1.1.1.0/24", "name": "", "is_accepted": true } ]

[ { "text": "please do not use link local address to set dns to continue recording. this address should only be used for dad detection and multicast communication in lan. router ra should be configured so that clients can obtain stateless address by slaac. this address should be unique for intranet prefix. you c…", "name": "", "is_accepted": true } ]

[ { "text": "workaround for missing dhcp default route:\n\nset protocols static route 0.0.0.0/0 dhcp-interface eth0", "name": "", "is_accepted": true } ]

[ { "text": "try to set ttl:\n\nset interfaces tunnel tun0 parameters ip ttl 64", "name": "", "is_accepted": true } ]

[ { "text": "hello.\n\nno, i don’t have a deticated dns server. i was hoping vyos could be that. how do you enter host entries into vyos?\n\ni believe it uses pdns", "name": "", "is_accepted": true } ]

[ { "text": "i don’t see rules for prefix-list.\n\ncan you share it? is address 111.68.25.242 exists/match in the prefix-list rule?", "name": "", "is_accepted": true } ]

[ { "text": "i’ve made sample test on lab using latest version and it worked as expected. also, made some test in version 1.3-rc6, getting same result.\n\nvyos@vyos# run show ver\n\nversion: vyos 1.4-rolling-202109050613\n\nrelease train: sagitta\n\nvrrp configuration on router\n\nvyos@vyos# run show config c…", "name": "", "is_accepted": true } ]

[ { "text": "debug. but again it is very minimal and shows you only rekeying and keepalices and the such, which is easier to see via tcpdump.", "name": "", "is_accepted": true } ]

[ { "text": "issue with the repository - fixed now", "name": "", "is_accepted": true } ]

[ { "text": "[@utosun](/u/utosun) it will be fixed with next rolling release, after 24.06", "name": "", "is_accepted": true } ]

[ { "text": "this ended up being my windows 10 machine. there were two routes in there for 0.0.0.0. it is working as expected.", "name": "", "is_accepted": true } ]

[ { "text": "there’s a [blog post](https://blog.vyos.io/2020-recap-and-2021-q1-plan) today that touches on these. looks like 1.3 lts is coming right along and the snapshots are coming with the new community site.", "name": "", "is_accepted": true } ]

[ { "text": "i think you can clone from git and build from docker container. \n\nenter to docker container\n\ndocker run --rm -it --privileged -v $(pwd):/vyos -w /vyos vyos/vyos-build bash \n\nget necessary source code\n\ngit clone https://github.com/vyos/vyatta-ipv6-rtradv.git \n\nneed choice commit and patch files\n\ncd v…", "name": "", "is_accepted": true } ]

[ { "text": "in the latest chronicles of me replying to myself and resolving issues\n\nturns out if i made my interfaces the base vlan interfaces instead of the vlan vrrp interfaces things are working properly. something must have changed since may for this to stop functioning but figured out finally and can move …", "name": "", "is_accepted": true } ]

[ { "text": "latest rolling has those drivers included", "name": "", "is_accepted": true } ]

[ { "text": "you need to add the attribute framed-ip-address on radius server only for these 2 accounts.\n\nif radius server does not send framed-ip-address then to clients will allocate ip from defined ip address pool on l2tp server.", "name": "", "is_accepted": true } ]

[ { "text": "it is community edition. try to test it.\n\nit listen mirrored traffic on specific port. so you need to check your cpu/memory statistic with this feature and without it.", "name": "", "is_accepted": true } ]

[ { "text": "to further analyze this, i would recommend to test from the router. your issue sounds like a driver reset on the windows side. when the issue is present, login into the router from a different device or via console and try to ping the windows host ipv4 address ad well as the upstream ipv4 gw.\n\nif bo…", "name": "", "is_accepted": true } ]

[ { "text": "[image] maimun.najib:\n\n(inaccessible\n\nit seems next-hop unreachable.\n\nshow ip route 8.8.8.8", "name": "", "is_accepted": true } ]

[ { "text": "you shouldn’t need a “relay-chain” you just setup dhcp relay on router a so that it is relaying requests to the ip address of the dhcp server behind b.\n\nconfig to apply to router a:\n\n# show service dhcp-relay\n\ninterface eth1 <------- interface on router a that has your client(s) on it.\n\nser…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@samip537](/u/samip537)\n\nin this is an example we export only prefix “2a0e:b107:6ec::/48” to ipv6 neighbor and importing “none”\n\nset policy prefix-list6 out rule 10 action 'permit'\n\nset policy prefix-list6 out rule 10 prefix '2a0e:b107:6ec::/48'\n\nset policy route-map rmap-in rule 10 action 'deny'\n\nset policy r…", "name": "", "is_accepted": true } ]

[ { "text": "thank you, [@studioharuspex](/u/studioharuspex). already fixed <https://phabricator.vyos.net/t1705>", "name": "", "is_accepted": true } ]

[ { "text": "you can check /var/log/ folder for log files, dmesg for kernel log.\n\nif you really want to check, commit save your config and check if /config/config.boot has the correct config, the show config output should also be in config.boot. that will survive the boot.\n\nalso what may happened, is that you bo…", "name": "", "is_accepted": true } ]

[ { "text": "yes, this will work, as you want. if: \n\nnetwork xxx is configured as a blackhole.\nthe route to the yyy network is configured via a gateway in xxx.\nrp\\_filter set to 1 on the ethx interface. \nthen traffic from yyy received on the ethx interface will be dropped.\n\nbut, you are close to reinventing bgp f…", "name": "", "is_accepted": true } ]

[ { "text": "ok, does the remote openvpn router know about your local net xxx.xxx.0.0/24?\n\ncan you try to run ping xxx.xxx.161.186 interface xxx.xxx.0.1 where xxx.xxx.0.1 - ip address on bridge interface.\n\nin another case, you need to add additional nat rule\n\nset nat source rule 110 outbound-interface 'vtun0'\n\nse…", "name": "", "is_accepted": true } ]

[ { "text": "you need to add the static route with the next-hop of your vpn , if you need check it .you can run the command show ip route table 220 , it show something like this:\n\nshow ip route table 220\n\ncodes: k - kernel route, c - connected, s - static, r - rip,\n\no - ospf, i - is-is, b - bgp, e - eigr…", "name": "", "is_accepted": true } ]

[ { "text": "[@sd0](/u/sd0) you have mistakes with configuration \nyou use eth1 and eth2 without vlans, but you set policy routes with vlan10 and vlan11. \nset interfaces ethernet eth1 vif 10 policy route ‘pbr’ \nset interfaces ethernet eth2 vif 11 policy route ‘pbr’ \nexample in docs was with one ethernet interface and 2 sub…", "name": "", "is_accepted": true } ]

[ { "text": "if you want to use both new asn and old asn, you need another peer session with the parameter “local-as”\n\nset protocols bgp 2000 neighbor 203.0.113.1 remote-as '65001'\n\nset protocols bgp 2000 neighbor 203.0.113.254 local-as 3000\n\nset protocols bgp 2000 neighbor 203.0.113.254 remote-as '65001'", "name": "", "is_accepted": true } ]

[ { "text": "try this one:\n\nset vrf bind-to-all", "name": "", "is_accepted": true } ]

[ { "text": "you can mark the routes with community.\n\nfor example:\n\nset policy community-list in rule 10 action 'permit'\n\nset policy community-list in rule 10 regex '65001:111'\n\nset policy community-list out rule 10 action 'permit'\n\nset policy community-list out rule 10 regex '65001:222'\n\nset policy route-map rmap-i…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@lexxa77](/u/lexxa77) , the bfd output is correct.\n\nit a bug in frr with output for bgp neighbor.\n\n“the issue is: the daemons that are using bfd does not have a way to get notified about timer value changes, so they always display whatever was configured or the defaults”\n\nlink [bfd-issue](https://github.com/frrouting/frr/issues/4485)", "name": "", "is_accepted": true } ]

[ { "text": "ok… it seems, that there are no logfiles (almost none) that can be deleted with this command and it seems, that everything goes into the… journal-log (whatever this is, don’t ask me, i’ve no idea how linux works, but i’m learning quick) … clearing this seems to work with\n\njournalctl --rotate … but n…", "name": "", "is_accepted": true } ]

[ { "text": "case of rtfm, the commands needed\n\nset system name-server (one name server per line. so more name servers more lines)\n\nset system domain-name\n\ni did not have to set these in 1.1.7, they were picked up from dhcp. so there was a change from 1.1.7 to 1.4…", "name": "", "is_accepted": true } ]

[ { "text": "i can’t reproduce it in vyos 1.4-rolling-202103190310", "name": "", "is_accepted": true } ]

[ { "text": "looking through that link it seems related to alg (i.e. conntrack helpers). another way to help mitigate the attack would be to disable conntrack helpers unless they are absolutely necessary for your environment/setup. e.g.\n\nset system conntrack modules ftp disable\n\nset system conntrack modules gre …", "name": "", "is_accepted": true } ]

[ { "text": "hi [@xtremxyz](/u/xtremxyz),\n\nthis is clearly a bug that you can no longer set encaplimit none - or that the config was not migrated to integers only. the encaplimit default is 4, what happens if you specify encaplimit 0 and test again?\n\nissue tracked via <https://phabricator.vyos.net/t3406>", "name": "", "is_accepted": true } ]

[ { "text": "it still in the development stage and needs more tests/reviews/bugfixes.\n\ngraphroot = \"/config/containers/storage\"", "name": "", "is_accepted": true } ]

[ { "text": "hi [@omidit](/u/omidit) .\n\nin your config, you should change tunnel source-address and remote address, and use “public” ip address (172.16.1.x in your case).\n\nrefer to: [tunnel — vyos 1.4.x (sagitta) documentation](https://docs.vyos.io/en/latest/configuration/interfaces/tunnel.html#generic-routing-encapsulation-gre)", "name": "", "is_accepted": true } ]

[ { "text": "you need firewall rules like\n\nset firewall group address-group blck address '51.10.10.1'\n\nset firewall name frwd-in default-action 'accept'\n\nset firewall name frwd-in rule 10 action 'drop'\n\nset firewall name frwd-in rule 10 destination address '8.8.8.8'\n\nset firewall name frwd-in rule 10 source group ad…", "name": "", "is_accepted": true } ]

[ { "text": "hello [@mafiosa](/u/mafiosa), i can confirm the bug. it looks like an interface state issue, please check show interfaces. if vxlan1 has state a/d, try manually up this sudo ip link set vxlan1 up and check again.", "name": "", "is_accepted": true } ]

[ { "text": "hi. 1gbit wan you should be ok with any server from recent years\n\n10gb should not be a problem either, make sure you get good nics\n\nsee <https://faelix.net/static/netmcr20191010.pdf>\n\nthere is spec\n\nsm chassis: front i/o, redundant 400w psus\n\nsm x11scm-f (2x rj45 intel® i210-at + oob/ipmi)\n\nxeon e3-1265…", "name": "", "is_accepted": true } ]

[ { "text": "hi sledge13!\n\nthis forum is for vyos, not vyatta…\n\nvyos is a many year old fork of vyatta and behavior has changed between the two products.", "name": "", "is_accepted": true } ]

[ { "text": "yes, it is normal behaviour. it use strongswan by default <https://wiki.strongswan.org/projects/strongswan/wiki/introductiontostrongswan#routing>", "name": "", "is_accepted": true } ]

[ { "text": "[@hazaki](/u/hazaki) i created a bug report for it. ref <https://phabricator.vyos.net/t3388>\n\nthanks", "name": "", "is_accepted": true } ]

[ { "text": "hello chief\\_dan,\n\nit works perfectly by adding persistent routes!\n\nthanks a lot for your help!\n\nhave a good weekend.", "name": "", "is_accepted": true } ]

[ { "text": "typical upgrade path should work, but we always recommend to test configuration in vm before (just in case)", "name": "", "is_accepted": true } ]

[ { "text": "my organization uses hyper-v in both failover cluster and as standalone hosts. i frequently have problems with the hyper-v cluster changing mac addresses or giving a migrated vm a duplicate mac of an existing vm when the vms migrate to a different physical host in the cluster. i have not seen this…", "name": "", "is_accepted": true } ]

[ { "text": "hi please see screenshot for details.\n\n[[image]](https://forum.vyos.io/uploads/default/original/2x/8/8deb32b297ef4dd39d3c215d51faff46690cf650.png \"image\")\n\nshow arp is the command to see the arp table in this version.\n\nsolution : after deleting the vyos then reinstall it worked. i configured each interface at a time.\n\nmy device behind interface eth0 i had to reboot as well after the reboot i was able to …", "name": "", "is_accepted": true } ]

[ { "text": "it probably that task <https://phabricator.vyos.net/t3290>", "name": "", "is_accepted": true } ]

[ { "text": "you can restrict the source ip address to a specific ip / network by adding:\n\nset nat destination rule 100 source address <ip address>\n\nhowever currently vyos doesn’t support nat groups (the firewall does), so if you need to allow several network you need either to:\n\nconfigure several nat rules\n\nhav…", "name": "", "is_accepted": true } ]

[ { "text": "i’m sure that it is possible to use a redirect to one ifb for many subinterfaces. i think you need to try.\n\nalso, i think that policer has more performance if you have a high load system.", "name": "", "is_accepted": true } ]

[ { "text": "the fix was added on may 23, i propose update your router to the latest rolling.", "name": "", "is_accepted": true } ]

[ { "text": "solved!!! (my mistake, sorry!)\n\nthe openvpn server on vyos (1.2.1) doesn’t use the “-client-to-client” option:\n\n> --------------- ps -ax | grep openvpn ---------------\n\n> 90669 ? ss 1:08 /usr/sbin/openvpn --daemon openvpn-vtun0 --verb 3 --writepid /var/run/openvpn-vtun0.pid --status /o…", "name": "", "is_accepted": true } ]

[ { "text": "fair enough and appreciate the update.\n\nthe issue was incorrect syntax. seems the op is sorted now.", "name": "", "is_accepted": true } ]

[ { "text": "seems isp block ipsec. please mark it as solved, if you don’t have another issues.", "name": "", "is_accepted": true } ]

[ { "text": "this moved fairly recently, and it appears that the documentation hasn’t been fully updated yet.\n\nthe basic format and commands are the same:\n\nsee:\n\nset service router-advert interface <interface name>\n\npossible completions:\n\ndefault-lifetime\n\nlifetime associated with the default ro…", "name": "", "is_accepted": true } ]

[ { "text": "ok, i missed the one thing i should have seen all along…\n\ni didn’t add a rule for all related and established connections to the outside-in ruleset.\n\nyeah, it was something super simple that i was overlooking. again.\n\nthanks all for your input. i’ll write this one down as a lesson learned.", "name": "", "is_accepted": true } ]

[ { "text": "turns out that the sticky-connections setting actually works\n\nonly ping doesn’t work because it’s not nated", "name": "", "is_accepted": true } ]

[ { "text": "the script is out of sync with current debian, ss is now /bin/ss\n\nthanks for reporting, i’ll fix it.", "name": "", "is_accepted": true } ]

[ { "text": "okay so i need to add rule 2 and so on. got it", "name": "", "is_accepted": true } ]

[ { "text": "[image] rand0m:\n\nset policy route pbr rule 10 set table '100'\n\nset policy route pbr rule 10 source address '192.168.3.0/24'\n\nlets try to modify these rule\n\nset policy route pbr rule 10 set table '100'\n\nset policy route pbr rule 10 source address '192.168.3.0/24'\n\nset policy route pbr rule 10 desti…", "name": "", "is_accepted": true } ]

[ { "text": "adding this option would be quiet easy for both of us.\n\ni took the opportunity to document how our kernel is built (<https://github.com/vyos/vyos-documentation/commit/e9171f34fbc21dda1d54dec1c4843fdcde647398>).\n\nplease check out the updated documentation at\n\n[https://docs.vyos.io/en/latest/contributin…](https://docs.vyos.io/en/latest/contributing/build-vyos.html#linux-kernel)", "name": "", "is_accepted": true } ]

[ { "text": "could you please try vyos 1.2.7 version and let us know if the issue persists.", "name": "", "is_accepted": true } ]

[ { "text": "after three weeks of messing around with it i finally have success!\n\nthe problem was that on my production network i have the “local” zone as well as other zones.\n\nall i needed to do was to allow the internet zone (which my vxlan is on) to pass through udp port 8472 packets to the local zone!\n\nso si…", "name": "", "is_accepted": true } ]

[ { "text": "[quote=“viacheslav, post:2, topic:6062”]\n\non another node “touch” that file and paste lines from that .key file\n\nsudo nano /config/auth/foo.key\n\nnano - it’s a text editor\n\npaste the contents of the key\n\nand press “ctrl+x” and “y” for saving file", "name": "", "is_accepted": true } ]

[ { "text": "[image] donmicky:\n\nplease how do we erase the configuration ?\n\ni’m a bit late to the party, but in case someone wants to know how to reset their vyatta installation.\n\nconfigure\n\nload /opt/vyatta/etc/config.boot.default\n\ncommit\n\nsave", "name": "", "is_accepted": true } ]

[ { "text": "figured out what was going on -\n\nwhen you have only one nic (eni) associated to an instance then you can set the ‘source/destination check’ at the instance level. in fact, when you check the ‘source/destination check’ from the instance it will show you the setting for the primary eni.\n\nmy error was …", "name": "", "is_accepted": true } ]

[ { "text": "firewall logging will be fixed in the next lts release\n\n<https://phabricator.vyos.net/t1938>", "name": "", "is_accepted": true } ]

[ { "text": "just want to update. my configuration did work finally. the issue was that one of the public ip i was using for second tunnel was originally used on a test vm for speed testing. shutting down that vm basically freed up the ip conflict.", "name": "", "is_accepted": true } ]

[ { "text": "why would you delete packages that are part of vyos?\n\ninstall a new image and import your config", "name": "", "is_accepted": true } ]

[ { "text": "it looks like in your example above, you’re running a show command on the config, i.e. show me this chunk of configuration.\n\nif you commit your config, then type exit to revert back to operational mode, what does “show flow-accounting” give you then?", "name": "", "is_accepted": true } ]

[ { "text": "delete interfaces openvpn vtun0 local-host\n\nset interfaces openvpn vtun0 openvpn-option multihome\n\nthis should make it listen on 0.0.0.0 (all ips)", "name": "", "is_accepted": true } ]

[ { "text": "hi avdvever,\n\nit’s under “set protocols bgp xxxx neighbor x.x.x.x as-override”.", "name": "", "is_accepted": true } ]

[ { "text": "i am so very sorry.\n\nit was a different device at the end of the ip, not the vyos.\n\nmy colleagues had moved the ip to a sophos device, and the ip was mapped to its ha port.", "name": "", "is_accepted": true } ]

[ { "text": "new config vy -3\n\nset policy prefix-list as65535-in rule 16 action ‘permit’\n\nset policy prefix-list as65535-in rule 16 ge ‘8’\n\nset policy prefix-list as65535-in rule 16 prefix ‘100.0.0.0/0’\n\nand out same", "name": "", "is_accepted": true } ]

[ { "text": "i understand now. \nyou are probably having mtu problems \nsee the [tcp mss clamping](https://wiki.vyos.net/wiki/pppoe) example. it didn’t make it over to the new documentation system, but i’ve migrated it.", "name": "", "is_accepted": true } ]

[ { "text": "after a reconfiguration from scratch it worked …", "name": "", "is_accepted": true } ]

[ { "text": "sorry tor taking so much time to answer. im 99% sure its the 1.3v . i guess i found out the reason of the problem. i was checking the running processes and suddenly the snmp starting showing 100% of use of the system’s memory. we monitor it with zabbix, via snmp. we immediately stopped all the snmp …", "name": "", "is_accepted": true } ]

[ { "text": "sure! it’s quite easy.\n\nfirst you setup a policy.\n\nthis policy says \"if i see any traffic with a source address of (your vlan10 clients) then i am going to put that traffic into routing table 100. you can use any table id, it doesn’t have to be 100.\n\nme@vyos# show policy\n\nroute lan-policy-based-rou…", "name": "", "is_accepted": true } ]