DD-Wrt and Cyberghost

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Advanced Networking
Goto page Previous  1, 2, 3  Next
Author Message
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 4411
Location: Netherlands

PostPosted: Sat May 25, 2019 7:52    Post subject: Reply with quote
I am pretty sure you have to enable NAT
But that should be in the cyberghost instructions

_________________
Routers:Netgear R7800, Netgear R6400v1, Netgear R6400v2, Linksys EA6900 (XvortexCFE), Linksys E2000 (converted WRT320N), WRT54GS v1.
Install guide Linksys EA6900: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=291230
OpenVPN Policy Based Routing guide: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=321686
Install guide R6400v2:http://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
OpenVPN Server Setup:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=318795
Install guide R7800: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Wireguard Setup guide:https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1183135
Sponsor
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 9:24    Post subject: Reply with quote
Oke thank you,

NAT has now been enabled, even though in the cyberghost setup i wasn't enabled. never the less it doesn't make a difference, unfortunately.

Matt

ps. i don't see my screenshots anymore?
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 8034

PostPosted: Sat May 25, 2019 12:10    Post subject: Reply with quote
Btw, usually better to start a new thread than revive an old one. If you think something in other threads are relevant, just provides links in the new thread.

Would help in this case to see the syslog. That's very useful for diagnostic purposes.

Also, I checked out the Cyberghost dd-wrt setup page, and it does say NAT disabled. A bit unusual, but that could work if the server NAT's the tunnel on their end before the traffic gets dumped on their local network. But it never hurts to NAT your end of the tunnel anyway, esp. given that most OpenVPN providers require it. Even if NAT was required, you would still be able to access the tunnel and use it from a shell (telnet/ssh) on the router (e.g., ping an IP address, either explicitly or domain name). NAT is only an issue for local clients behind the router.

So I would go to a shell on the router and see if you can do either of the following successfully.

Code:
ping 8.8.8.8


Code:
ping cnn.com


If you can do the first but not the second, that usually means you're connected, but have a DNS problem.

_________________
DD-WRT: DNS Leak Detection w/ VPNs (updated 6/5/19)
NEW SCRIPT!: ddwrt-mount-usb-drives.sh
NEW SCRIPT!: ddwrt-blacklist-domains.sh
NEW SCRIPT!: ddwrt-ovpn-remote-access.sh
NEW SCRIPT!: ddwrt-pptp-policy-based-routing.sh
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 12:34    Post subject: Reply with quote
thank you for your comments, i will take that in account.

reply on ping 8.8.8.8: (with NAT enabled)

