Jump to content


Photo

Vpn met xtrend et8000 en openpli 6.2

Started by Egbertjan, 17 Nov 2018 18:18

  • Please log in to reply
130 replies to this topic

Re: Vpn met xtrend et8000 en openpli 6.2 #81 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 14 January 2019 - 23:06

Geen idee, mijn glazen bol is in reparatie. ;)

 

Ik zou uit bovenstaande config in ieder geval deze regel halen:

ncp-disable

want ook die snapt de 2.3.9 client niet.

 

Dit is de config bij mijn ouders:

root@h3:~# cat /etc/openvpn/client.conf 
dev tap
tls-client
remote openvpn.example.org 443
pull
proto tcp-client
script-security 2
comp-lzo
reneg-sec 0
cipher AES-256-CBC
auth SHA256

auth-user-pass password.txt

<ca>
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
</ca>

Op een Zgemma H3 met OpenPLi 6.2, OpenVPN 2.3.9:

root@h3:~# openvpn --version
OpenVPN 2.3.9 mipsel-oe-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on May  8 2018

Mijn OpenVPN server is een Synology.

 

(p,s, ik gebruik tap interfaces ipv tun interfaces, maar dat maakt voor de rest niet uit).


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #82 littlesat

  • PLi® Core member
  • 56,272 posts

+691
Excellent

Posted 14 January 2019 - 23:35

