Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "thank you. we will continue using the bridge.", "name": "", "is_accepted": true } ]

[ { "text": "believe i just answered this same question/issue in another section of the forum\n\n[image]\n\n[randomly failing to resolve host address (openvpn + 1.3 rolling only)](https://forum.vyos.io/t/randomly-failing-to-resolve-host-address-openvpn-1-3-rolling-only/5562/4) [bugs](/c/bugs)\n\ni had this issue before and fixed it by using a solution provided by [@raeven](/u/raeven) on slack. try setting openvpn-o…", "name": "", "is_accepted": true } ]

[ { "text": "no, more details [wireguard doesn't allow use of dns for remote peer endpoint](https://forum.vyos.io/t/wireguard-doesnt-allow-use-of-dns-for-remote-peer-endpoint/5314)", "name": "", "is_accepted": true } ]

[ { "text": "hello, can you confirm that cause of memory leak is solved with ixgbe 5.6.3?", "name": "", "is_accepted": true } ]

[ { "text": "hello [@culkinad](/u/culkinad). you can handle more 2000 customers and on desktop hw like (i5/i7 ivy-bridge). main hw params in this case nic intel 82599 or x710/xl710. as for servers hw - nice choice poweredge r640. also you need to disable ht and enable rps, because pppoe is l2 traffic. of course cpu and ram fre…", "name": "", "is_accepted": true } ]

[ { "text": "ok - is it because i had no default route present on r7 and r8? what i did here is i only had reverse routes present for 192.168.47.0/24 and 192.168.42.x on r7 and r8 respectively.\n\ni just added a route on r7 as\n\n[edit]\n\nvyos@r7# set protocols static route 0.0.0.0/0 next-hop 100.1.1.48\n\nand same on r…", "name": "", "is_accepted": true } ]

[ { "text": "we have not implemented ldpd in our rolling releases by default, so there are no such additional commands (for restarting).", "name": "", "is_accepted": true } ]

[ { "text": "[@rand0m](/u/rand0m) can you delete rule 350 in nat?\n\nset nat source rule 350\n\ndo you really need it?", "name": "", "is_accepted": true } ]

[ { "text": "hello [@paulojrandrade](/u/paulojrandrade). you can update your router next command for rolling release \nadd system image https://downloads.vyos.io/rolling/current/amd64/vyos-rolling-latest.iso\n\nor install ixgbe 5.6.3 deb package for 1.2.3. for this method you need create support request. \nnotice: reboot is necessary f…", "name": "", "is_accepted": true } ]

[ { "text": "amd64, but you should be warned that there are a lot of differences between vse 6.3 and vyos 1.1.8\n\nthis may not end well. vyos is a fork from vyatta 6.6(if i recall correctly), and there are many differences between 6.3 and 6.6. nat commands being the biggest change i can remember.", "name": "", "is_accepted": true } ]