PING 8.8.8.8 (8.8.8.Cool: 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=56 time=149.775 ms
64 bytes from 8.8.8.8: seq=1 ttl=56 time=14.267 ms
64 bytes from 8.8.8.8: seq=2 ttl=56 time=14.267 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 14.267/59.436/149.775 ms

reply on ping cnn.com

PING cnn.com (151.101.65.67): 56 data bytes
64 bytes from 151.101.65.67: seq=0 ttl=56 time=226.482 ms
64 bytes from 151.101.65.67: seq=1 ttl=56 time=14.915 ms
64 bytes from 151.101.65.67: seq=2 ttl=56 time=14.390 ms
--- cnn.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 14.390/85.262/226.482 ms

which means i am indeed connected and DNS is working.
which is true cause i am online behind the router but i am on my own ip adress not the vpn's ip.

i will post the syslog directly in the post below.
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 12:38    Post subject: Reply with quote
System Log
Jan 1 01:00:10 DD-WRT syslog.info syslogd started: BusyBox v1.24.2
Jan 1 00:00:10 DD-WRT user.info : klogd : klog daemon successfully started
Jan 1 00:00:10 DD-WRT kern.notice kernel: klogd started: BusyBox v1.24.2 (2016-12-15 06:31:45 CET)
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.000000] Linux version 3.18.45 (root@nmndev) (gcc version 6.1.0 (LEDE GCC 6.1.0 r1259) ) #3077 Thu Dec 15 06:31:31 CET 2016
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] bootconsole [early0] enabled
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] CPU0 revision is: 00019750 (MIPS 74Kc)
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] cpu apb ddr apb cpu 720 ddr 600 ahb 200
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] sys id = 1130 Qualcomm Atheros QCA9558 ver 1 rev 1.0 (0x1130)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] Determined physical RAM map:
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] memory: 04000000 @ 00000000 (usable)
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Zone ranges:
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Normal [mem 0x00000000-0x03ffffff]
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Movable zone start for each node
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Early memory node ranges
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] node 0: [mem 0x00000000-0x03ffffff]
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x03ffffff]
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.000000] On node 0 totalpages: 16384
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.000000] free_area_init_node: node 0, pgdat 802df5d0, node_mem_map 81000000
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.000000] Normal zone: 128 pages used for memmap
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.000000] Normal zone: 0 pages reserved
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.000000] Normal zone: 16384 pages, LIFO batch:3
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Primary instruction cache 64kB, 4-way, VIPT, linesize 32 bytes.
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.000000] pcpu-alloc: [0] 0
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.000000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/sbin/init
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] Writing ErrCtl register=00000000
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] Readback ErrCtl register=00000000
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.000000] Memory: 61488K/65536K available (2264K kernel code, 153K rwdata, 228K rodata, 160K init, 237K bss, 4048K reserved)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.000000] NR_IRQS:83
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.060000] Calibrating delay loop... 358.80 BogoMIPS (lpj=1794048)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.060000] pid_max: default: 32768 minimum: 301
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.060000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.070000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.070000] NET: Registered protocol family 16
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.080000] ar71xx: using random MAC address for eth0
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.280000] ar71xx: using random MAC address for eth1
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.490000] ar724x-pci ar724x-pci.0: PCIe link is down
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.500000] registering PCI controller with io_map_base unset
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.500000] ar724x-pci ar724x-pci.1: PCIe link is down
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.510000] registering PCI controller with io_map_base unset
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.520000] PCI host bridge to bus 0000:00
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.520000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x11ffffff]
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.530000] pci_bus 0000:00: root bus resource [io 0x0000]
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.530000] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]

System Log
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.540000] PCI host bridge to bus 0000:01
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.540000] pci_bus 0000:01: root bus resource [mem 0x12000000-0x13ffffff]
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.550000] pci_bus 0000:01: root bus resource [io 0x0001]
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.550000] pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.560000] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.560000] Switched to clocksource MIPS
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.560000] NET: Registered protocol family 2
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.570000] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.570000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.580000] TCP: Hash tables configured (established 1024 bind 1024)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.580000] TCP: reno registered
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.590000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.590000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.600000] NET: Registered protocol family 1
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 0.600000] PCI: CLS 0 bytes, default 32
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.600000] gpio_proc: module loaded and /proc/gpio/ created
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.610000] futex hash table entries: 256 (order: -1, 3072 bytes)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.620000] squashfs: version 3.0 (2006/03/15) Phillip Lougher
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.620000] msgmni has been set to 120
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.630000] io scheduler noop registered
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.630000] io scheduler deadline registered (default)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.640000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.640000] console [ttyS0] disabled
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.670000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.680000] console [ttyS0] enabled
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.680000] bootconsole [early0] disabled
Jan 1 00:00:10 DD-WRT kern.emerg kernel: [ 0.690000] guessed flashsize = 8M
Jan 1 00:00:10 DD-WRT kern.emerg kernel: [ 0.700000] scanning for root partition
Jan 1 00:00:10 DD-WRT kern.emerg kernel: [ 0.700000] tplink uboot detected
Jan 1 00:00:10 DD-WRT kern.emerg kernel: [ 0.700000] guessed bootloader size = 20000
Jan 1 00:00:10 DD-WRT kern.emerg kernel: [ 0.720000]
Jan 1 00:00:10 DD-WRT kern.emerg kernel: [ 0.720000] found squashfs at 110000
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.730000] adjusted length 760000, original length 75E762
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.740000] Creating 9 MTD partitions on "ar7240-nor0":
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.740000] 0x000000000000-0x000000020000 : "RedBoot"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.750000] 0x000000020000-0x0000007e0000 : "linux"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.750000] 0x000000110000-0x000000760000 : "rootfs"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.760000] mtd: partition "rootfs" set to be root filesystem
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.760000] 0x000000760000-0x0000007e0000 : "ddwrt"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.770000] 0x0000007e0000-0x0000007f0000 : "nvram"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.770000] 0x0000007f0000-0x000000800000 : "board_config"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.780000] 0x000000000000-0x000000800000 : "fullflash"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.790000] 0x000000000000-0x000000020000 : "fullboot"
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.790000] 0x000000010000-0x000000020000 : "uboot-env"
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.800000] libphy: Fixed MDIO Bus: probed
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.800000] tun: Universal TUN/TAP device driver, 1.6
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.810000] tun: (C) 1999-2004 Max Krasnyansky
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.820000] u32 classifier
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.820000] Performance counters on

