Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "multicast routing not supported at this time", "name": "", "is_accepted": true } ]

[ { "text": "well, i think i may have had a moment… used the wrong command syntax.\n\nfor reference if anyone is searching it is\n\nset firewall name lan-cam rule 900 destination group port-group pg-ssh\n\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": "it’s looks like\n\nset interfaces bonding bond0 member interface 'eth1'\n\nset interfaces bonding bond0 vif-s 666 vif-c 800 address '10.60.196.1/29'", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\nyou need to use a prefix\n\nfor example:\n\n2001:db8:beef:2::/64\n\nyou try to configure a full ipv6 address", "name": "", "is_accepted": true } ]

[ { "text": "i have an idea what you can try (i don’t say it’s wrongly configured or a bug of whatever… it’s just a setting to try… sort of “set sce to aux”) …\n\nin the pppoe0 → dhcpv6-options → pd 0 → try to set “length” to 56 (or whatever length you get from your isp)", "name": "", "is_accepted": true } ]

[ { "text": "[@billdh2k](/u/billdh2k), modules already available on 1.3 beta. 1.4 rolling still on updating stage\n\nvyos@vyos:~$ show version | match version\n\nversion: vyos 1.3-beta-202102160443\n\nvyos@vyos:~$ sudo cat /boot/config-5.4.96-amd64-vyos | grep sfc\n\nconfig\\_sfc=m\n\nconfig\\_sfc\\_mcdi\\_mon=y\n\nconfig\\_sfc\\_sriov=y\n\nconfig\\_s…", "name": "", "is_accepted": true } ]

[ { "text": "in the end it appears that snat here does not get reported for the responses. decrypting of the esp packets show that correct ip headers are being sent anyway and the problem is on remote side. everything works as expected then", "name": "", "is_accepted": true } ]

[ { "text": "[@djgroom](/u/djgroom), already fixed in the latest rolling.", "name": "", "is_accepted": true } ]

[ { "text": "[image] olofl:\n\nexit\n\nrestart vpn\n\nreset ip bgp all\n\ntry to change it to:\n\nrun restart vpn\n\nrun reset ip bgp all\n\nexit", "name": "", "is_accepted": true } ]

[ { "text": "hm, very interesting situation. in this case you need manually delete all hw-id .... entry in sudo /etc/config/config.boot. and then restart router.", "name": "", "is_accepted": true } ]

[ { "text": "hi,\n\nyes the documation is not yet correct at this point. when you take a look at the possible commands:\n\nvyos@rtr-1# set interfaces vxlan vxlan123 [tab]\n\npossible completions:\n\n+ address ip address\n\n> bridge-group add this interface to a bridge group\n\ndescription description\n\n> firewall …", "name": "", "is_accepted": true } ]

[ { "text": "vyos 1.1.8 doesn’t have possibility to clear ospf process.\n\nit should be provided in 1.2.", "name": "", "is_accepted": true } ]

[ { "text": "hello sir,\n\ni tried it on <https://downloads.vyos.io/rolling/current/amd64/vyos-rolling-latest.iso>\n\nit’s working now. the above issue is not coming.\n\nwas there some fix done ? because earlier it wasn’t working.", "name": "", "is_accepted": true } ]

[ { "text": "you aren’t running vyos. you’re running edgeos. vyos is not ubiquiti.\n\nyou need to use the ubiquiti forums.", "name": "", "is_accepted": true } ]

[ { "text": "no, forwarding refers to the process of transferring a packet received on a interface out on another interface (what people usually refer as routing)\n\nmirroring is duplicating the traffic received and/or sent through an interface to another interface for the purpose of analyzing it. it is some time …", "name": "", "is_accepted": true } ]

[ { "text": "[image] romell:\n\n192.168.0.249\n\nfrom node 192.168.0.249\n\nsudo scp /config/auth/test [email protected]:/config/auth/", "name": "", "is_accepted": true } ]

[ { "text": "the was no gateway-address in pptp config.\n\nset vpn pptp remote-access gateway-address\n\nsolved the problem.\n\nthank you [@dmitry](/u/dmitry) for your help.", "name": "", "is_accepted": true } ]

[ { "text": "‘show system storage’", "name": "", "is_accepted": true } ]

[ { "text": "if you want that response was from both interfaces you need “local” pbr.\n\n<https://phabricator.vyos.net/t439>\n\nand <https://phabricator.vyos.net/t2747>\n\nso as forkaround.\n\nset protocols static table 100 interface-route 0.0.0.0/0 next-hop-interface eth0.2\n\nset protocols static table 101 interface-route 0.…", "name": "", "is_accepted": true } ]

[ { "text": "at the moment, we don’t have a specific example (with rt like you said), but there are some examples in our blog :\n\n[image]\n\n[l3vpn evpn with vyos](https://blog.vyos.io/l3vpn-evpn-creating-a-multi-tenant-service-provider-network)\n\ncreating a multi-tenant service provider network\n\n<https://docs.vyos.io/en/latest/configuration/vrf/index.html>", "name": "", "is_accepted": true } ]

[ { "text": "this commit id for branch current, seems you build 1.3-rolling. before build iso, change branch. \ngit checkout crux \nand then make your iso.", "name": "", "is_accepted": true } ]

[ { "text": "only time i learned nhrp was cisco exam years ago.\n\ni’d first fix this\n\nset protocols nhrp tunnel tun1 map 10.11.12.1/24 nbma-address ‘100.1.1.1’\n\n100.1.1.1 is used nowhere else , and probably should be 100.1.1.10\n\nbtw: afaik, ikev1 can handle aes256 fine", "name": "", "is_accepted": true } ]

[ { "text": "in my virtual setup i could not ping the br interface. they are in the same subnet. in my previous post i wrote that i don’t see traffic on macsec tunnel. i see arp request on vyos13-1, but nothing on vyos13-2.\n\ni redid this setup on hardware devices and it works, my end host communicate on layer2 t…", "name": "", "is_accepted": true } ]

[ { "text": "well this seem to work now :slight\\_smile:\n\nsource {\n\nrule 100 {\n\ndescription “outbound internet traffic”\n\noutbound-interface eth0\n\nsource {\n\naddress 192.168.0.0/20\n\n}\n\ntranslation {\n\naddress masquerade\n\n}\n\n}\n\n}", "name": "", "is_accepted": true } ]

[ { "text": "hey, \nthe build worked as its configured. i tested it a few minutes ago with current branch. actually no qcow2 or raw format is created. the make process build a iso with some extras for openstack. \nfeel free to open a pull request to build this images or create a feature request in [phabricator](https://phabricator.vyos.net) for …", "name": "", "is_accepted": true } ]

[ { "text": "i rebuilt my iso and everything seems to be golden now.", "name": "", "is_accepted": true } ]

[ { "text": "bios battery in your apu flat/going flat, causing it to lose saved time across reboots, would be my guess.\n\nonce the clock is out by a certain amount, ntp won’t try to correct it (unless forced to)", "name": "", "is_accepted": true } ]

[ { "text": "hello [@acid\\_grim](/u/acid_grim) \ncan you check command: \nsudo netstat -tulpnw | grep ssh \nvyos@vyos# run show version \nversion: vyos 1.2-rolling-201911180217\n\nvyos@vyos# show service \n ssh {\n listen-address 192.168.122.109\n listen-address fd00:feed:beef:3::233\n port 22\n }\n\nvyos@vyos:~$ sudo n…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@yueningxia](/u/yueningxia), maybe will helpful 1.3 board on the phabricator\n\n<https://phabricator.vyos.net/project/view/148/>", "name": "", "is_accepted": true } ]

[ { "text": "unlike cisco, vyos does not specify a secondary ip explicitly. just repeat the command to enter the ips.\n\ncisco\n\ninterface serial0/0/0\n\nip address 10.10.0.1 255.255.255.0\n\nip address 10.20.0.1 255.255.255.0 secondary\n\nip address 10.30.0.1 255.255.255.0 secondary\n\nvyos\n\nset interface ethernet eth0 addr…", "name": "", "is_accepted": true } ]

[ { "text": "[@priyesh4u2003](/u/priyesh4u2003), improve already in latest rolling. <https://phabricator.vyos.net/t2067>", "name": "", "is_accepted": true } ]

[ { "text": "well, i feel like a fool. i regenerated a new key and pulled down the connection files. all working now. sorry for the noise, and thanks again for the prompt response.\n\none last thing… is there a good site with info on how to read the logs?", "name": "", "is_accepted": true } ]

[ { "text": "managed to get it working by :\n\ndel system name-server ‘8.8.4.4’\n\ndel system name-server ‘8.8.8.8’\n\ndel service dns forwarding name-server ‘8.8.8.8’\n\ndel service dns forwarding name-server ‘8.8.4.4’\n\n#and use peer dns\n\nset system name-server ‘203.142.82.222’\n\nset system name-server ‘203.142.84.222’ …", "name": "", "is_accepted": true } ]

[ { "text": "the filesystem was nfs. i moved it to ext4 and it built without issue. it may be helpful to include a note under the “docker” section on github regarding this. \nthank you for your help on the issue.", "name": "", "is_accepted": true } ]

[ { "text": "hello i solved my issue.\n\nvyos vms had nothing to do with the poor routing performance. i apologize for the wasted time and bad publicity on the forum. i will modify the title accordingly.\n\ni have a edgerouter x between my pc and my esxi host and a static route sending traffic destinated to the vm b…", "name": "", "is_accepted": true } ]

[ { "text": "bfd is now in rolling and will be available in 1.2.4 lts", "name": "", "is_accepted": true } ]

[ { "text": "closing this out.\n\nusing the file that viacheslav mentioned works perfectly.\n\nfor anyone else that may want to get working, here is what i have showing interface activity for eth0 (wan), eth1 (lan trunk), and my wireguard itnterface.\n\nmodprobe ledtrig-netdev\n\necho 0 > /sys/class/leds/apu4:green:led1…", "name": "", "is_accepted": true } ]

[ { "text": "[@hagbard](/u/hagbard) lastest image vyos 1.2.0-rolling+201809120337 fixed my problem with\n\nrtnetlink answers: permission denied\n\nconfig already exists", "name": "", "is_accepted": true } ]

[ { "text": "nevermind, looks like this is a known issue already\n\n<https://phabricator.vyos.net/t445>\n\nworkaround fix, while annoying, worked for me.", "name": "", "is_accepted": true } ]

[ { "text": "from vyos host\n\nsudo curl <http://x.x.x.x>", "name": "", "is_accepted": true } ]

[ { "text": "if you can’t set source, use a snat rule.\n\nfilter on original source matching pppoe address , new address is one of your true wan ips.", "name": "", "is_accepted": true } ]

[ { "text": "hey,\n\ngreat… working with vyos 1.3-rolling-202002250504\n\n#delete interfaces ethernet eth1 vif 323\n\nthanks a lot.", "name": "", "is_accepted": true } ]

[ { "text": "[image] petr:\n\nrule 90\n\ndelete rule 90 from policy-map. so you export specific prefixes without prepending and fullview table with prepending.\n\nchange your policy route-map like this.\n\nset policy route-map out-hns-v4 rule 10 action 'permit'\n\nset policy route-map out-hns-v4 rule 10 match ip addre…", "name": "", "is_accepted": true } ]

[ { "text": "it is merely the name for the dhcp pool.", "name": "", "is_accepted": true } ]

[ { "text": "will be fixed in the next rolling release", "name": "", "is_accepted": true } ]

[ { "text": "hmm, i can’t reproduce it. i added 10 wg interfaces with names, as long as the names can be resolved everything came up. the name resolution is working before the wg interfaces are being setup, so i’m not sure why yours is not working.", "name": "", "is_accepted": true } ]

[ { "text": "i got it.\n\ni forgot to put the default-router.\n\nthe answer in my case is:\n\nconfigure\n\nedit service dhcp-server shared-network-name “network name” subnet 192.152.16.0/24\n\nset default-router 192.152.16.245\n\ncommit\n\nsave\n\nexit", "name": "", "is_accepted": true } ]

[ { "text": "hello [@eronlloyd](/u/eronlloyd) . it has by default 1000\n\nsudo sysctl net.ipv4.icmp\\_ratelimit\n\nnet.ipv4.icmp\\_ratelimit = 1000\n\nyou can try to increase this by the following command:\n\nset system sysctl custom net.ipv4.icmp\\_ratelimit value 10000", "name": "", "is_accepted": true } ]

[ { "text": "hello [@danfoster](/u/danfoster), did you try use next? \nset service ssh access-control deny user 'emergency user'", "name": "", "is_accepted": true } ]

[ { "text": "first off, keep in mind that 1.3 is buster, not stretch.\n\njust make sure to run sudo apt update before your install", "name": "", "is_accepted": true } ]

[ { "text": "i was able to build the iso without any issues - thanks for the help team", "name": "", "is_accepted": true } ]

[ { "text": "but after trying to get this topology to work for the better part of a day, i ended up redesigning the network slightly and segregating ospf into different area’s with 0.0.0.2 as a ‘border’ area with extra routers d&e for a path redundancy. \n [[image]](https://forum.vyos.io/uploads/db9559/original/1x/aedc0b3790bd97e6503c3cb9013272dadf239d1a.png \"image.png\")\nits now working as it should.", "name": "", "is_accepted": true } ]

[ { "text": "well if some one experiment the same situation i can confirm the packet flow when a dnat it’s apply the zone-policy should come from a local-zone to the lan zone.", "name": "", "is_accepted": true } ]

[ { "text": "okie dokie mate,\n\ni going to deploy zone-based config…", "name": "", "is_accepted": true } ]

[ { "text": "it seems that it is mandatory to use add system image to upgrade (it is not recommended to use apt to update, it may damage the system)", "name": "", "is_accepted": true } ]

[ { "text": "try such configuration (in the example only pool 66–70)\n\nset interfaces ethernet eth4 vif 101 address '10.0.27.65/27'\n\nset interfaces ethernet eth4 vif 101 ip proxy-arp-pvlan\n\nset interfaces ethernet eth6 vif 501 address '203.0.113.94/27'\n\nset interfaces ethernet eth6 vif 501 description 'foo'\n\nset inte…", "name": "", "is_accepted": true } ]

[ { "text": "so far the plan is only to make it available via pam, which means authentication on a vyos system only. the local openvpn process may be able to use that as well, not sure yet.", "name": "", "is_accepted": true } ]

[ { "text": "1.1.8 is eol and has a different syntax.\n\nset interfaces ethernet eth1 vrrp xxx\n\nit is recommended to use lts or at least 1.3 version. for example [1.3.0-rc6](https://vyos.net/get/snapshots/)", "name": "", "is_accepted": true } ]

[ { "text": "i am so sorry, i have taken so much of your time.\n\nit works without issue now.\n\nall i had to do was add a route to the sophos host ip, on the pfsense vti, and set an exclude on nat for the sophos ip, on the vyos.\n\ni can now ping the pfsense host ip from the sophos ip, through the vpn!\n\nall i had to …", "name": "", "is_accepted": true } ]

[ { "text": "i‘m on your side on this. the default of maxfail10 makes little sense. will change it to 0.\n\n<https://phabricator.vyos.net/t2087>", "name": "", "is_accepted": true } ]

[ { "text": "at the moment, i don’t see a solution.", "name": "", "is_accepted": true } ]

[ { "text": "hi, zakwan\n\nmaybe you met the same issue as me. please follow my instruction to fixed this issue.\n\n[image]\n\n[how to make lan as the default gateway and make static routing for wan works](https://forum.vyos.io/t/how-to-make-lan-as-the-default-gateway-and-make-static-routing-for-wan-works/4681/8)\n\nhello [@echowings](/u/echowings), i reproduced this schema in our laboratory, and i think i have workaro…", "name": "", "is_accepted": true } ]

[ { "text": "update: i have to run the docker with --sysctl net.ipv6.conf.lo.disable\\_ipv6=0 to pass the test, then everything is fine. now i can build the deb files.\n\nthank you viacheslav.", "name": "", "is_accepted": true } ]

[ { "text": "it was an issue with wireless at the remote site, not sure what it is yet but full functionality if plugged in via hardware.", "name": "", "is_accepted": true } ]

[ { "text": "hello [@marcomuskus](/u/marcomuskus), you can use standard radius attributes delegated-ipv6-prefix and framed-ipv6-prefix", "name": "", "is_accepted": true } ]

[ { "text": "i found the unionfs-fuse issue crop up on an aws instance as well.\n\ni also found it only happened when using a script without telling it to exit when done. example -\n\nroot@router:/scripts# df -h | wc -lc\n\n65 5092\n\ncurrently 65 mountpoints.\n\nrunning this simple script -\n\n#!/bin/vbash\n\nsource /op…", "name": "", "is_accepted": true } ]

[ { "text": "[image] juesor:\n\nflags 0x00000200, action taken “treataswdr”. err\n\nas i see the vyos send prefixes, but xr9kv don’t accept it?\n\ntry on the xr9kv site\n\nno bgp enforce first-as", "name": "", "is_accepted": true } ]

[ { "text": "[image] viacheslav:\n\nthis prefix is local on that router. so you don’t receive it from the neighbor.\n\nyes, that is expected and okay. it really seems that updating to the latest rolling release fixed the problem of no metric/local pref being set.", "name": "", "is_accepted": true } ]

[ { "text": "you may be missing a few configuration options, qos can be a very complex topic. to see a practical example:\n\n<https://www.five-ten-sg.com/mapper/blog/bufferbloat%20solved%20with%20vyos>\n\nalso a good read:\n\n<https://wiki.vyos.net/wiki/qos>", "name": "", "is_accepted": true } ]

[ { "text": "[@zeroh](/u/zeroh), analizing your network diagram and the commands executed on one router, there seems to be some basic errors in your deployment:\n\nnetwork segmentation: you define the network 10.45.32.0/24 for your “internet network”, and also 10.45.32.32/27 for your “virtal lan network”. second network (/27…", "name": "", "is_accepted": true } ]

[ { "text": "source nat (masquerade) happens at post routing\n\ndestination nat at pre-routing: we must change the destination address, before we take routing decision based on destination address.\n\neth+ means: match on all eth interfaces.\n\nin your lb rule 2, it makes no sense to use eth+. packets from 192.168.40…", "name": "", "is_accepted": true } ]

[ { "text": "any rolling release after vyos-1.3-rolling-202002220217-amd64.iso should have it back in. please test and report bugs via phabricator.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@mafiosa](/u/mafiosa)!\n\ntry to generate/configure a link-local (fe80::/10) address on the tunnel interfaces. this solution worked for me.\n\ni think that these link-local addresses should be automatically generated and configure on any interface but it does not occur in vyos (<https://phabricator.vyos.net/t2807>)…", "name": "", "is_accepted": true } ]

[ { "text": "just delete the fixed address. \ndelete interfaces ethernet eth1 address 192.168.0.1/24 \nset interfaces ethernet eth1 address dhcp \ncommit \nor the reverse.", "name": "", "is_accepted": true } ]

[ { "text": "ok. that all makes much more sense now. so if i were you, i would create a source nat rule with the wireguard interface as the outbound. then i’d create a new routing table (let’s say 100) with a static interface route of 0.0.0.0/0 to wg0. then i’d put the vms in a firewall group(address if it’s jus…", "name": "", "is_accepted": true } ]

[ { "text": "if you ping the ip of eth2 the reply will come from that interface. the issue you describe above is however route based. your pkg comes in on eth2 and is supposed to be route to a host via let’s say eth3. your default route goes via eth0. your host will receive that pkg and will reply, the reply com…", "name": "", "is_accepted": true } ]

[ { "text": "hi [@seanwg](/u/seanwg), i have an idea to make usernames from lua, like <interface>-<mac>, because in chap-secrets checked only the first entry.\n\nin your case, you can manually add lua file to template /usr/share/vyos/templates/accel-ppp/ipoe.config.tmpl", "name": "", "is_accepted": true } ]

[ { "text": "hi [@ddb\\_db](/u/ddb_db) ,\n\noption moved to the interface settings:\n\nset interfaces ethernet ethx ip adjust-mss xxxx\n\nset interfaces ethernet ethx ipv6 adjust-mss xxxx", "name": "", "is_accepted": true } ]

[ { "text": "hello [@jhanley](/u/jhanley), vrf support not implemented in vyos, but you can attribute for adding to network namespaces, e.g.\n\nnas-port-id=ns1/ or with interface name nas-port-id=[ns/][name]", "name": "", "is_accepted": true } ]

[ { "text": "link to the commit here:\n\n<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79e9fed460385a3d8ba0b5782e9e74405cb199b1>", "name": "", "is_accepted": true } ]

[ { "text": "i’ll close this thread in favor of the phabricator task.", "name": "", "is_accepted": true } ]

[ { "text": "please ignore this issue, the program works fine.", "name": "", "is_accepted": true } ]

[ { "text": "bug report created:\n\n<https://phabricator.vyos.net/t3393>\n\nthanks,", "name": "", "is_accepted": true } ]

[ { "text": "tested it, works well.\n\nset system login radius-server 10.1.1.50 port ‘1812’\n\nset system login radius-server 10.1.1.50 secret ‘testing123’\n\nset system login radius-server 10.1.1.50 timeout ‘30’", "name": "", "is_accepted": true } ]

[ { "text": "hello.\n\nwhite-box switches not supported at this time", "name": "", "is_accepted": true } ]

[ { "text": "re-check firewalls on all routers/default gateways.\n\nand after try to dump traffic\n\nmonitor traffic interface x", "name": "", "is_accepted": true } ]

[ { "text": "hi ken,\n\nthe most common way to make virtual routers is to install a hypervisor on the physical host, such as kvm, esxi, or another, and setup multiple vms. if you already have a hypervisor setup, just move vyos to vms. i’ve been doing that for a long time, in production as well as in labs. this way…", "name": "", "is_accepted": true } ]

[ { "text": "hello [@matzus](/u/matzus), did you try to change sequence number for rules? e.g. \nset policy route vpn rule 90 destination group network-group ‘!local-networks’\nset policy route vpn rule 90 set mark 100\nset policy route vpn rule 90 source address ‘192.168.10.0/29’\nset policy route vpn rule 100 destination group…", "name": "", "is_accepted": true } ]

[ { "text": "i didn’t mention that i was doing the upgrade 1.3 → 1.4\n\nafter i does a clean install the issue was gone.\n\nthanks for your help.", "name": "", "is_accepted": true } ]

[ { "text": "i created a bug report [t3674](https://phabricator.vyos.net/t3674)", "name": "", "is_accepted": true } ]

[ { "text": "[@dbenson](/u/dbenson) this is already known but unfortunately not yet fixed. <https://phabricator.vyos.net/t2859>", "name": "", "is_accepted": true } ]

[ { "text": "seems ipsec closeaction for peers might help <https://phabricator.vyos.net/t1780>", "name": "", "is_accepted": true } ]

[ { "text": "firewalling the vyos itself is via “local” not “in” rules. for example:-\n\nset interfaces ethernet eth1 vif 5 firewall local name ‘rulename’", "name": "", "is_accepted": true } ]

[ { "text": "hi [@mafiosa](/u/mafiosa) , username and password can be set here:\n\nset vpn l2tp remote-access authentication local-users username test password 'test’\n\ni’ve checked and connectivity were established and working in lab with vyos-1.3-rolling-202012 and routeros-x86-6.47.2:\n\nvyos lan interface eth0 - 192.168.0.1/24 …", "name": "", "is_accepted": true } ]

[ { "text": "reboot fixed it on both routers…", "name": "", "is_accepted": true } ]

[ { "text": "so, you want to use two different accounts on namecheap? still possible with a little trick: \nset service dns dynamic interface eth0 service namecheap host-name 'host1'\nset service dns dynamic interface eth0 service namecheap login 'user1'\nset service dns dynamic interface eth0 service namecheap pas…", "name": "", "is_accepted": true } ]

[ { "text": "[image]\n\n[vyos 1.2.0-rc6 is available for download](https://blog.vyos.io/vyos-1-dot-2-0-rc6-is-available-for-download)\n\nvyos 1.2.0-rc6 is available for download\n\nit currently compares the installed packages with the image build date to see it anything was additionally installed.", "name": "", "is_accepted": true } ]

[ { "text": "‘configure’ is a vyos operational mode command\n\nuser@vyos:~$ clear\n\npossible completions:\n\nconsole clear screen\n\nfirewall clear firewall statistics\n\nflow-accounting\n\nclear flow accounting\n\ninterfaces clear interface information\n\nip clear internet protocol …", "name": "", "is_accepted": true } ]

[ { "text": "well first switch to ikev2 and i bet your issue will be solved :wink:", "name": "", "is_accepted": true } ]

[ { "text": "hello [@jack9603301](/u/jack9603301) and [@fegauthier](/u/fegauthier).\n\nin this case, the preferred method setup pppoe client mtu to 1500 and face/vif mtu to 1508. one more important thing, your isp should accept/allow jumbo frames and allow on pppoe bras (broadband remote access server) mtu 1500\n\nthe second way more universal and ha…", "name": "", "is_accepted": true } ]