Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Probleme PPPoe RDS

    Scheduled Pinned Locked Moved Romanian
    23 Posts 7 Posters 13.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alextz
      last edited by

      Salut

      Am incercat cu un cablu stiut ca bun si sa inversez re0 cu re1 dar nimic nu s-a schimbat.

      pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
	inet6 fe80::5679:ba88%pppoe0 prefixlen 64 scopeid 0x7 
	inet 86.121.186.136 --> 10.0.0.1 netmask 0xffffffff 
	nd6 options=21 <performnud,auto_linklocal></performnud,auto_linklocal></up,pointopoint,running,noarp,simplex,multicast>

      placile:

      re0@pci0:1:0:0:	class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet
re1@pci0:2:0:0:	class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet
      1 Reply Last reply Reply Quote 0
      • C
        catalin
        last edited by

        deci ai 2 realtek-uri , ai avut aceasta problema din totdeauna ? sau a aparaut recent ? daca a aparut recent gandeste-te bine daca ai schimbat ceva : upgrade pfsense , driver , etc . In mare suspectez cablul , dar iti mai pot recomanda urmatoarele lucruri , relativ simple :

        • Daca ai alt cablu incearca cu el .
        • Daca ai o placa de retea la indemana incearca sa pui wan-ul pe ea pt cateva teste
        • Incearca sa setezi MTU-ul pe wan la 1480

        E destul de greu de diagnosticat aceasta problema .
        De regul din cauza conectivitatii fizice sau a unei probleme cu driverele integrate in bsd pentru anumite modele de placi sau chiar un defect hw al placii de retea .
        Pentru a exclude o problema de isp + cablu + interfata retea daca placa de retea e detasabila - incearc-o pe un alt pc de preferat un windows fa o conexiune pppoe si genereaza trafic . in acest fel daca totul e ok ramane o problema software pe pfsense .
        Asta ca sa sti in ce directie sa te indrepti cu diagnosticarea .

        Adevarul se afla dincolo de noi …

        1 Reply Last reply Reply Quote 0
        • A
          alextz
          last edited by

          Salut,

          Am facut si switch intre cele 2 placi de retea si problema persista. Am aceasta problema cu pfsense 2.2.6 si 2.3 (singurele cu care am testat).
          Cablul l-am schimbat dar o sa-l mai schimb cu inca unu known working.

          Incerc si MTU si revin.

          Placile sunt integrate pe placa de baza.

          1 Reply Last reply Reply Quote 0
          • C
            catalin
            last edited by

            eventual incearca sa bagi cablul direct in pc -ul  pe care lucrezi sa faci niste teste - ca sa excluzi isp + cablu

            Adevarul se afla dincolo de noi …

            1 Reply Last reply Reply Quote 0
            • B
              bdaniel7
              last edited by

              Salut,
              Am si eu aceeasi problema, cred, tot la RDS, fibra optica, abonamentul de "500 Mbps".
              pfSense 2.2.6 x64, placa Gigabyte GA-N3050N-D3H

              Intel(R) Celeron(R) CPU N3050 @ 1.60GHz
              Current: 1600 MHz, Max: 1601 MHz
              2 CPUs: 1 package(s) x 2 core(s)

              
re0@pci0:1:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xe000-0xe0ff mem 0x81300000-0x81300fff,0xa0100000-0xa0103fff irq 16 at device 0.0 on pci1
rgephy0: <rtl8251 1000base-t="" media="" interface="">PHY 1 on miibus0