System Log
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.830000] Actions configured
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.830000] Netfilter messages via NETLINK v0.30.
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.840000] nf_conntrack version 0.5.0 (960 buckets, 3840 max)
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.840000] nf_conntrack_rtsp v0.7 loading
Jan 1 00:00:10 DD-WRT kern.warn kernel: [ 0.850000] nf_nat_rtsp v0.7 loading
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.850000] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.860000] TCP: westwood registered
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.860000] TCP: hybla registered
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.860000] TCP: vegas registered
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.870000] NET: Registered protocol family 17
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.870000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 0.890000] Bridge firewalling registered
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.890000] 8021q: 802.1Q VLAN Support v1.8
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.890000] searching for nvram
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.900000] nvram size = 0
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.950000] Atheros AR71xx hardware watchdog driver version 0.1.0
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.950000] ar71xx-wdt: timeout=15 secs (max=107) ref freq=40000000
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.980000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 0.990000] Freeing unused kernel memory: 160K (802f8000 - 80320000)
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 3.390000] ar71xx-wdt: enabling watchdog timer
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 3.460000] switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 4.110000] libphy: ag71xx_mdio: probed
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 4.700000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 4.710000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 5.300000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:SGMII
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 6.010000] eth1: link up (1000Mbps/Full duplex)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 6.080000] Loading modules backported from Linux version wt-2016-10-03-1-g6fcb1a6
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 6.090000] Backport generated by backports.git backports-20160324-9-g0e38f5c
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 6.840000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 6.840000] ath: EEPROM regdomain: 0x0
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 6.840000] ath: EEPROM indicates default country code should be used
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 6.840000] ath: doing EEPROM country->regdmn map search
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 6.840000] ath: country maps to regdmn code: 0x3a
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 6.840000] ath: Country alpha2 being used: US
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 6.840000] ath: Regpair used: 0x3a
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 6.850000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.debug kernel: [ 6.860000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 6.870000] gpiochip_find_base: cannot find free range
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 6.880000] gpiochip_add: GPIOs -1..22 (ath9k-phy0) failed to register
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 6.880000] ieee80211 phy0: Atheros AR9550 Rev:0 mem=0xb8100000, irq=79
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 7.700000] eth0: link up (1000Mbps/Full duplex)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.080000] device br0 entered promiscuous mode
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.110000] eth1: link down
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.120000] eth1: link up (1000Mbps/Full duplex)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.140000] eth1: link down
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.150000] eth1: link up (1000Mbps/Full duplex)
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.160000] device eth1 entered promiscuous mode
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.160000] br0: port 1(eth1) entered forwarding state
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.170000] br0: port 1(eth1) entered forwarding state