Soms heb je idd pech in sommige hotels als ze op poort 443 dpi hebben... :( maar dan kan je eigenlijk toch alleen browseren op zo’n netwerk....:(

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W

Re: Vpn met xtrend et8000 en openpli 6.2 #83 Egbertjan

  • Senior Member
  • 499 posts

+1
Neutral

Posted 14 January 2019 - 23:42

Ik heb de oplossing denk in gevonden. Ik kwam nog een instelling tegen in pfsense waar hij voor het maken van de config file geen regels erin zet die openvpn 2.4 of hoger nodig heeft, maar werkt op 2.3 of ouder. zet ik dat aan en zet ik in de server instellingen ncp uit dan zie ik daar niks meer van terug in mijn config file. Maakt het nog uit voor de snelheid op hoeveel bit het certificaat staat ingesteld en bedoel dan voornamelijk de client kant. Ik heb nu een certificaat van 2048 bit. Mijn netgear had dit op 1024.bit staan. Ik merk wel dat een snelle i7 wel 300/300 mbit haalt en op mijn telefoon s9 via wifi maar 60/90 mbit haalt. Op een s8 is dit nog lager. 

 

Ik laat morgen even weten of het nu werkt bij mijn Oma


Edited by Egbertjan, 14 January 2019 - 23:43.

In het bezet van 2x VU+ Ultimo 4k 4TB HDD en 10TB HDD en een Vu plus duo4k SE zonder HDD .

3 Schotels met: 5w,0,8w,3e,4,8e,7e,9e,13e,16e,19,2e,23,5e,28,2e en 42e 

Ziggo Kabel.

Smartkaarten :Ziggo,Fransat ,TVR Roemenië,HD+, SRG/SSR,TNTSAT,TIVUSAT en TV Vlaanderen.

Re: Vpn met xtrend et8000 en openpli 6.2 #84 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 January 2019 - 00:48

Het certificaat is niet zo van belang, X.509 / TLS maakt gebruik van asynchrone encryptie, en dat is vrij snel. 

 

Wat meer invloed heeft op snelheid is de gebruikte cipher. Hoe meer bits daar, en hoe complexer het algoritme, hoe harder de CPU er aan moet rekenen. 


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #85 Egbertjan

  • Senior Member
  • 499 posts

+1
Neutral

Posted 15 January 2019 - 01:30

Het certificaat is niet zo van belang, X.509 / TLS maakt gebruik van asynchrone encryptie, en dat is vrij snel. 

 

Wat meer invloed heeft op snelheid is de gebruikte cipher. Hoe meer bits daar, en hoe complexer het algoritme, hoe harder de CPU er aan moet rekenen. 

Tot nu toe heel erg bedank voor je uitleg ik snap er nu al veel meer van. Ik merk dat 

 

Ik kan kiezen uit deze ciphers met aes met 128 bit key Kan jij mij zeggen welke het snelste voor de client? Ik merk dat het voor de snelheid heel erg uitmaakt met welk apparaat ik verbind met de openvpn server en dat de cpu belasting ook erg omhoog schiet op de apparaten waar ik mee verbind met mijn openvpn server. De openvpn server heeft tijdens een speedtest maximaal 15 % cpu belasting (PFSense staat ook op een quad core i7)

AES-128 cbc,cfb,cfb1,cfb8,gcm, of ofb

 

Ik kan ook andere encryptie nemen Sommige hier van kunnen ook lager dan 128 bit. Zijn die andere encryptie methoden wel veilig

 

Bijvoorbeeld 

 

Bf, camellia, cast5 des,idea,rc2,rc5 of seed


In het bezet van 2x VU+ Ultimo 4k 4TB HDD en 10TB HDD en een Vu plus duo4k SE zonder HDD .

3 Schotels met: 5w,0,8w,3e,4,8e,7e,9e,13e,16e,19,2e,23,5e,28,2e en 42e 

Ziggo Kabel.

Smartkaarten :Ziggo,Fransat ,TVR Roemenië,HD+, SRG/SSR,TNTSAT,TIVUSAT en TV Vlaanderen.

Re: Vpn met xtrend et8000 en openpli 6.2 #86 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 January 2019 - 11:13

Alles lager dan AES-256 is strikt genomen niet meer veilig. De vraag is wie er geinteresseerd is meekijken wat oma over de tunnel doet.

 

Het is ook van belang wat je door de tunnel wilt doen. Is dat remote support, dan is dit een non-discussie. Is dat streaming, dan wil je zo min mogelijk overhead hebben.

 

De H3 is met AES-256 snel genoeg om een 3Mbps transcoded stream over internet door te kijken (zo kan ik bij mijn ouders TV kijken via mijn box), voor onderweg doe ik het met een VU Zero met dezelfde config.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #87 Pippin

  • Senior Member
  • 103 posts

+2
Neutral

Posted 15 January 2019 - 17:02

OpenVPN is een eigen protocol, geen SSL/TLS, ook al maakt het gebruik van TLS.

Wireshark herkent dan ook gewoon OpenVPN verkeer (oudere versies kunnen het als het google quic protocol identificeren).

 

--cipher AES-128-CBC en --auth SHA1 zijn daarom nog steeds veilig voor OpenVPN. Het advies vanuit OpenVPN is echter AES-128-CBC met SHA256 mede om vragen van gebruikers te voorkomen.

De server is zodanig met NCP (welke standaard AES-128-GCM of AES-256-GCM zal selecteren indien ondersteund door de client) te configureren zodat oudere versies, pre 2.4, compatible blijven.

 

Altijd --tls-auth gebruiken.

 

Compressie uitschakelen i.v.m. Voracle attack. Compressie heeft meestal toch geen zin want veel verkeer is reeds gecomprimeerd en waarom CPU cycles weggooien want compressie voegt ten alle tijden tenminste 1 byte per packet toe.

 

Manual,

2.3: https://community.op...penvpn23ManPage

2.4: https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage


Edited by Pippin, 15 January 2019 - 17:03.

Today's scientists have substituted mathematics for experiments, and they wander off through equation after equation, and eventually build a structure which has no relation to reality. Nikola Tesla

Re: Vpn met xtrend et8000 en openpli 6.2 #88 Erik Slagter

  • PLi® Core member
  • 46,960 posts

+541
Excellent

Posted 15 January 2019 - 18:53

Wij zijn "bekend" met OpenVPN ;) Het is wel degelijk TLS, maar geen "SSL / TLS VPN" zoals dat vaak als benaming gebruikt wordt voor een veilige remote desktop, dat is heel iets anders, dat is echt gewoon https, wat OpenVPN niet is.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: Vpn met xtrend et8000 en openpli 6.2 #89 Egbertjan

  • Senior Member
  • 499 posts

+1
Neutral

Posted 15 January 2019 - 19:23

Het werkt helaas nog niet.

 

Jan  1 01:00:17 et8000 syslog.info syslogd started: BusyBox v1.24.1
Jan  1 01:00:17 et8000 user.notice kernel: klogd started: BusyBox v1.24.1 (2018-05-08 13:39:50 CEST)
Jan  1 01:00:17 et8000 user.info kernel: [    0.054000] workingset: timestamp_bits=14 max_order=17 bucket_order=3
Jan  1 01:00:17 et8000 user.notice kernel: [    0.055000] NFS: Registering the id_resolver key type
Jan  1 01:00:17 et8000 user.notice kernel: [    0.055000] Key type id_resolver registered
Jan  1 01:00:17 et8000 user.notice kernel: [    0.055000] Key type id_legacy registered
Jan  1 01:00:17 et8000 user.info kernel: [    0.055000] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jan  1 01:00:17 et8000 user.info kernel: [    0.055000] Installing knfsd (copyright © 1996 okir@monad.swb.de).
Jan  1 01:00:17 et8000 user.info kernel: [    0.055000] fuse init (API version 7.26)
Jan  1 01:00:17 et8000 user.info kernel: [    0.061000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Jan  1 01:00:17 et8000 user.info kernel: [    0.061000] io scheduler noop registered
Jan  1 01:00:17 et8000 user.info kernel: [    0.061000] io scheduler cfq registered (default)
Jan  1 01:00:17 et8000 user.info kernel: [    0.061000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jan  1 01:00:17 et8000 user.info kernel: [    0.062000] serial8250.0: ttyS0 at MMIO 0x10406700 (irq = 52, base_baud = 5062500) is a 16550A
Jan  1 01:00:17 et8000 user.info kernel: [    0.062000] serial8250.0: ttyS1 at MMIO 0x10406740 (irq = 53, base_baud = 5062500) is a 16550A
Jan  1 01:00:17 et8000 user.info kernel: [    0.063000] serial8250.0: ttyS2 at MMIO 0x10406780 (irq = 54, base_baud = 5062500) is a 16550A
Jan  1 01:00:17 et8000 user.info kernel: [    0.069000] loop: module loaded
Jan  1 01:00:17 et8000 user.info kernel: [    0.069000] ahci ahci.0: SSS flag set, parallel bus scan disabled
Jan  1 01:00:17 et8000 user.info kernel: [    0.079000] ahci ahci.0: AHCI 0001.0300 32 slots 3 ports 6 Gbps 0x3 impl platform mode
Jan  1 01:00:17 et8000 user.info kernel: [    0.079000] ahci ahci.0: flags: ncq sntf stag clo pmp slum part 
Jan  1 01:00:17 et8000 user.info kernel: [    0.084000] scsi host0: ahci
Jan  1 01:00:17 et8000 user.info kernel: [    0.084000] scsi host1: ahci
Jan  1 01:00:17 et8000 user.info kernel: [    0.085000] scsi host2: ahci
Jan  1 01:00:17 et8000 user.notice kernel: [    0.085000] ata1: FORCE: PHY spd limit set to 3.0Gbps
Jan  1 01:00:17 et8000 user.info kernel: [    0.085000] ata1: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x100 irq 33
Jan  1 01:00:17 et8000 user.notice kernel: [    0.085000] ata2: FORCE: PHY spd limit set to 3.0Gbps
Jan  1 01:00:17 et8000 user.info kernel: [    0.085000] ata2: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x180 irq 33
Jan  1 01:00:17 et8000 user.info kernel: [    0.085000] ata3: DUMMY
Jan  1 01:00:17 et8000 user.info kernel: [    0.085000] brcmstb_nand: NAND controller driver is loaded
Jan  1 01:00:17 et8000 user.info kernel: [    0.086000] libphy: Fixed MDIO Bus: probed
Jan  1 01:00:17 et8000 user.debug kernel: [    0.086000] __clk_enable: network [1]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.086000] bcm7429_pm_network_enable 00
Jan  1 01:00:17 et8000 user.debug kernel: [    0.086000] __clk_enable: enet [1]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.086000] bcm40nm_pm_genet_enable 00
Jan  1 01:00:17 et8000 user.info kernel: [    0.088000] bcmgenet: configuring instance #0 for external RGMII
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] __clk_disable: enet [0]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] bcm40nm_pm_genet_disable 00
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] __clk_disable: network [0]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] bcm7429_pm_network_disable 00
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] __clk_enable: network [1]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] bcm7429_pm_network_enable 00
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] __clk_enable: moca_genet [1]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] bcm40nm_pm_genet1_enable 00
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] __clk_enable: moca [1]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.088000] bcm40nm_pm_moca_enable 00
Jan  1 01:00:17 et8000 user.info kernel: [    0.398000] ata1: SATA link down (SStatus 0 SControl 320)
Jan  1 01:00:17 et8000 user.err kernel: [    0.408000] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen
Jan  1 01:00:17 et8000 user.err kernel: [    0.408000] ata1: irq_stat 0x00000040, connection status changed
Jan  1 01:00:17 et8000 user.err kernel: [    0.408000] ata1: SError: { DevExch }
Jan  1 01:00:17 et8000 user.info kernel: [    0.408000] ata1: hard resetting link
Jan  1 01:00:17 et8000 user.err kernel: [    0.443000] No PHY detected, not registering interface:1
Jan  1 01:00:17 et8000 user.debug kernel: [    0.443000] __clk_disable: moca [0]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.443000] bcm40nm_pm_moca_disable 00
Jan  1 01:00:17 et8000 user.debug kernel: [    0.443000] __clk_disable: moca_genet [0]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.443000] bcm40nm_pm_genet1_disable 00
Jan  1 01:00:17 et8000 user.debug kernel: [    0.443000] __clk_disable: network [0]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.443000] bcm7429_pm_network_disable 00
Jan  1 01:00:17 et8000 user.warn kernel: [    0.451000] bcmgenet: probe of bcmgenet.1 failed with error -5
Jan  1 01:00:17 et8000 user.info kernel: [    0.451000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan  1 01:00:17 et8000 user.debug kernel: [    0.451000] __clk_enable: usb [1]
Jan  1 01:00:17 et8000 user.debug kernel: [    0.451000] bcm40nm_pm_usb_enable 00
Jan  1 01:00:17 et8000 user.info kernel: [    0.451000] ehci-brcm ehci-brcm.0: Broadcom STB EHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.451000] ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
Jan  1 01:00:17 et8000 user.info kernel: [    0.461000] ehci-brcm ehci-brcm.0: irq 56, io mem 0x10480300
Jan  1 01:00:17 et8000 user.info kernel: [    0.468000] ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
Jan  1 01:00:17 et8000 user.info kernel: [    0.468000] hub 1-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.468000] hub 1-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.468000] ehci-brcm ehci-brcm.1: Broadcom STB EHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.468000] ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
Jan  1 01:00:17 et8000 user.info kernel: [    0.479000] ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
Jan  1 01:00:17 et8000 user.info kernel: [    0.486000] ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
Jan  1 01:00:17 et8000 user.info kernel: [    0.486000] hub 2-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.486000] hub 2-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.486000] ehci-brcm ehci-brcm.2: Broadcom STB EHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.486000] ehci-brcm ehci-brcm.2: new USB bus registered, assigned bus number 3
Jan  1 01:00:17 et8000 user.info kernel: [    0.497000] ehci-brcm ehci-brcm.2: irq 61, io mem 0x10490300
Jan  1 01:00:17 et8000 user.info kernel: [    0.504000] ehci-brcm ehci-brcm.2: USB 0.0 started, EHCI 1.00
Jan  1 01:00:17 et8000 user.info kernel: [    0.504000] hub 3-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.504000] hub 3-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.504000] ehci-brcm ehci-brcm.3: Broadcom STB EHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.504000] ehci-brcm ehci-brcm.3: new USB bus registered, assigned bus number 4
Jan  1 01:00:17 et8000 user.info kernel: [    0.515000] ehci-brcm ehci-brcm.3: irq 62, io mem 0x10490500
Jan  1 01:00:17 et8000 user.info kernel: [    0.522000] ehci-brcm ehci-brcm.3: USB 0.0 started, EHCI 1.00
Jan  1 01:00:17 et8000 user.info kernel: [    0.522000] hub 4-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.522000] hub 4-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.522000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan  1 01:00:17 et8000 user.info kernel: [    0.522000] ohci-brcm ohci-brcm.0: Broadcom STB OHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.523000] ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 5
Jan  1 01:00:17 et8000 user.info kernel: [    0.523000] ohci-brcm ohci-brcm.0: irq 58, io mem 0x10480400
Jan  1 01:00:17 et8000 user.info kernel: [    0.589000] hub 5-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.589000] hub 5-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.589000] ohci-brcm ohci-brcm.1: Broadcom STB OHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.589000] ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 6
Jan  1 01:00:17 et8000 user.info kernel: [    0.590000] ohci-brcm ohci-brcm.1: irq 59, io mem 0x10480600
Jan  1 01:00:17 et8000 user.info kernel: [    0.656000] hub 6-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.656000] hub 6-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.657000] ohci-brcm ohci-brcm.2: Broadcom STB OHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.657000] ohci-brcm ohci-brcm.2: new USB bus registered, assigned bus number 7
Jan  1 01:00:17 et8000 user.info kernel: [    0.657000] ohci-brcm ohci-brcm.2: irq 63, io mem 0x10490400
Jan  1 01:00:17 et8000 user.info kernel: [    0.710000] ata2: SATA link down (SStatus 0 SControl 320)
Jan  1 01:00:17 et8000 user.info kernel: [    0.723000] hub 7-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.723000] hub 7-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.723000] ohci-brcm ohci-brcm.3: Broadcom STB OHCI
Jan  1 01:00:17 et8000 user.info kernel: [    0.724000] ohci-brcm ohci-brcm.3: new USB bus registered, assigned bus number 8
Jan  1 01:00:17 et8000 user.info kernel: [    0.724000] ohci-brcm ohci-brcm.3: irq 64, io mem 0x10490600
Jan  1 01:00:17 et8000 user.info kernel: [    0.790000] hub 8-0:1.0: USB hub found
Jan  1 01:00:17 et8000 user.info kernel: [    0.790000] hub 8-0:1.0: 1 port detected
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] usbcore: registered new interface driver usb-storage
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] mousedev: PS/2 mouse device common for all mice
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] i2c /dev entries driver
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] usbcore: registered new interface driver btusb
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] sdhci: Secure Digital Host Controller Interface driver
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] sdhci: Copyright© Pierre Ossman
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] sdhci-pltfm: SDHCI platform and OF driver helper
Jan  1 01:00:17 et8000 user.info kernel: [    0.791000] sdhci-brcmstb sdhci-brcmstb.0: Enabling controller
Jan  1 01:00:17 et8000 user.warn kernel: [    0.792000] mmc0: Failed to set 32-bit DMA mask.
Jan  1 01:00:17 et8000 user.warn kernel: [    0.792000] mmc0: No suitable DMA available - falling back to PIO
Jan  1 01:00:17 et8000 user.info kernel: [    0.825000] mmc0: SDHCI controller on sdhci-brcmstb.0 [sdhci-brcmstb.0] using PIO
Jan  1 01:00:17 et8000 user.info kernel: [    0.825000] sdhci-brcmstb sdhci-brcmstb.1: Disabled by bootloader
Jan  1 01:00:17 et8000 user.info kernel: [    0.825000] hidraw: raw HID events driver © Jiri Kosina
Jan  1 01:00:17 et8000 user.info kernel: [    0.825000] usbcore: registered new interface driver usbhid
Jan  1 01:00:17 et8000 user.info kernel: [    0.825000] usbhid: USB HID core driver
Jan  1 01:00:17 et8000 user.info kernel: [    0.826000] NET: Registered protocol family 17
Jan  1 01:00:17 et8000 user.info kernel: [    0.826000] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Jan  1 01:00:17 et8000 user.info kernel: [    0.826000] Bluetooth: HIDP socket layer initialized
Jan  1 01:00:17 et8000 user.notice kernel: [    0.827000] Key type dns_resolver registered
Jan  1 01:00:17 et8000 user.info kernel: [    0.827000] PM: CP0 COUNT/COMPARE frequency does not depend on divisor
Jan  1 01:00:17 et8000 user.info kernel: [    0.828000] EBI CS1: setting up NAND flash (primary)
Jan  1 01:00:17 et8000 user.info kernel: [    0.828000] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xdc
Jan  1 01:00:17 et8000 user.info kernel: [    0.828000] nand: Samsung NAND 512MiB 3,3V 8-bit
Jan  1 01:00:17 et8000 user.info kernel: [    0.828000] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Jan  1 01:00:17 et8000 user.info kernel: [    0.828000] brcmnand brcmnand.0: 512MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, BCH-4
Jan  1 01:00:17 et8000 user.info kernel: [    0.828000] 
Jan  1 01:00:17 et8000 user.info kernel: [    0.828000] Bad block table found at page 262080, version 0x01
Jan  1 01:00:17 et8000 user.info kernel: [    0.829000] Bad block table found at page 262016, version 0x01
Jan  1 01:00:17 et8000 user.info kernel: [    0.829000] nand_read_bbt: bad block at 0x000000580000
Jan  1 01:00:17 et8000 user.info kernel: [    0.829000] nand_read_bbt: bad block at 0x000005380000
Jan  1 01:00:17 et8000 user.info kernel: [    0.829000] nand_read_bbt: bad block at 0x00000cbe0000
Jan  1 01:00:17 et8000 user.info kernel: [    0.829000] nand_read_bbt: bad block at 0x000016a00000
Jan  1 01:00:17 et8000 user.info kernel: [    0.829000] nand_read_bbt: bad block at 0x00001db00000
Jan  1 01:00:17 et8000 user.info kernel: [    0.829000] nand_read_bbt: bad block at 0x00001df20000
Jan  1 01:00:17 et8000 user.notice kernel: [    0.829000] Creating 3 MTD partitions on "brcmnand.0":
Jan  1 01:00:17 et8000 user.notice kernel: [    0.830000] 0x000000000000-0x000020000000 : "complete"
Jan  1 01:00:17 et8000 user.notice kernel: [    0.833000] 0x000000000000-0x000000600000 : "kernel"
Jan  1 01:00:17 et8000 user.notice kernel: [    0.834000] 0x000000600000-0x000020000000 : "rootfs"
Jan  1 01:00:17 et8000 user.info kernel: [    0.837000] EBI CS0: setting up SPI flash
Jan  1 01:00:17 et8000 user.warn kernel: [    0.838000] brcm_setup_spi_flash: can't locate SPI master
Jan  1 01:00:17 et8000 user.warn kernel: [    0.838000] brcm_setup_cs: can't register SPI flash (error -19)
Jan  1 01:00:17 et8000 user.notice kernel: [    0.838000] ubi0: default fastmap pool size: 200
Jan  1 01:00:17 et8000 user.notice kernel: [    0.838000] ubi0: default fastmap WL pool size: 100
Jan  1 01:00:17 et8000 user.notice kernel: [    0.838000] ubi0: attaching mtd2
Jan  1 01:00:17 et8000 user.notice kernel: [    1.107000] ubi0: attached by fastmap
Jan  1 01:00:17 et8000 user.notice kernel: [    1.107000] ubi0: fastmap pool size: 200
Jan  1 01:00:17 et8000 user.notice kernel: [    1.107000] ubi0: fastmap WL pool size: 100
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: attached mtd2 (name "rootfs", size 506 MiB)
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: good PEBs: 4039, bad PEBs: 9, corrupted PEBs: 0
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1428988142
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: available PEBs: 0, total reserved PEBs: 4039, PEBs reserved for bad PEB handling: 71
Jan  1 01:00:17 et8000 user.notice kernel: [    1.119000] ubi0: background thread "ubi_bgt0d" started, PID 87
Jan  1 01:00:17 et8000 user.info kernel: [    1.119000] ALSA device list:
Jan  1 01:00:17 et8000 user.info kernel: [    1.119000]   No soundcards found.
Jan  1 01:00:17 et8000 user.err kernel: [    1.119000] Warning: unable to open an initial console.
Jan  1 01:00:17 et8000 user.notice kernel: [    1.120000] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 88
Jan  1 01:00:17 et8000 user.notice kernel: [    1.159000] UBIFS (ubi0:0): recovery needed
Jan  1 01:00:17 et8000 user.info kernel: [    1.164000] usb 8-1: new full-speed USB device number 2 using ohci-brcm
Jan  1 01:00:17 et8000 user.info kernel: [    1.296000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan  1 01:00:17 et8000 user.info kernel: [    1.302000] ata1.00: ATA-7: SAMSUNG HD322HJ, 1AC01118, max UDMA7
Jan  1 01:00:17 et8000 user.info kernel: [    1.302000] ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
Jan  1 01:00:17 et8000 user.info kernel: [    1.308000] ata1.00: configured for UDMA/133
Jan  1 01:00:17 et8000 user.info kernel: [    1.308000] ata1: EH complete
Jan  1 01:00:17 et8000 user.notice kernel: [    1.309000] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD322HJ  1118 PQ: 0 ANSI: 5
Jan  1 01:00:17 et8000 user.notice kernel: [    1.317000] sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan  1 01:00:17 et8000 user.notice kernel: [    1.318000] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
Jan  1 01:00:17 et8000 user.notice kernel: [    1.318000] sd 0:0:0:0: [sda] Write Protect is off
Jan  1 01:00:17 et8000 user.debug kernel: [    1.318000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan  1 01:00:17 et8000 user.notice kernel: [    1.318000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan  1 01:00:17 et8000 user.info kernel: [    1.321000]  sda: sda1
Jan  1 01:00:17 et8000 user.notice kernel: [    1.322000] sd 0:0:0:0: [sda] Attached SCSI disk
Jan  1 01:00:17 et8000 user.notice kernel: [    1.388000] UBIFS (ubi0:0): recovery completed
Jan  1 01:00:17 et8000 user.notice kernel: [    1.389000] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
Jan  1 01:00:17 et8000 user.notice kernel: [    1.389000] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jan  1 01:00:17 et8000 user.notice kernel: [    1.389000] UBIFS (ubi0:0): FS size: 501682176 bytes (478 MiB, 3951 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
Jan  1 01:00:17 et8000 user.notice kernel: [    1.389000] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
Jan  1 01:00:17 et8000 user.notice kernel: [    1.389000] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID 204EDFB5-70D2-4291-B44B-4FDD3463F7B6, small LPT model
Jan  1 01:00:17 et8000 user.info kernel: [    1.390000] VFS: Mounted root (ubifs filesystem) on device 0:12.
Jan  1 01:00:17 et8000 user.info kernel: [    1.392000] devtmpfs: mounted
Jan  1 01:00:17 et8000 user.info kernel: [    1.392000] Freeing unused kernel memory: 284K
Jan  1 01:00:17 et8000 user.warn kernel: [    1.392000] This architecture does not have kernel memory protection.
Jan  1 01:00:17 et8000 user.notice kernel: [    1.570000] random: crng init done
Jan  1 01:00:17 et8000 user.info kernel: [    2.093000] EXT4-fs (sda1): recovery complete
Jan  1 01:00:17 et8000 user.info kernel: [    2.115000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Jan  1 01:00:17 et8000 user.warn kernel: [    2.260000] tpm: loading out-of-tree module taints kernel.
Jan  1 01:00:17 et8000 user.info kernel: [    2.264000] usbcore: registered new interface driver tpm
Jan  1 01:00:17 et8000 user.warn kernel: [    5.318000] dvb: module_layout: kernel tainted.
Jan  1 01:00:17 et8000 user.warn kernel: [    5.318000] Disabling lock debugging due to kernel taint
Jan  1 01:00:17 et8000 user.info kernel: [    7.915000] input: dreambox remote control (native) as /devices/virtual/input/input0
Jan  1 01:00:17 et8000 user.info kernel: [    7.916000] input: dreambox advanced remote control (native) as /devices/virtual/input/input1
Jan  1 01:00:17 et8000 user.info kernel: [    7.990000] dvbdev: DVB: registering new adapter (dvb0)
Jan  1 01:00:17 et8000 user.info kernel: [    7.992000] platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-C)...
Jan  1 01:00:17 et8000 user.info kernel: [    8.330000] input: front panel as /devices/virtual/input/input2
Jan  1 01:00:17 et8000 user.info kernel: [    9.028000] Registered IR keymap rc-cec
Jan  1 01:00:17 et8000 user.info kernel: [    9.029000] input: RC for hdmi_cec as /devices/platform/hdmi.0/rc/rc0/input3
Jan  1 01:00:17 et8000 user.info kernel: [    9.029000] rc rc0: RC for hdmi_cec as /devices/platform/hdmi.0/rc/rc0
Jan  1 01:00:17 et8000 user.debug kernel: [   10.745000] __clk_enable: network [1]
Jan  1 01:00:17 et8000 user.debug kernel: [   10.745000] bcm7429_pm_network_enable 00
Jan  1 01:00:17 et8000 user.debug kernel: [   10.745000] __clk_enable: enet [1]
Jan  1 01:00:17 et8000 user.debug kernel: [   10.745000] bcm40nm_pm_genet_enable 00
Jan  1 01:00:17 et8000 user.info kernel: [   10.846000] bcmgenet bcmgenet.0 eth0: link up, 1000 Mbps, full duplex
Jan  1 01:00:17 et8000 user.info kernel: [   14.596000] NET: Registered protocol family 10
Jan  1 01:00:17 et8000 user.info kernel: [   14.602000] Segment Routing with IPv6
Jan  1 01:00:17 et8000 user.info kernel: [   14.858000] tun: Universal TUN/TAP device driver, 1.6
Jan  1 01:00:17 et8000 user.info kernel: [   14.859000] tun: © 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Found user 'avahi' (UID 996) and group 'avahi' (GID 995).
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Successfully dropped root privileges.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: avahi-daemon 0.6.32 starting up.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Successfully called chroot().
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Successfully dropped remaining capabilities.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Loading service file /services/sftp-ssh.service.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Loading service file /services/ssh.service.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::216:b4ff:fe06:1a5.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: New relevant interface eth0.IPv6 for mDNS.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.12.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: New relevant interface eth0.IPv4 for mDNS.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Network interface enumeration completed.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Registering new address record for fe80::216:b4ff:fe06:1a5 on eth0.*.
Jan  1 01:00:17 et8000 daemon.info avahi-daemon[513]: Registering new address record for 192.168.178.12 on eth0.IPv4.
Jan  1 01:00:18 et8000 daemon.info avahi-daemon[513]: Server startup complete. Host name is et8000.local. Local service cookie is 3742332384.
Jan  1 01:00:19 et8000 daemon.info avahi-daemon[513]: Service "et8000" (/services/ssh.service) successfully established.
Jan  1 01:00:19 et8000 daemon.info avahi-daemon[513]: Service "et8000" (/services/sftp-ssh.service) successfully established.
Jan 15 19:19:31 et8000 authpriv.warn login[1374]: pam_lastlog(login:session): file /var/log/lastlog created
Jan 15 19:19:31 et8000 authpriv.info login[1374]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Jan 15 19:19:31 et8000 authpriv.notice login[1410]: ROOT LOGIN  on '/dev/pts/0' from '192.168.178.23:52517'
Jan 15 19:19:38 et8000 daemon.err openvpn[1437]: Options error: You must define TUN/TAP device (--dev)
Jan 15 19:19:38 et8000 daemon.warn openvpn[1437]: Use --help for more information.
 
dit staat er nu in mijn log. Ik heb het ook nog geprobeerd te starten via telnet werkte helaas niet. Wie kan mij vertellen wat er fout gaat?
 
Dit is mijn client3.conf
persist-tun
persist-key
cipher AES-256-CBC
auth SHA256
tls-client
client
remote mijn ip adres 443 udp
verify-x509-name "OpenVPN-ServerCert" name
auth-user-pass /etc/openvpn/userpass.txt
remote-cert-tls server
 
<ca>
-----BEGIN CERTIFICATE-----
xxxxxxx
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
xxxxxxxx
-----END PRIVATE KEY-----
</key>
key-direction 1
<tls-auth>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
xxxx
-----END OpenVPN Static key V1-----
</tls-auth>
 

In het bezet van 2x VU+ Ultimo 4k 4TB HDD en 10TB HDD en een Vu plus duo4k SE zonder HDD .

3 Schotels met: 5w,0,8w,3e,4,8e,7e,9e,13e,16e,19,2e,23,5e,28,2e en 42e 

Ziggo Kabel.

Smartkaarten :Ziggo,Fransat ,TVR Roemenië,HD+, SRG/SSR,TNTSAT,TIVUSAT en TV Vlaanderen.

Re: Vpn met xtrend et8000 en openpli 6.2 #90 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 January 2019 - 19:35

Het heeft weinig zin om elke keer zo'n hele lap log te posten als daar geen enkele openvpn regel in staat...

 

Volgens mij start openvpn dus niet eens. Wat is de output van

/etc/init.d/openvpn start

?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #91 Egbertjan

  • Senior Member
  • 499 posts

+1
Neutral

Posted 15 January 2019 - 19:38

Dit krijg ik van telnet als ik hem wil starten.

 

et8000 login: root
Password:
Last login: Tue Jan 15 19:19:31 CET 2019 on pts/0
root@et8000:~# /etc/init.d/openvpn start
Starting openvpn: FAILED-> client3.
root@et8000:~#

In het bezet van 2x VU+ Ultimo 4k 4TB HDD en 10TB HDD en een Vu plus duo4k SE zonder HDD .

3 Schotels met: 5w,0,8w,3e,4,8e,7e,9e,13e,16e,19,2e,23,5e,28,2e en 42e 

Ziggo Kabel.

Smartkaarten :Ziggo,Fransat ,TVR Roemenië,HD+, SRG/SSR,TNTSAT,TIVUSAT en TV Vlaanderen.

Re: Vpn met xtrend et8000 en openpli 6.2 #92 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 January 2019 - 19:50

Start hem eens direct op:

/usr/sbin/openvpn --daemon --writepid /var/run/openvpn.client3.pid --verb 5 --config /etc/openvpn/client3.conf --cd /etc/openvpn --log /var/log/openvpn.log

dan weet je ook zeker dat de log naar de juiste file gaat.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #93 Egbertjan

  • Senior Member
  • 499 posts

+1
Neutral

Posted 15 January 2019 - 19:59

/usr/sbin/openvpn --daemon --writepid /var/run/openvpn.client3.pid --verb 5 --config /etc/openvpn/client3.conf --cd /etc/openvpn --log /var/log/openvpn.log

 

Wil je dat ik dit commando ga uitvoeren via telnet?


In het bezet van 2x VU+ Ultimo 4k 4TB HDD en 10TB HDD en een Vu plus duo4k SE zonder HDD .

3 Schotels met: 5w,0,8w,3e,4,8e,7e,9e,13e,16e,19,2e,23,5e,28,2e en 42e 

Ziggo Kabel.

Smartkaarten :Ziggo,Fransat ,TVR Roemenië,HD+, SRG/SSR,TNTSAT,TIVUSAT en TV Vlaanderen.

Re: Vpn met xtrend et8000 en openpli 6.2 #94 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 January 2019 - 20:52

Ja, graag. Ik ben benieuwd of dat wat zegt, en of er dat wat in /var/log/openvpn.log komt...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #95 Pippin

  • Senior Member
  • 103 posts

+2
Neutral

Posted 15 January 2019 - 21:10

Het zal zeggen: Options error: You must define TUN/TAP device (--dev)

 

Teveel gerommeld, opnieuw via Client Export Package exporteren in pfSense.


Edited by Pippin, 15 January 2019 - 21:11.

Today's scientists have substituted mathematics for experiments, and they wander off through equation after equation, and eventually build a structure which has no relation to reality. Nikola Tesla

Re: Vpn met xtrend et8000 en openpli 6.2 #96 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 January 2019 - 21:11

Er ontbreekt inderdaad een "dev tun". Maar dat verklaart nog niet waarom er helemaal geen logging is, ook niet van die foutmelding. Dat maakt zoeken wel lastig.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #97 Pippin

  • Senior Member
  • 103 posts

+2
Neutral

Posted 15 January 2019 - 21:57

Jawel hoor:

 

Jan 15 19:19:38 et8000 daemon.err openvpn[1437]: Options error: You must define TUN/TAP device (--dev)
Jan 15 19:19:38 et8000 daemon.warn openvpn[1437]: Use --help for more information.
;)

Today's scientists have substituted mathematics for experiments, and they wander off through equation after equation, and eventually build a structure which has no relation to reality. Nikola Tesla

Re: Vpn met xtrend et8000 en openpli 6.2 #98 WanWizard

  • PLi® Core member
  • 68,598 posts

+1,739
Excellent

Posted 15 January 2019 - 22:01

Hmm.... Brein wil al een tijdje niet meer, nu gaan ook mijn ogen er aan... :(

 

Die is inderdaad wel erg duidelijk, ja. Zowat het meest belangrijke directief, hoe die nu weg kan zijn?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: Vpn met xtrend et8000 en openpli 6.2 #99 Egbertjan

  • Senior Member
  • 499 posts

+1
Neutral

Posted 15 January 2019 - 23:52

Ik wil jullie tot nu toe erg bedanken allemaal voor de hulp. Ik heb in PFsene bij het exporteren van de config file al een optie gevonden dat hij dev tun er bij zet in de config file in. Bij openvpn connect op android en openvpn voor windows 10 kan het blijkbaar zonder die regel. Ik laat jullie morgen weten of het werkt bij mijn oma.  :)


Edited by Egbertjan, 15 January 2019 - 23:53.

In het bezet van 2x VU+ Ultimo 4k 4TB HDD en 10TB HDD en een Vu plus duo4k SE zonder HDD .

3 Schotels met: 5w,0,8w,3e,4,8e,7e,9e,13e,16e,19,2e,23,5e,28,2e en 42e 

Ziggo Kabel.

Smartkaarten :Ziggo,Fransat ,TVR Roemenië,HD+, SRG/SSR,TNTSAT,TIVUSAT en TV Vlaanderen.

Re: Vpn met xtrend et8000 en openpli 6.2 #100 Sagitarius †

  • Senior Member
  • 4,735 posts

+78
Good

Posted 16 January 2019 - 12:24

Ik wil jullie tot nu toe erg bedanken allemaal voor de hulp. Ik heb in PFsene bij het exporteren van de config file al een optie gevonden dat hij dev tun er bij zet in de config file in. Bij openvpn connect op android en openvpn voor windows 10 kan het blijkbaar zonder die regel. Ik laat jullie morgen weten of het werkt bij mijn oma.  :)

Oma mag wel blij zijn met zo'n kleinzoon :-)


73's

PE1AQZ

Back to [NL] Gebruikersondersteuning

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Forums
  2. → PLi® Support
  3. → [NL] Gebruikersondersteuning