re1@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x0c hdr=0x00
re1: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xd000-0xd0ff mem 0x81200000-0x81200fff,0xa0000000-0xa0003fff irq 17 at device 0.0 on pci2
rgephy1: <rtl8251 1000base-t="" media="" interface="">PHY 1 on miibus1</rtl8251></realtek></rtl8251></realtek> 

              
Apr 1 20:56:54	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:54	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:54	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:54	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:54	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:54	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:54	ppp: web: web is not running
Apr 1 20:56:53	ppp: process 47666 terminated
Apr 1 20:56:53	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:53	ppp: waiting for process 47666 to die...
Apr 1 20:56:53	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:52	ppp: waiting for process 47666 to die...
Apr 1 20:56:51	ppp: waiting for process 47666 to die...
Apr 1 20:56:51	ppp: [wan] IPV6CP: Close event
Apr 1 20:56:51	ppp: [wan] IPCP: Close event
Apr 1 20:56:51	ppp: [wan] IFACE: Close event
Apr 1 20:56:51	ppp: caught fatal signal TERM
Apr 1 20:56:51	ppp: process 60882 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:56:51	ppp:
Apr 1 20:56:51	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:56:47	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:47	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:56:44	ppp: [wan_link0] Link: reconnection attempt 1 in 3 seconds
Apr 1 20:56:44	ppp: [wan_link0] LCP: Down event
Apr 1 20:56:44	ppp: [wan_link0] Link: DOWN event
Apr 1 20:56:44	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:56:35	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:35	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:35	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:35	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:35	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:35	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:35	ppp: web: web is not running
Apr 1 20:56:35	ppp: process 11520 terminated
Apr 1 20:56:35	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:35	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:34	ppp: waiting for process 11520 to die...
Apr 1 20:56:33	ppp: [wan] IPV6CP: Close event
Apr 1 20:56:33	ppp: [wan] IPCP: Close event
Apr 1 20:56:33	ppp: [wan] IFACE: Close event
Apr 1 20:56:33	ppp: caught fatal signal TERM
Apr 1 20:56:33	ppp: waiting for process 11520 to die...
Apr 1 20:56:33	ppp: process 47666 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:56:33	ppp:
Apr 1 20:56:33	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:56:29	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:29	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:56:27	ppp: [wan_link0] Link: reconnection attempt 1 in 2 seconds
Apr 1 20:56:27	ppp: [wan_link0] LCP: Down event
Apr 1 20:56:27	ppp: [wan_link0] Link: DOWN event
Apr 1 20:56:27	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:56:18	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:18	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:18	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:18	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:18	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:18	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:18	ppp: web: web is not running
Apr 1 20:56:18	ppp: process 84181 terminated
Apr 1 20:56:18	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:18	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:17	ppp: waiting for process 84181 to die...
Apr 1 20:56:16	ppp: waiting for process 84181 to die...
Apr 1 20:56:16	ppp: [wan] IPV6CP: Close event
Apr 1 20:56:16	ppp: [wan] IPCP: Close event
Apr 1 20:56:16	ppp: [wan] IFACE: Close event
Apr 1 20:56:16	ppp: caught fatal signal TERM
Apr 1 20:56:16	ppp: process 11520 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:56:16	ppp:
Apr 1 20:56:16	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:56:14	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:14	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:56:10	ppp: [wan_link0] Link: reconnection attempt 1 in 4 seconds
Apr 1 20:56:10	ppp: [wan_link0] LCP: Down event
Apr 1 20:56:10	ppp: [wan_link0] Link: DOWN event
Apr 1 20:56:10	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:56:01	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:56:01	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:56:01	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:56:01	ppp: [wan_link0] LCP: Open event
Apr 1 20:56:01	ppp: [wan_link0] Link: OPEN event
Apr 1 20:56:01	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:56:01	ppp: web: web is not running
Apr 1 20:56:01	ppp: process 30022 terminated
Apr 1 20:56:01	ppp: [wan_link0] Link: Shutdown
Apr 1 20:56:01	ppp: [wan] Bundle: Shutdown
Apr 1 20:56:00	ppp: waiting for process 30022 to die...
Apr 1 20:55:59	ppp: [wan] IPV6CP: Close event
Apr 1 20:55:59	ppp: [wan] IPCP: Close event
Apr 1 20:55:59	ppp: [wan] IFACE: Close event
Apr 1 20:55:59	ppp: caught fatal signal TERM
Apr 1 20:55:59	ppp: waiting for process 30022 to die...
Apr 1 20:55:59	ppp: process 84181 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:55:59	ppp:
Apr 1 20:55:59	ppp: Multi-link PPP daemon for FreeBSD
Apr 1 20:55:55	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:55:55	ppp: [wan_link0] Link: reconnection attempt 1
Apr 1 20:55:53	ppp: [wan_link0] Link: reconnection attempt 1 in 2 seconds
Apr 1 20:55:53	ppp: [wan_link0] LCP: Down event
Apr 1 20:55:53	ppp: [wan_link0] Link: DOWN event
Apr 1 20:55:53	ppp: [wan_link0] PPPoE connection timeout after 9 seconds
Apr 1 20:55:44	ppp: [wan_link0] PPPoE: Connecting to ''
Apr 1 20:55:44	ppp: [wan_link0] LCP: LayerStart
Apr 1 20:55:44	ppp: [wan_link0] LCP: state change Initial --> Starting
Apr 1 20:55:44	ppp: [wan_link0] LCP: Open event
Apr 1 20:55:44	ppp: [wan_link0] Link: OPEN event
Apr 1 20:55:44	ppp: [wan] Bundle: Interface ng0 created
Apr 1 20:55:44	ppp: web: web is not running
Apr 1 20:55:44	ppp: process 5937 terminated
Apr 1 20:55:44	ppp: [wan_link0] Link: Shutdown
Apr 1 20:55:44	ppp: [wan] Bundle: Shutdown
Apr 1 20:55:43	ppp: waiting for process 5937 to die...
Apr 1 20:55:42	ppp: waiting for process 5937 to die...
Apr 1 20:55:42	ppp: [wan] IFACE: Rename interface pppoe0 to pppoe0
Apr 1 20:55:42	ppp: [wan] IFACE: Down event
Apr 1 20:55:41	ppp: [wan] IPV6CP: LayerDown
Apr 1 20:55:41	ppp: [wan] IPV6CP: SendTerminateReq #3
Apr 1 20:55:41	ppp: [wan] IPV6CP: state change Opened --> Closing
Apr 1 20:55:41	ppp: [wan] IPV6CP: Close event
Apr 1 20:55:41	ppp: [wan] IFACE: Removing IPv4 address from pppoe0 failed(IGNORING for now. This should be only for PPPoE friendly!): Can't assign requested address
Apr 1 20:55:41	ppp: [wan] IFACE: Delete route 0.0.0.0/0 10.0.0.1 failed: No such process
Apr 1 20:55:41	ppp: [wan] IPCP: LayerDown
Apr 1 20:55:41	ppp: [wan] IPCP: SendTerminateReq #4
Apr 1 20:55:41	ppp: [wan] IPCP: state change Opened --> Closing
Apr 1 20:55:41	ppp: [wan] IPCP: Close event
Apr 1 20:55:41	ppp: [wan] IFACE: Close event
Apr 1 20:55:41	ppp: waiting for process 5937 to die...
Apr 1 20:55:41	ppp: process 30022 started, version 5.7 (root@pfSense_RELENG_2_2_amd64_amd64-pfSense_RELENG_2_2-job-03 20:05 21-Aug-2015)
Apr 1 20:55:41	ppp:
Apr 1 20:55:41	ppp: Multi-link PPP daemon for FreeBSD

              Problema a aparut de cand am placa asta de baza (pe care am cumparat-o pentru ca are procesor incorporat si n-are nevoie de ventilator)
              si se manifesta cand creste traficul (de ex, cand testez viteza).

              1 Reply Last reply Reply Quote 0
              • A
                alextz
                last edited by

                Salut,

                E ciudat comportamentul dar eu cred ca am descoperit "problema". Daca pun powerD in Adaptive si reusesc imediat sa pierd conexiunea.
                Incearca sa pui powerD in HiAdaptive. La mine asa conexiunea e stabila de 24h deja.

                1 Reply Last reply Reply Quote 0
                • A
                  alextz
                  last edited by

                  Dupa 18h de mers OK cand am incercat un speedtest am pus conexiunea in cap imediat. Nu inteleg ce naiba se intampla….

                  1 Reply Last reply Reply Quote 0
                  • C
                    catalin
                    last edited by

                    din cate vad cei de la GB mai au un model asemanator cu probleme : GA-J1900N-D3V  - https://forum.pfsense.org/index.php?topic=73518.135 . probabil e o problema din fabricatie a placii sau a cipsetului de lan , nu stiu , cred ca ar trebui sa deschideti o solicitare catre gigabyte poate se poate rezolva cu un firmware de interfata de retea sau un patch de bios (banuiesc ca aveti ultima versiune de bios)

                    Adevarul se afla dincolo de noi …

                    1 Reply Last reply Reply Quote 0
                    • A
                      alextz
                      last edited by

                      Ultimul BIOS. E greu de crezut ca este de la Gigabyte din moment ce am aceeasi placa cu un ipfire si merge fara sa sughite de 3 zile.

                      Cred ca este o problema de drivere sau ceva in pfsense.

                      1 Reply Last reply Reply Quote 0
                      • C
                        catalin
                        last edited by

                        deci pe kernel de linux merge , perfect , o intrebare versiunea de pfsense pe care o foloseste ce versiune de freebsd are ? uname -a ?

                        –- nu mai folosesc pfsense de multa vreme / am alta solutie / folosesc insa freebsd pentru alte proiecte - care e si la baza pfsens-ului .

                        Adevarul se afla dincolo de noi …

                        1 Reply Last reply Reply Quote 0
                        • A
                          alextz
                          last edited by

                          Asta e rezultatul

                          FreeBSD pfSense.localdomain 10.3-RELEASE FreeBSD 10.3-RELEASE #5 51f8df0(RELENG_2_3): Sat Apr  2 12:32:38 CDT 2016     root@ce23-amd64-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense  amd64
                          1 Reply Last reply Reply Quote 0
                          • C
                            catalin
                            last edited by

                            vad ca are la baza freebsd 10.3 care inca nu a fost lansat … intampini aceasi problema si pe versiunile mai vechi de pfsense 2.2.x ? care sunt bazate pe editii released freebsd 10.2-px .
                            daca te pasionaeaza / ai timp poti incerca sa pui pe el un BSD Router - http://bsdrp.net/ sa vezi daca se comporta la fel , sau mai simplu chiar un freebsd 10.2 il configurezi strict ca un gateway de internet si faci niste teste - pentru a vedea daca e o pb de la pfsense sau de freebsd . de altfel in loguri nu mai gasesti nimic ? in afara de deconectarile de pppoe ? analizeaza tot /var/log/ si posteaza daca gasesti ceva util care apare in timpul deconectarilor

                            Adevarul se afla dincolo de noi …

                            1 Reply Last reply Reply Quote 0
                            • A
                              alextz
                              last edited by

                              Am incercat 2.3 pentru ca pe 2.2.6 face la fel.

                              1 Reply Last reply Reply Quote 0
                              • A
                                alextz
                                last edited by

                                Am folosit ipfire si arch linux 24h+ pentru testing si nu au nici o problema cu conectarea pe PPPoE.
                                Vad ca se plangea lumea pe forum si de un Z170N de la Gigabyte cu dual lan Intel de aceeasi problema.

                                O sa incerc cu FreeBSD 10.3 sa vad daca acolo e stabil.

                                1 Reply Last reply Reply Quote 0
                                • N
                                  nikkon
                                  last edited by

                                  pe adaptor intel nu am avut nici o probleme cu pppoe indiferent de valoarea MTU.
                                  2.2.6 a mers destul de mult…acum sunt pe 2.3 si merge perfect.
                                  folosesc I350

                                  pfsense 2.3.4 on Supermicro A1SRi-2758F + 8GB ECC + SSD

                                  Happy PfSense user :)

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    alextz
                                    last edited by

                                    Am testat si Freebsd 10.3 si totul este OK.

                                    Se pare ca pfSense chiar uraste Realtek si cu toate ca in Freebsd sau Linux totul functioneaza OK aici nu se reuseste o implementare stabila.

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      CIURI
                                      last edited by

                                      Salut ,

                                      Eu am un GA-N3150M-D3P si pot sa confirm ca pe PPPoE face figuri pe placa onboard realtek si nu e ISP devina ca aveam problema cu conexiunea de backup pe romtelecom ca am dual wan.Modemul de DSL era pe bridge mode si ma conectam PPPoE direct de pe pfsense.Inainte cand aveam placa intel onboard nici o problema.Am trecut pe IP si nat 1:1 si am rezolvat.

                                      Pe RDS am o placa de server broadcom : https://images.allyouneed.com/medias/sys_master/public/a/r/ag/50365166604513_image680x534.jpg pci 133 dar care merge si pe pci normal doar sa ai suficient spatiu si sa nu atinga nimic partea care ramane afara din slot.

                                      Am 2 placi identice si merg de ani buni pe pfsense ok deci le recomand doar o singura remarca trebuie putin ventinalte ca se incalzesc destul de tare.

                                      Parere personala evitati chipseturile de retea ieftine ca numa probleme fac la drivere.

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        CIURI
                                        last edited by

                                        Mda , am inceput si eu sa am probleme cu PPPoE-ul de la rds .De cand au mutat sandramaua pe fibra imi face figuri. Cel mai ciudat e ca aproape de fiecare data cand incarc un clip pe youtube atunci crapa.Problema apare zilnic.

                                        Am setat mtu pe 1480 , is curios daca mai face problema.Trist e ca de cand folosesc pfsense de 7-8 ani nu am avut probleme de genu …

                                        1 Reply Last reply Reply Quote 0
                                        • N
                                          nikkon
                                          last edited by

                                          nu cred ca asta va rezolva problema
                                          cred ca pica din alta cauza.

                                          pfsense 2.3.4 on Supermicro A1SRi-2758F + 8GB ECC + SSD

                                          Happy PfSense user :)

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            Pa3ot
                                            last edited by

                                            Salutare!

                                            Si eu am avut cateva probleme cu interfata de WAN unde am o conexiune PPPoE de la RDS/RCS. De fiecare data cand voiam sa torrentez ceva, imi cadea interfata si nu se putea repara decat cu reboot la firewall.
                                            Asta e firewallul: https://www.aliexpress.com/item/4000084035033.html?spm=a2g0s.9042311.0.0.f06a4c4dSsfSwv
                                            Logurile sunt identice cu cele ale lui @bdaniel7 .

                                            Mai multe detalii aici: https://forum.netgate.com/topic/132347/pppoe-wan-fails-to-reconnect-after-link-loss

                                            Ma rog, intru-un final am aflat (desi banuaim inca de la inceput) ca cei de la realtek au ceva probleme cu driverele, asa ca dupa ore de cautari am gasit solutia. Am instalat un driver updatat. Detalii si aici: https://forum.netgate.com/topic/141389/psa-realtek-network-drivers-rtl8111-in-bsd-pfsense-are-problematic

                                            In linkurile de mai jos se gasesc driverul compilat si inclusiv instructiuni cum sa il instalezi.
                                            Aici gasiti driverul plus instructiuni de instalare: https://forum.netgate.com/topic/135850/official-realtek-driver-binary-1-95-for-2-4-4-release
                                            Aici gasiti doar instructiunile pas cu pas: https://gist.github.com/jovimon/524e116471f249626fd2ccd141f3fe05
                                            Driverul e deja compilat asa ca trebuie sa incepi cu pasul 3. Am folosit putty si wiscp din windows. Va trebui sa activezi ssh pe firewall, instructiuni aici: https://www.youtube.com/watch?v=oakOE2iDkhU

                                            Dupa ce am instalat driverul se pare ca totul este in regula. Am facut cateva teste de stress si nu au mai fost probleme.

                                            B 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.