System Log
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.180000] device br0 entered promiscuous mode
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.200000] device br0 left promiscuous mode
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.700000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 2 is up
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.700000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 4 is up
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 9.710000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 5 is up
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 11.170000] br0: port 1(eth1) entered forwarding state
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 13.730000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 13.750000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 13.780000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 15.000000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 15.010000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.240000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.380000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.610000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.620000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.630000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.640000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.660000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 16.680000] device ath0 entered promiscuous mode
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.780000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.notice kernel: [ 16.970000] random: hostapd urandom read with 32 bits of entropy available
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.980000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 16.990000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.err kernel: [ 17.010000] Halt ACK timeout
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 17.020000] br0: port 2(ath0) entered forwarding state
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 17.030000] br0: port 2(ath0) entered forwarding state
Jan 1 00:00:10 DD-WRT user.info : dnsmasq : dnsmasq daemon successfully started
Jan 1 00:00:10 DD-WRT user.info : cron : cron daemon successfully started
Jan 1 00:00:10 DD-WRT cron.info cron[850]: (CRON) STARTUP (fork ok)
Jan 1 00:00:10 DD-WRT user.info : wland : WLAN daemon successfully started
Jan 1 00:00:10 DD-WRT kern.info kernel: [ 17.830000] device eth0 entered promiscuous mode
Jan 1 00:00:12 DD-WRT kern.info kernel: [ 19.030000] br0: port 2(ath0) entered forwarding state
Jan 1 00:00:12 DD-WRT daemon.warn openvpn[834]: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Jan 1 00:00:12 DD-WRT daemon.err openvpn[834]: Options error: Unrecognized option or missing or extra parameter(s) in [CMD-LINE]:1: down-pre (2.4_rc1)
Jan 1 00:00:12 DD-WRT daemon.warn openvpn[834]: Use --help for more information.
Jan 1 00:00:12 DD-WRT kern.warn kernel: [ 19.620000] ipt_TRIGGER: module license 'unspecified' taints kernel.
Jan 1 00:00:12 DD-WRT kern.warn kernel: [ 19.630000] Disabling lock debugging due to kernel taint
Jan 1 00:00:12 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jan 1 00:00:12 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:12 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:12 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:12 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 00:00:13 DD-WRT kern.info kernel: [ 20.430000] eth0: link down
Jan 1 00:00:13 DD-WRT kern.info kernel: [ 20.440000] device eth0 left promiscuous mode
Jan 1 00:00:13 DD-WRT user.info : ttraff : traffic counter daemon successfully started
Jan 1 00:00:13 DD-WRT user.info : klogd : kernel log daemon successfully stopped
Jan 1 00:00:13 DD-WRT kern.notice kernel: klogd: exiting
Jan 1 00:00:13 DD-WRT user.info : resetbutton : resetbutton daemon successfully stopped
Jan 1 00:00:13 DD-WRT user.info : syslogd : syslog daemon successfully stopped