[ { "text": "thanks! the version is 1.1.8\n\nnat {\n\nsource {\n\nrule 8 {\n\ndescription \"exclude encrypted traffic from nat\"\n\ndestination {\n\naddress 10.150.0.0/22\n\n}\n\nexclude\n\noutbound-interface eth2\n\n}\n\nrule 9 {\n\n…", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\nthe value in the brackets are a the tag. you can check the weight or other bgp related infos with:\n\nshow ip bgp\n\nyou set the weight to the prefix, but both router 100.100.100.6 and 102.102.102.7 propagate this prefix.\n\none option is create a route-map per neighbor or you match with e.g. the i…", "name": "", "is_accepted": true } ]

[ { "text": "all good. no worries at all. i appreciate the help.", "name": "", "is_accepted": true } ]

[ { "text": "yes eth1 is the lan network interface, and its subnet is 10.11.0.0/24.\n\neth0 is the vyos public network interface.\n\n10.10.0.0/24 (and 10.50.0.0/24) are the remote subnets.\n\ninterestingly it worked when i attached these rules to the eth0 interface as ‘in’:\n\nset firewall group network-group remote-ne…", "name": "", "is_accepted": true } ]

[ { "text": "hi.\n\nthanks for the info. i’m running my own vyos build v1.2.5\n\nthe problem came from a misunderstanding of how addressing is supposed to work in wireguard. i updated my config to be a bit different now and all works.\n\nsetting address 10.50.50.1/24 did work though, not sure about 10.50.50.0/24, didn…", "name": "", "is_accepted": true } ]

[ { "text": "the qcow image is a basic image, just as if you installed it from iso. only its installed allready for your benefit.", "name": "", "is_accepted": true } ]

[ { "text": "arrrrr! thanks for your suggestion, but i figured it out. the tftp service was only binding to the ipv4 address. i’m dual stacked on the gitlab / tftp server and have a and aaaa records for it in dns. vyos was preferring the ipv6 connection when using fqdn. \nonce i set the flag to ipv6, the service …", "name": "", "is_accepted": true } ]

[ { "text": "hello [@romantcyganov](/u/romantcyganov) , thank you for reporting a bug. this bug also affected 1.3-rc6 version.\n\nyou can track the bug by the following link [⚓ t3790 does not possible to configure pptp static ip-address to users](https://phabricator.vyos.net/t3790)", "name": "", "is_accepted": true } ]

[ { "text": "hi maltahl!\n\nwhile looking at your error i see: unable to modify interface: address already in use, this means that port 53 is already in use on your device.\n\nas port 53 is dns, do you have a dns server configured on your device?", "name": "", "is_accepted": true } ]

[ { "text": "problem is fixed by changing network interface driver from virtio to rtl8139 or e1000.", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\ni think you will not achieve much performance because vyos does not use much io or read/write speed.\n\nthanks,", "name": "", "is_accepted": true } ]

[ { "text": "this one will be fixed in the 1.3 beta version from tomorrow - easy fix, nasty error.\n\n[ssh: t3212: remove restartpreventexitstatus from systemd unit](https://github.com/vyos/vyos-1x/commit/c71bf9ca97a04d578eb1f600fb7435b001fd17cd)\n\ncommitted 04:50pm - 18 jan 21 utc (utc)\n\n[[c-po]\n\n…](https://github.com/c-po)", "name": "", "is_accepted": true } ]

[ { "text": "just readded the 1.3 rc2 image via my working 1.3 rc1 installation. rebooted the router and bam, no dhcp. at this point i am 100% certain rc2 dhcp client is broken big time. only took my until 0130 my time to sort it out. welcome any and all outside confirmation or refutation. vyos team, let’s hope …", "name": "", "is_accepted": true } ]

[ { "text": "zone police zone 20lan has no ruleset attached, allowing traffic from 00lan", "name": "", "is_accepted": true } ]

[ { "text": "figured it out - for anyone stumbling on this the body needs to be formed as follows\n\n$body = @{\n\ndata = '{\"op\": \"showconfig\",\"path\": []}'\n\nkey = \"supersecretkey\"\n\n}", "name": "", "is_accepted": true } ]

[ { "text": "this sounds like two questions rather than one. :wink:\n\ni feel like the real question is whether you can run vyos on bare metal, and the answer is yes, you can. if you already have another linux distro installed on that box, it should run vyos just fine too.\n\nboot it from the vyos livecd (or make a …", "name": "", "is_accepted": true } ]

[ { "text": "try to check\n\nshow ipv6 bgp summary\n\ncheck also, if you have that option in the configuration\n\nset protocols bgp xxxxx parameters default no-ipv4-unicast", "name": "", "is_accepted": true } ]

[ { "text": "ok resolved with hw-id command and rebooted the machine. that resolved the issue.", "name": "", "is_accepted": true } ]

[ { "text": "dang!! issue is resolved.i spent almost 2 days and night and you know the issue was digital ocean firewall which was blocking the connection. even numerous times i allowed source 172.16.3.0/24 all tcp/all udp/icmp but it was not allowing.\n\nfinally this morning i thought lets remove the firewall comp…", "name": "", "is_accepted": true } ]

[ { "text": "hagbard is right. if you have more than one active default routes and want to use nat, you must configure load balancing or routing policy to be ensure that all traffic for same connection will be forwarded through one external interface.\n\notherwise, problems is inevitable. :slight\\_smile:", "name": "", "is_accepted": true } ]

[ { "text": "do you want to load key from ansible to vyos host?\n\nexample [ansible — vyos 1.4.x (sagitta) documentation](https://docs.vyos.io/en/latest/automation/vyos-ansible.html)", "name": "", "is_accepted": true } ]

[ { "text": "can you check if you have in /etc/ntp.conf the line interface ignore wildcard. if so, put it into comment and restart ntpd and check if it works then.", "name": "", "is_accepted": true } ]

[ { "text": "this supported in latest rolling releases \n<https://downloads.vyos.io/?dir=rolling/current/amd64>", "name": "", "is_accepted": true } ]

[ { "text": "are you getting more speed than expected?\n\nmaybe you are taking 0.5mbps as 0.5mbit/s? it actually is 0.5 mbyte/s.\n\nvery often problems come because of [tc’s very peculiar way of naming rate units](https://docs.vyos.io/en/latest/qos.html#units).\n\nlet us know if that is your case.", "name": "", "is_accepted": true } ]

[ { "text": "[@toadzhou](/u/toadzhou) you can use pseudo-ethernet interfaces\n\n[[map2wan]](https://forum.vyos.io/uploads/default/original/2x/5/5f5751f4225514a58f58f249504a51c6d6534535.png \"map2wan\")\n\ndelete ip addresses from eth0 and assign it to pethx interfaces. example in lts release.\n\nnat-gw configuration\n\nset firewall all-ping 'enable'\n\nset firewall broadcast-ping 'disable'\n\nset firewall config-trap 'disable'\n\nset firewall ipv6-rec…", "name": "", "is_accepted": true } ]

[ { "text": "on site a: add routes to pin each tunnel to an interface\n\n1.1.1.2/32 -> use gw1\n\n2.2.2.3/32 ->use gw2\n\ncreate 2 vti ipsec tunnels.\n\n1: local=1.1.1.1 remote=1.1.1.2 ip=10.255.255.1/30\n\n2: local=2.2.2.2 remote=2.2.2.3 ip=10.255.255.5/30\n\nenable routing protocol like ospf , do similar on site…", "name": "", "is_accepted": true } ]

[ { "text": "answer… because first i had to go into the “configration” mode with the “config” command… the # or in front of the commands in the documentation show, if it's a config-command (#) or a normal-command () … nice… didn’t know that, maybe a point to mention in a tutorial :slightly\\_smiling\\_face:", "name": "", "is_accepted": true } ]

[ { "text": "yes, two years after, i can confirm that project is live and have bright future", "name": "", "is_accepted": true } ]

[ { "text": "hi, can you try increase some sysctl params and test again? \nset system sysctl custom net.core.rmem\\_default value '425984'\nset system sysctl custom net.ipv4.tcp\\_rmem value '4096 212992 6291456'\n\ni tested ipsec recently with speed more 1gbps without any sysctl modification and didn’t see any issues.", "name": "", "is_accepted": true } ]

[ { "text": "i figured out the key to getting this to work was changing my tunnel local ip address from being the one exposed on the external pfsense firewall to instead the private ipv4 address of the vyos node itself. that allowed vyos to figure out the ipv4 routing off the device for the tunnel.\n\ni also modif…", "name": "", "is_accepted": true } ]

[ { "text": "ok, after realizing this is was fairly simple to fix.\n\nthis is actually a well known problem, especially with the connectx-2: <https://forums.servethehome.com/index.php?threads/mellanox-connectx-2-en-and-windows-10.6991/>\n\ntl;dr: make sure to enable jumbo frames for the entire network path, possibly i…", "name": "", "is_accepted": true } ]

[ { "text": "it will be fixed with next rolling release, after 26 may.", "name": "", "is_accepted": true } ]

[ { "text": "i’ve checked the differences between the vyos 1.2.5 and 1.3. the latter has some options off by default, such as tcp-segmentation-offload, generic-segmentation-offload, generic-receive-offload. i’ve enabled all of them with:\n\nethtool -k ethx sg on\n\nethtool -k ethx gso on\n\nethtool -k ethx gro on\n\niperf…", "name": "", "is_accepted": true } ]

[ { "text": "if that is your goal, please refer to this docs:\n\nwan load balancing: [wan load balancing — vyos 1.3.x (equuleus) documentation](https://docs.vyos.io/en/equuleus/configuration/loadbalancing/index.html)\n\npolicy and multiple uplinks example: [policy — vyos 1.3.x (equuleus) documentation](https://docs.vyos.io/en/equuleus/configuration/policy/index.html#multiple-uplinks)", "name": "", "is_accepted": true } ]

[ { "text": "hello.\n\nyou can send these address through the provider’s gateway.\n\nexample:\n\nvyos@vyos# set protocols static route 192.168.200.18/32 next-hop 192.168.200.1\n\nresult:\n\nvyos@vyos# traceroute 192.168.200.18\n\ntraceroute to 192.168.200.18 (192.168.200.18), 30 hops max, 60 byte packets\n\n1 192.168.200.1 (1…", "name": "", "is_accepted": true } ]

[ { "text": "i know this is an old question, however, i believe this will really make it simpler for new users: \nin my scenario: \npc1 = 192.168.0.3 (linux) username = user1 \nvyos = 192.168.0.101 (version 1.1.8) username = user1 \n\nlogin to vyos\nswitch to configuration mode\ntype the command: loadkey user1 scp://us…", "name": "", "is_accepted": true } ]

[ { "text": "well, i think i may have had a moment… used the wrong command syntax. \nfor reference if anyone is searching it is \nset firewall name lan-cam rule 900 destination group port-group pg-ssh \nslightly not intuitive as i thought the port-group may fit under port, and didnt pick up it goes under destinatio…", "name": "", "is_accepted": true } ]

[ { "text": "nope, this not supported", "name": "", "is_accepted": true } ]

[ { "text": "[@sever](/u/sever), it solved in last rolling release.", "name": "", "is_accepted": true } ]

[ { "text": "when you configure a destination nat, the destination ip address in the nat rule is the original address the client try to reach, i.e. the wan address, and the translation address is the real address of the host.\n\nso in your nat rule you need to exchange the 2 addresses.\n\nsame for the firewall rule…", "name": "", "is_accepted": true } ]

[ { "text": "on local site add allowed ips 1.2.50.0/28 or 1.2.50.2/32\n\nallowed-ips 1.2.50.0/28\n\non the remote site add allowed ips 1.2.5.0/28 or 1.2.50.1/32", "name": "", "is_accepted": true } ]

[ { "text": "so in the end of the day this is how i solved it:\n\nansible pulls the config file from the device (nothing fashionable here, because nodes don’t have python);\n\ncontroller node uses command module to launch a python script that parses and edits the pulled config file on the controller;\n\nansible pushes …", "name": "", "is_accepted": true } ]

[ { "text": "yes, that’s correct.", "name": "", "is_accepted": true } ]

[ { "text": "latest rolling release are on 4.14", "name": "", "is_accepted": true } ]

[ { "text": "1.1.7 is extremely old and no longer supported. you’d be much better off to try with a 1.3 rolling release and see if that addresses your problem. the kernel will be much more up to date and hopefully will support what you’re after.", "name": "", "is_accepted": true } ]

[ { "text": "hello,\n\nthis is not supported currently", "name": "", "is_accepted": true } ]

[ { "text": "[@blackmetal](/u/blackmetal) try latest rolling release. \nlet us know if this feature works as expected.", "name": "", "is_accepted": true } ]

[ { "text": "fixed in next rolling", "name": "", "is_accepted": true } ]

[ { "text": "hello [@gullio](/u/gullio), i think this problem with mikrotik and mppe, in vyos cli exist special option for this. \nset service pppoe-server ppp-options mppe deny \nand commit. \nif this changes don’t help you, please provide connection log. \nshow log tail 100 | match pppoe", "name": "", "is_accepted": true } ]

[ { "text": "welcome [@absolutesantaja](/u/absolutesantaja)! i noticed this too recently and logged a ticket for it [here](https://phabricator.vyos.net/t2279). all i can do is suggest you subscribe.\n\ncheers!", "name": "", "is_accepted": true } ]

[ { "text": "try it\n\nset interfaces ethernet eth0 ip enable-proxy-arp", "name": "", "is_accepted": true } ]

[ { "text": "hello, [@alpha23](/u/alpha23)! \nyou need to build an image with enabled cloud-init, using instructions from the <https://github.com/vyos/vyos-build> \ntake attention to the target systems - different hypervisors and cloud providers may need different build targets.", "name": "", "is_accepted": true } ]

[ { "text": "hi, i think this happens because you have duplicates address in the group\n\nset firewall group address-group management-hosts address 'xxx.xxx.16.250'\n\nset firewall group address-group management-hosts address 'xxx.xxx.16.1-xxx.xxx.16.254'\n\ncan you confirm this?", "name": "", "is_accepted": true } ]

[ { "text": "[@steamedhams](/u/steamedhams) so it looks like psks are required for both peers to work not only one. this behavior was working in 1.2.\n\nprogress tracked via: <https://phabricator.vyos.net/t2632>", "name": "", "is_accepted": true } ]

[ { "text": "i forgot one quick check: how much memory does your vm have? by default kvm gives vms only 128m ram, which is too little to unpack the initramfs, so make sure you give it at least 256 (“qemu-kvm -m 256 …”).", "name": "", "is_accepted": true } ]

[ { "text": "hi, [@mp\\_irl](/u/mp_irl)!\n\ncan you try for testing purposes execute next command in shell instead of tcpdump?\n\nsudo ip link set eth0 promisc on\n\ncheck connectivity after this please.", "name": "", "is_accepted": true } ]

[ { "text": "thanks followed that thread and applied the workaround", "name": "", "is_accepted": true } ]

[ { "text": "the solution (although it’s more a “hack”)\n\nso i managed to “hack” the config so that it works ok, by doing the following:\n\ncreate a custom script with the contents given bellow:\n\nnano -w /config/scripts/wan-lb-hook.script\n\nconfigure this script as the wan load-balancing hook with:\n\nset load-balanci…", "name": "", "is_accepted": true } ]

[ { "text": "i rebooted twice didn’t help. increased ram to 2gb from 1 and got resolved.", "name": "", "is_accepted": true } ]

[ { "text": "figured out the issue.\n\nmy allowed-ips where incorrect", "name": "", "is_accepted": true } ]

[ { "text": "tcpdump tries to resolve ip addresses to their reverse dns lookup records \".in- addr . arpa \".\n\nneed additional keys.\n\nmonitor traffic interface any filter -n", "name": "", "is_accepted": true } ]

[ { "text": "i had this issue before and fixed it by using a solution provided by [@raeven](/u/raeven) on slack. try setting openvpn-option “–proto udp4” on the interface. as soon as i did this, i was no longer getting errors resolving or determining protocol and openvpn began working as expected.", "name": "", "is_accepted": true } ]

[ { "text": "hello [@alvintlc](/u/alvintlc) , did you configure coa on vyos side?\n\nset service pppoe-server authentication radius dynamic-author server 172.16.101.100\n\nset service pppoe-server authentication radius dynamic-author key somekey\n\nset service pppoe-server authentication radius dynamic-author port 3799", "name": "", "is_accepted": true } ]

[ { "text": "the difference is edgeos puts this configuration on the firewall, and vyos (more sanely in my opinion), puts this information its own section\n\nthis is my config that accomplishes two things:\n\nmakes it so i can still access the hosts from my local network.\n\nroutes all traffic from those hosts to my v…", "name": "", "is_accepted": true } ]

[ { "text": "you can set a different mtu, but i doubt that it will be an issue if you don’t filter icmp. in my tests, it was outperforming openvpn.", "name": "", "is_accepted": true } ]

[ { "text": "if you add two rules for the vpn traffic it will work.\n\nprotocol udp port 500, 4500\n\nprotocol esp", "name": "", "is_accepted": true } ]

[ { "text": "thanks [@dmitry](/u/dmitry), [@viacheslav](/u/viacheslav) for your help and support. the issue is resolved. after reconfiguration, it is working fine.", "name": "", "is_accepted": true } ]

[ { "text": "i have a write-up of the installation i just did (using virtualbox on linux to write to the raw cf card) of vyos 1.1.7 if it’s of use to anyone who finds this thread: <http://blog.jasonantman.com/2017/03/vyos-on-alix-2c1-single-board-computer/>", "name": "", "is_accepted": true } ]

[ { "text": "this should be corrected in the latest rolling versions.", "name": "", "is_accepted": true } ]

[ { "text": "no, the source address is the outoing interface. rsyslog don’t have a configuration statement where you can configure the source address. \nif you must have one specific source you have to try using nat to fix it.", "name": "", "is_accepted": true } ]

[ { "text": "further investigation revealed that azure disallows gre connections by policy. i enabled ipsec in tunnel mode, and nhrp registered immediately.\n\nalso, this appears to be an illegal command:\n\nset protocols nhrp tunnel tun0 map 172.16.128.1/24 nbma-address '[hostname].[region].cloudapp.azure.com'\n\nth…", "name": "", "is_accepted": true } ]

[ { "text": "just found out the issue, in vmware platform, i have 6 hosts, the ssh works after migrated to another host. it seems blocked by physical server. i am not sure this is related to hardware issue or vmware problem. thank you [viacheslav](https://forum.vyos.io/u/viacheslav) for helping on this case.\n\nseems this is not working on broadcom ni…", "name": "", "is_accepted": true } ]

[ { "text": "i solve my problem myself :wink: if you activate the serial console redirection in the bios it works. but you have to set the parameter hide setup item to disabled under advanced/oem form. then there is under advanced the entry serial console redirection.\n\nthanks for the posts and a happy new year!", "name": "", "is_accepted": true } ]

[ { "text": "adding the following on the vyos server (ubuntu being the client) resolved the issue. i appreciate your help.\n\nset nat source rule 10 outbound-interface 'eth1'\n\nset nat source rule 10 source address '10.10.1.0/24'\n\nset nat source rule 10 translation address 'masquerade'", "name": "", "is_accepted": true } ]

[ { "text": "dear vyos team,\n\nrelated to the problem above, it was resolved after i patched the net-snmp according to this [patch](https://sourceforge.net/p/net-snmp/patches/1352/). currently for snmpd is not using the cpu to 100%.\n\n[[image]](https://forum.vyos.io/uploads/default/original/2x/9/94e1d872e83bacb8594e50a76aacc6e167b5ddb5.png \"image\")\n\nthanks.", "name": "", "is_accepted": true } ]

[ { "text": "thanks for all the responses here. i think my questions have been answered in the vyos context. i have more questions, about dns but it would be off topic for this forum as it no longer really relates to vyos.\n\nthanks all for the help.", "name": "", "is_accepted": true } ]

[ { "text": "you can flush the entire table using the ip command.\n\nip -s -s neigh flush all", "name": "", "is_accepted": true } ]

[ { "text": "it looks like /opt/vyatta/etc/functions/script-template is overwriting $@. workaround:\n\nadd args=\"$@\" above the source line.\n\nchange main \"$@\" to main \"$args\".", "name": "", "is_accepted": true } ]

[ { "text": "thanks, [@nikita.af](/u/nikita.af)!\n\nin your case, to add the route, you need the magic option “onlink”:\n\nsudo ip route add 1.1.1.1 via 172.31.1.1 dev eth0 proto static onlink\n\nor use the vtysh, which should handle this:\n\nsudo vtysh\n\nconf t\n\nip route 1.1.1.1/32 172.31.1.1 eth0\n\nor, the native cli:\n\nset protocols stat…", "name": "", "is_accepted": true } ]

[ { "text": "figured it out. nothing wrong about the dhcp-server configuration - just a problem with my test methotology. i’m in the process of transfering the 1.1.7 config from the currently active firewall to a new box with vyos 1.2.3 and my minimal test-environment with firewall + laptop was of course way too…", "name": "", "is_accepted": true } ]

[ { "text": "hello [@frank-bnc](/u/frank-bnc), i saw you close your ticket in help desk. i need additional information.\n\nexactly output of commands:\n\nsudo systemctl status conntrackd.service\n\nsudo journalctl > /tmp/log\n\nshow configuration commands | strip-private\n\nand provide please /tmp/log. i think will be better continue rese…", "name": "", "is_accepted": true } ]

[ { "text": "notice:\n\nvalue for attribute nas-ip-address pam\\_radius gets from /etc/hosts.\n\nnas-ip-address will be correct if we add to /etc/hosts\n\n<ip address> <system\\_hostname>", "name": "", "is_accepted": true } ]

[ { "text": "srs.\n\nsolved.\n\nthe config is inside adress-family ipv4-unicast…", "name": "", "is_accepted": true } ]

[ { "text": "i don’t see your redistribute parameters.\n\ni hope it should help.\n\nset protocols bgp xxxx address-family ipv4-unicast redistribute kernel", "name": "", "is_accepted": true } ]

[ { "text": "hello [@mlewinski](/u/mlewinski), ospf cli was redesigned, now it more logical. try to use\n\nset protocols ospf interface eth0 authentication md5 ...", "name": "", "is_accepted": true } ]

[ { "text": "please upgrade to the latest version and try again as we did a lot of fixes in the last 8 weeks.", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\ni finally found the problem, i do notknow why does snmp does not available in my config.\n\ni have reapply my snmp rules and they are working now.\n\nthanks,", "name": "", "is_accepted": true } ]

[ { "text": "hello, [blason](https://forum.vyos.io/u/blason)!\n\nplease specify your vyos version. also, could you please tell, did you try set vpn ipsec options disable-route-autoinstall?\n\nyou can also clear 220 table\n\nafter all of this please let me know if it works", "name": "", "is_accepted": true } ]

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

[ { "text": "hi [@sidnei](/u/sidnei). do you have nat or stateful firewall on this router?\n\nmaybe better disable conntrack for more performance?", "name": "", "is_accepted": true } ]