System Log
Jan 1 01:00:14 DD-WRT syslog.info syslogd started: BusyBox v1.24.2
Jan 1 00:00:14 DD-WRT kern.notice kernel: klogd started: BusyBox v1.24.2 (2016-12-15 06:31:45 CET)
Jan 1 00:00:14 DD-WRT user.info : resetbutton : resetbutton daemon successfully started
Jan 1 00:00:14 DD-WRT kern.info kernel: [ 21.750000] eth0: link up (1000Mbps/Full duplex)
Jan 1 00:00:15 DD-WRT kern.info kernel: [ 22.770000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Jan 1 00:00:18 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jan 1 00:00:18 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:18 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:18 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:18 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 00:00:18 DD-WRT user.info : process_monitor successfully started
Jan 1 00:00:18 DD-WRT user.info : wland : WLAN daemon successfully stopped
Jan 1 00:00:18 DD-WRT user.info : wland : WLAN daemon successfully started
May 25 12:31:55 DD-WRT user.info : WAN is up. IP: 192.168.1.28
May 25 12:31:55 DD-WRT user.info : openvpn : OpenVPN daemon (Client) starting/restarting...
May 25 12:31:55 DD-WRT user.info : cron : cron daemon successfully stopped
May 25 12:31:55 DD-WRT daemon.warn openvpn[1567]: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
May 25 12:31:55 DD-WRT daemon.err openvpn[1567]: Options error: Unrecognized option or missing or extra parameter(s) in [CMD-LINE]:1: down-pre (2.4_rc1)
May 25 12:31:55 DD-WRT daemon.warn openvpn[1567]: Use --help for more information.
May 25 12:31:56 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
May 25 12:31:56 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
May 25 12:31:56 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
May 25 12:31:56 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
May 25 12:31:56 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
May 25 12:31:56 DD-WRT daemon.debug process_monitor[1561]: Restarting cron (time sync change)
May 25 12:31:56 DD-WRT daemon.debug process_monitor[1561]: We need to re-update after 3600 seconds
May 25 12:31:56 DD-WRT daemon.info process_monitor[1561]: set timer: 3600 seconds, callback: ntp_main()
May 25 12:31:56 DD-WRT kern.notice kernel: [ 27.000000] random: nonblocking pool is initialized
May 25 12:31:56 DD-WRT user.info : cron : cron daemon successfully started
May 25 12:31:56 DD-WRT cron.info cron[1942]: (CRON) STARTUP (fork ok)
May 25 12:31:56 DD-WRT user.info : process_monitor : Process Monitor successfully stopped
May 25 12:31:56 DD-WRT user.info : process_monitor successfully started
May 25 12:31:56 DD-WRT user.info : wland : WLAN daemon successfully stopped
May 25 12:31:56 DD-WRT daemon.debug process_monitor[1986]: We need to re-update after 3600 seconds
May 25 12:31:56 DD-WRT daemon.info process_monitor[1986]: set timer: 3600 seconds, callback: ntp_main()
May 25 12:31:56 DD-WRT user.info : wland : WLAN daemon successfully started
May 25 12:31:56 DD-WRT user.info : WAN is up. IP: 192.168.1.28
May 25 12:31:56 DD-WRT user.info : openvpn : OpenVPN daemon (Client) starting/restarting...
May 25 12:31:56 DD-WRT daemon.warn openvpn[1991]: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
May 25 12:31:56 DD-WRT daemon.err openvpn[1991]: Options error: Unrecognized option or missing or extra parameter(s) in [CMD-LINE]:1: down-pre (2.4_rc1)
May 25 12:31:56 DD-WRT daemon.warn openvpn[1991]: Use --help for more information.
May 25 12:32:05 DD-WRT user.debug : ttraff: data collection started
May 25 12:36:28 DD-WRT daemon.info hostapd: ath0: STA 48:2c:a0:68:9c:6b IEEE 802.11: authenticated
May 25 12:36:28 DD-WRT daemon.info hostapd: ath0: STA 48:2c:a0:68:9c:6b IEEE 802.11: associated (aid 1)
May 25 12:36:28 DD-WRT daemon.info hostapd: ath0: STA 48:2c:a0:68:9c:6b RADIUS: starting accounting session 00000009-00000000
May 25 12:36:28 DD-WRT daemon.info hostapd: ath0: STA 48:2c:a0:68:9c:6b WPA: pairwise key handshake completed (WPA)
May 25 12:36:28 DD-WRT daemon.info hostapd: ath0: STA 48:2c:a0:68:9c:6b WPA: group key handshake completed (WPA)
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 12:46    Post subject: Reply with quote
i hope that is infromative.
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 8034

PostPosted: Sat May 25, 2019 12:52    Post subject: Reply with quote
I assume those pings were conducted on the router itself??

If it's working on the router, and you have NAT enabled, I don't see why it wouldn't work from any client on the local network.

At this point, I'm not even sure what the real problem is that you're claiming.

_________________
DD-WRT: DNS Leak Detection w/ VPNs (updated 6/5/19)
NEW SCRIPT!: ddwrt-mount-usb-drives.sh
NEW SCRIPT!: ddwrt-blacklist-domains.sh
NEW SCRIPT!: ddwrt-ovpn-remote-access.sh
NEW SCRIPT!: ddwrt-pptp-policy-based-routing.sh
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 13:29    Post subject: Reply with quote
yea it has been ran from the router itself.

the problem is that the vpn is "not" working, my ip (the ip's behind the router are)is the ip of my service provider, not the ip of my vpn. which is kinda the idea of a VPN.

kind greats

Matt
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 8034

PostPosted: Sat May 25, 2019 14:11    Post subject: Reply with quote
Are using the PBR (policy based routing) field? If you place any source IPs there, only those devices will use the VPN. All others use the WAN.

Let's see a dump of the routing table and make sure the default gateway is pointing to the VPN.

Code:
route

_________________
DD-WRT: DNS Leak Detection w/ VPNs (updated 6/5/19)
NEW SCRIPT!: ddwrt-mount-usb-drives.sh
NEW SCRIPT!: ddwrt-blacklist-domains.sh
NEW SCRIPT!: ddwrt-ovpn-remote-access.sh
NEW SCRIPT!: ddwrt-pptp-policy-based-routing.sh
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 14:48    Post subject: Reply with quote
the reply to code is:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default mymodem 0.0.0.0 UG 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
169.254.0.0 * 255.255.0.0 U 0 0 0 br0
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0

i am not sure about if i use the PBR, i looked for the field but didn't find it yet.

also bumped into some comments on SFE being related.

kind greats
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 8034

PostPosted: Sat May 25, 2019 16:46    Post subject: Reply with quote
Well the above make no sense at all. Not only is there no default gateway to the VPN in that routing table, but there are no routes *at all* to the VPN! It's like the VPN isn't even running. Did you enable the VPN before dumping that routing table?
_________________
DD-WRT: DNS Leak Detection w/ VPNs (updated 6/5/19)
NEW SCRIPT!: ddwrt-mount-usb-drives.sh
NEW SCRIPT!: ddwrt-blacklist-domains.sh
NEW SCRIPT!: ddwrt-ovpn-remote-access.sh
NEW SCRIPT!: ddwrt-pptp-policy-based-routing.sh
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 17:14    Post subject: Reply with quote
i am looking through the forum thread :
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=312327&sid=b6d9ef77d19bb850fb9863b3a617807b

on policy based routing configure VPN W/dd-wrt linksys router

and i am unclear on some things, for now i have set the static ip my 3 main machines. which seems to be fine.

but in your replies in the thread mentioned above you use the ip address followed by /32 (192.168.1.90/32) is that 32 the port?

as you also use this row, which confuses me even more on the value behind the /:

192.168.1.100/30
192.168.1.104/29
192.168.1.112/28
192.168.1.128/28
192.168.1.144/30
192.168.1.148/31
192.168.1.150/32

i finally found also under tap setup / basic setup i did not find SFE, did find STP (enable/disable) but i assume this is something different. so i can for now not check if sfe is disabled.

the is nothing in the field PBR field (finally found it Wink), so all should be routed through the VPN if i understand correctly.

i also checked if vpn services are up under status/openvpn (not vpn), see the attached screenshot. it seems like it is not working.

also when if i get everything working, i would be interested in that kill script for if vpn would fail, but that is not for now.
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 17:26    Post subject: Reply with quote
your last answer en my last post crossed, i posted before reading your answer.

yes, start openvpn client is enabled, i double checked and made sure i also applied the settings and ran the dump again. exactly the same output. so indeed it all feels like the vpn is not up and running.

the syslog i posted earlier:
allthough i don't really understand i feel like in this bit below there is something wrong.

Jan 1 00:00:12 DD-WRT daemon.warn openvpn[834]: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Jan 1 00:00:12 DD-WRT daemon.err openvpn[834]: Options error: Unrecognized option or missing or extra parameter(s) in [CMD-LINE]:1: down-pre (2.4_rc1)
Jan 1 00:00:12 DD-WRT daemon.warn openvpn[834]: Use --help for more information.
Jan 1 00:00:12 DD-WRT kern.warn kernel: [ 19.620000] ipt_TRIGGER: module license 'unspecified' taints kernel.
Jan 1 00:00:12 DD-WRT kern.warn kernel: [ 19.630000] Disabling lock debugging due to kernel taint
Jan 1 00:00:12 DD-WRT user.info : vpn modules : vpn modules successfully unloaded

but maybe i am mistaken.

kind regards

Matt


Last edited by spikey1973 on Sat May 25, 2019 17:40; edited 1 time in total
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 5243
Location: Akershus, Norway

PostPosted: Sat May 25, 2019 17:40    Post subject: Reply with quote
Is comp-lzo supposed to be enabled?

It will cause problems if enabled on one side only.
spikey1973
DD-WRT Novice


Joined: 20 Feb 2017
Posts: 29

PostPosted: Sat May 25, 2019 17:43    Post subject: Reply with quote
according to cyberghost guidelines it does.

https://support.cyberghostvpn.com/hc/en-us/articles/213811885-Router-How-to-configure-OpenVPN-for-flashed-DD-WRT-routers

should i try to turn it off?
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Advanced Networking All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum