openVPN with IpVanish on a R7000 Nighthawk, can't get VPN

Post new topic   Reply to topic    DD-WRT Forum Index -> Advanced Networking
Author Message
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 3:03    Post subject: openVPN with IpVanish on a R7000 Nighthawk, can't get VPN Reply with quote
Thank you all in advance before I start my problems
Here is the build that I am running Firmware: DD-WRT v3.0-r31160M kongac (01/18/17)

I tried following the tutorial on there site but ppl are saying it's old and certain things need to be changed.

I've followed the tutorial, things in question that I've changed is
enabled user pass authentication (put in my Ip user/pass)

TLS Cipher None

Additonal Config looks like this
persist-remote-ip
auth SHA256
keysize 256
tls-remote lax-a01.ipvanish.com
script-security 3 system

no command scripts running in the startup scripts

my logs look like this
System Log
Jan 1 01:00:13 DD-WRT syslog.info syslogd started: BusyBox v1.24.2
Jan 1 01:00:13 DD-WRT user.info : klogd : klog daemon successfully started
Jan 1 01:00:13 DD-WRT kern.notice kernel: klogd started: BusyBox v1.24.2 (2017-01-18 20:19:14 CET)
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:03.0: [14e4:4715] type 00 class 0x020000
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:03.0: reg 0x10: [mem 0x18024000-0x18024fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:03.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:04.0: [14e4:4715] type 00 class 0x020000
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:04.0: reg 0x10: [mem 0x18025000-0x18025fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:04.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:05.0: [14e4:4715] type 00 class 0x020000
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:05.0: reg 0x10: [mem 0x18026000-0x18026fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:05.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:06.0: [14e4:4715] type 00 class 0x020000
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:06.0: reg 0x10: [mem 0x18027000-0x18027fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:06.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:07.0: [14e4:0501] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:07.0: reg 0x10: [mem 0x18012000-0x18012fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:07.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:08.0: [14e4:0501] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:08.0: reg 0x10: [mem 0x18013000-0x18013fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:08.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:09.0: [14e4:0501] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:09.0: reg 0x10: [mem 0x18014000-0x18014fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:09.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0a.0: [14e4:0510] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0a.0: reg 0x10: [mem 0x1800b000-0x1800bfff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0a.0: reg 0x14: [mem 0x1800c000-0x1800cfff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0a.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0b.0: [14e4:471a] type 00 class 0x0c0310
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0b.0: reg 0x10: [mem 0x18022000-0x18022fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0b.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0b.1: [14e4:471a] type 00 class 0x0c0320
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0b.1: reg 0x10: [mem 0x18021000-0x18021fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0b.1: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0c.0: [14e4:472a] type 00 class 0x0c0330
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0c.0: reg 0x10: [mem 0x18023000-0x18023fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0c.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0d.0: [14e4:0503] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0d.0: reg 0x10: [mem 0x18020000-0x18020fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0d.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0e.0: [14e4:4711] type 00 class 0x040100
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0e.0: reg 0x10: [mem 0x1802a000-0x1802afff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0f.0: [14e4:0506] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0f.0: reg 0x10: [mem 0x18210000-0x1821ffff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:10.0: [14e4:0507] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:10.0: reg 0x10: [mem 0x18010000-0x18010fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
System Log
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0000:00:11.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:11.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:12.0: [14e4:0509] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:12.0: reg 0x10: [mem 0x18028000-0x18028fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:12.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:13.0: [14e4:050a] type 00 class 0xffffff
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:13.0: reg 0x10: [mem 0x18029000-0x18029fff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0000:00:13.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
Jan 1 01:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan 1 01:00:13 DD-WRT kern.info kernel: PCIE1 link=1
Jan 1 01:00:13 DD-WRT kern.info kernel: PCIE1 switching to GEN2
Jan 1 01:00:13 DD-WRT kern.info kernel: PCIE1 link=1
Jan 1 01:00:13 DD-WRT kern.info kernel: PCI host bridge to bus 0001:00
Jan 1 01:00:13 DD-WRT kern.info kernel: pci_bus 0001:00: root bus resource [mem 0x08000000-0x0fffffff]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0001:00:00.0: [14e4:8012] type 01 class 0x060400
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
Jan 1 01:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 0 domain 1
Jan 1 01:00:13 DD-WRT kern.info kernel: PCI: bus0: Fast back to back transfers disabled
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0001:01:00.0: [14e4:4360] type 00 class 0x028000
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0001:01:00.0: reg 0x10: [mem 0x08000000-0x08007fff 64bit]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0001:01:00.0: Max Payload Size set to 512 (was 128, max 512)
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0001:01:00.0: supports D1 D2
Jan 1 01:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 1 domain 1
Jan 1 01:00:13 DD-WRT kern.info kernel: PCI: bus1: Fast back to back transfers disabled
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 01
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x080fffff]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0001:01:00.0: BAR 0: assigned [mem 0x08000000-0x08007fff 64bit]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0001:00:00.0: PCI bridge to [bus 01]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0001:00:00.0: bridge window [mem 0x08000000-0x080fffff]
Jan 1 01:00:13 DD-WRT kern.info kernel: PCIE2 link=1
Jan 1 01:00:13 DD-WRT kern.info kernel: PCIE2 switching to GEN2
Jan 1 01:00:13 DD-WRT kern.info kernel: PCIE2 link=1
Jan 1 01:00:13 DD-WRT kern.info kernel: PCI host bridge to bus 0002:00
Jan 1 01:00:13 DD-WRT kern.info kernel: pci_bus 0002:00: root bus resource [mem 0x40000000-0x47ffffff]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0002:00:00.0: [14e4:8012] type 01 class 0x060400
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
Jan 1 01:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 0 domain 2
Jan 1 01:00:13 DD-WRT kern.info kernel: PCI: bus0: Fast back to back transfers disabled
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0002:01:00.0: [14e4:4360] type 00 class 0x028000
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0002:01:00.0: reg 0x10: [mem 0x40000000-0x40007fff 64bit]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0002:01:00.0: Max Payload Size set to 512 (was 128, max 512)
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci 0002:01:00.0: supports D1 D2
Jan 1 01:00:13 DD-WRT kern.warn kernel: PCI: Fixing up bus 1 domain 2
Jan 1 01:00:13 DD-WRT kern.info kernel: PCI: bus1: Fast back to back transfers disabled
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci_bus 0002:01: busn_res: [bus 01-ff] end is updated to 01
Jan 1 01:00:13 DD-WRT kern.debug kernel: pci_bus 0002:00: busn_res: [bus 00-ff] end is updated to 01
System Log
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0002:01:00.0: BAR 0: assigned [mem 0x40000000-0x40007fff 64bit]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0002:00:00.0: PCI bridge to [bus 01]
Jan 1 01:00:13 DD-WRT kern.info kernel: pci 0002:00:00.0: bridge window [mem 0x40000000-0x400fffff]
Jan 1 01:00:13 DD-WRT kern.info kernel: PCIE3 link=0
Jan 1 01:00:13 DD-WRT kern.info kernel: futex hash table entries: 512 (order: 3, 32768 bytes)
Jan 1 01:00:13 DD-WRT kern.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
Jan 1 01:00:13 DD-WRT kern.info kernel: io scheduler noop registered (default)
Jan 1 01:00:13 DD-WRT kern.info kernel: io scheduler cfq registered
Jan 1 01:00:13 DD-WRT kern.info kernel: serial8250_init
Jan 1 01:00:13 DD-WRT kern.info kernel: Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
Jan 1 01:00:13 DD-WRT kern.info kernel: console [ttyS0] disabled
Jan 1 01:00:13 DD-WRT kern.info kernel: serial8250.0: ttyS0 at MMIO 0x18000300 (irq = 117, base_baud = 7812500) is a 16550
Jan 1 01:00:13 DD-WRT kern.info kernel: console [ttyS0] enabled
Jan 1 01:00:13 DD-WRT kern.info kernel: serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117, base_baud = 7812500) is a 16550
Jan 1 01:00:13 DD-WRT kern.info kernel: brd: module loaded
Jan 1 01:00:13 DD-WRT kern.info kernel: loop: module loaded
Jan 1 01:00:13 DD-WRT kern.err kernel: bcmsflash: found no supported devices
Jan 1 01:00:13 DD-WRT kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 01:00:13 DD-WRT kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x2000000, 0x20000
Jan 1 01:00:13 DD-WRT kern.info kernel: found TRX Header on nflash!
Jan 1 01:00:13 DD-WRT kern.notice kernel: nflash: squash filesystem with lzma found at block 29
Jan 1 01:00:13 DD-WRT kern.notice kernel: Creating 5 MTD partitions on "nflash":
Jan 1 01:00:13 DD-WRT kern.notice kernel: 0x000000000000-0x000000080000 : "boot"
Jan 1 01:00:13 DD-WRT kern.notice kernel: 0x000000080000-0x000000200000 : "nvram"
Jan 1 01:00:13 DD-WRT kern.notice kernel: 0x000000200000-0x000002200000 : "linux"
Jan 1 01:00:13 DD-WRT kern.notice kernel: 0x0000003a0000-0x000002200000 : "rootfs"
Jan 1 01:00:13 DD-WRT kern.notice kernel: 0x000002200000-0x000002240000 : "board_data"
Jan 1 01:00:13 DD-WRT kern.info kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 1 01:00:13 DD-WRT kern.info kernel: tun: (C) 1999-2004 Max Krasnyansky
Jan 1 01:00:13 DD-WRT kern.info kernel: PPP generic driver version 2.4.2
Jan 1 01:00:13 DD-WRT kern.info kernel: PPP BSD Compression module registered
Jan 1 01:00:13 DD-WRT kern.info kernel: PPP Deflate Compression module registered
Jan 1 01:00:13 DD-WRT kern.info kernel: PPP MPPE Compression module registered
Jan 1 01:00:13 DD-WRT kern.info kernel: NET: Registered protocol family 24
Jan 1 01:00:13 DD-WRT kern.info kernel: GACT probability NOT on
Jan 1 01:00:13 DD-WRT kern.info kernel: Mirror/redirect action on
Jan 1 01:00:13 DD-WRT kern.info kernel: Simple TC action Loaded
Jan 1 01:00:13 DD-WRT kern.info kernel: netem: version 1.3
Jan 1 01:00:13 DD-WRT kern.info kernel: u32 classifier
Jan 1 01:00:13 DD-WRT kern.info kernel: Performance counters on
Jan 1 01:00:13 DD-WRT kern.info kernel: input device check on
Jan 1 01:00:13 DD-WRT kern.info kernel: Actions configured
Jan 1 01:00:13 DD-WRT kern.info kernel: Netfilter messages via NETLINK v0.30.
Jan 1 01:00:13 DD-WRT kern.info kernel: nf_conntrack version 0.5.0 (3971 buckets, 15884 max)
Jan 1 01:00:13 DD-WRT kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan 1 01:00:13 DD-WRT kern.info kernel: xt_time: kernel timezone is -0000
Jan 1 01:00:13 DD-WRT kern.info kernel: ip_set: protocol 6
Jan 1 01:00:13 DD-WRT kern.info kernel: gre: GRE over IPv4 demultiplexor driver
Jan 1 01:00:13 DD-WRT kern.warn kernel: nf_nat_rtsp v0.7 loading
System Log
Jan 1 01:00:13 DD-WRT kern.info kernel: NET: Registered protocol family 17
Jan 1 01:00:13 DD-WRT kern.info kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Jan 1 01:00:13 DD-WRT kern.notice kernel: Bridge firewalling registered
Jan 1 01:00:13 DD-WRT kern.info kernel: 8021q: 802.1Q VLAN Support v1.8
Jan 1 01:00:13 DD-WRT kern.notice kernel: Registering SWP/SWPB emulation handler
Jan 1 01:00:13 DD-WRT kern.info kernel: max nvram space = 131072
Jan 1 01:00:13 DD-WRT kern.info kernel: read 65536 bytes to offset 0
Jan 1 01:00:13 DD-WRT kern.notice kernel: Key type encrypted registered
Jan 1 01:00:13 DD-WRT kern.info kernel: Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
Jan 1 01:00:13 DD-WRT kern.info kernel: nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
Jan 1 01:00:13 DD-WRT kern.info kernel: nand: AMD/Spansion NAND 128MiB 3,3V 8-bit
Jan 1 01:00:13 DD-WRT kern.info kernel: nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Jan 1 01:00:13 DD-WRT kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan 1 01:00:13 DD-WRT kern.warn kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Jan 1 01:00:13 DD-WRT kern.warn kernel: Available 7 bytes at (off,len):
Jan 1 01:00:13 DD-WRT kern.warn kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0)
Jan 1 01:00:13 DD-WRT kern.info kernel: Scanning device for bad blocks
Jan 1 01:00:13 DD-WRT kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan 1 01:00:13 DD-WRT kern.notice kernel: Creating 1 MTD partitions on "brcmnand":
Jan 1 01:00:13 DD-WRT kern.notice kernel: 0x000002240000-0x000008000000 : "ddwrt"
Jan 1 01:00:13 DD-WRT kern.info kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Jan 1 01:00:13 DD-WRT kern.info kernel: Freeing unused kernel memory: 344K (8048c000 - 804e2000)
Jan 1 01:00:13 DD-WRT kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan 1 01:00:13 DD-WRT kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 01:00:13 DD-WRT kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 01:00:13 DD-WRT kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 01:00:13 DD-WRT kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Jan 1 01:00:13 DD-WRT kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 01:00:13 DD-WRT kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 01:00:13 DD-WRT kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 01:00:13 DD-WRT kern.info kernel: ET Corerev 5
Jan 1 01:00:13 DD-WRT kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan 1 01:00:13 DD-WRT kern.info kernel: roboswitch: Probing device 'eth0'
Jan 1 01:00:13 DD-WRT kern.info kernel: roboswitch: trying a 53012! at eth0
Jan 1 01:00:13 DD-WRT kern.info kernel: detected CPU Port is 5
Jan 1 01:00:13 DD-WRT kern.info kernel: roboswitch: found a 53012! at eth0
Jan 1 01:00:13 DD-WRT kern.info kernel: detected CPU Port is 5
Jan 1 01:00:13 DD-WRT kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan 1 01:00:13 DD-WRT kern.warn kernel: wl_module_init: txworkq set to 0x0
Jan 1 01:00:13 DD-WRT kern.warn kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan 1 01:00:13 DD-WRT kern.warn kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan 1 01:00:13 DD-WRT kern.warn kernel: eth0: mixed HW and IP checksum settings.
Jan 1 01:00:13 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: device eth0 entered promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: device eth1 entered promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: device eth2 entered promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jan 1 01:00:13 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
System Log
Jan 1 01:00:13 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jan 1 01:00:13 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:13 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 01:00:13 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jan 1 01:00:13 DD-WRT kern.info kernel: device vlan2 entered promiscuous mode
Jan 1 01:00:13 DD-WRT user.info : cron : cron daemon successfully started
Jan 1 01:00:13 DD-WRT cron.info cron[923]: (CRON) STARTUP (fork ok)
Jan 1 01:00:14 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jan 1 01:00:14 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 01:00:14 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 01:00:14 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 01:00:14 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 01:00:14 DD-WRT kern.info kernel: device vlan2 left promiscuous mode
Jan 1 01:00:14 DD-WRT user.info : ttraff : traffic counter daemon successfully started
Jan 1 01:00:14 DD-WRT kern.notice kernel: random: dnsmasq: uninitialized urandom read (128 bytes read, 65 bits of entropy available)
Jan 1 01:00:14 DD-WRT kern.notice kernel: random: dnsmasq: uninitialized urandom read (48 bytes read, 66 bits of entropy available)
Jan 1 01:00:14 DD-WRT daemon.info dnsmasq[1006]: started, version 2.77 cachesize 1500
Jan 1 01:00:14 DD-WRT daemon.info dnsmasq[1006]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth DNSSEC loop-detect no-inotify
Jan 1 01:00:14 DD-WRT daemon.info dnsmasq-dhcp[1006]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
Jan 1 01:00:14 DD-WRT user.info : dnsmasq : dnsmasq daemon successfully started
Jan 1 01:00:14 DD-WRT daemon.warn dnsmasq[1006]: no servers found in /tmp/resolv.dnsmasq, will retry
Jan 1 01:00:14 DD-WRT daemon.info dnsmasq[1006]: read /etc/hosts - 2 addresses
Jan 1 01:00:15 DD-WRT daemon.err openvpn[888]: Options error: Unrecognized option or missing or extra parameter(s) in /tmp/openvpncl/openvpn.conf:26: tls-remote (2.4.0)
Jan 1 01:00:15 DD-WRT daemon.warn openvpn[888]: Use --help for more information.
Jan 1 01:00:16 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
Jan 1 01:00:16 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 01:00:16 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 01:00:16 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 01:00:16 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 01:00:16 DD-WRT daemon.info dnsmasq[1006]: reading /tmp/resolv.dnsmasq
Jan 1 01:00:16 DD-WRT daemon.info dnsmasq[1006]: using nameserver 209.18.47.61#53
Jan 1 01:00:16 DD-WRT daemon.info dnsmasq[1006]: using nameserver 24.25.227.55#53
Jan 1 01:00:16 DD-WRT user.info : process_monitor successfully started
Jan 1 01:00:16 DD-WRT user.info : wland : WLAN daemon successfully stopped
Jan 1 01:00:16 DD-WRT user.info : wland : WLAN daemon successfully started
Jan 1 01:00:16 DD-WRT user.info : WAN is up. IP: 98.150.213.205
Jan 1 01:00:16 DD-WRT user.info : openvpn : OpenVPN daemon (Client) starting/restarting...
Jan 1 01:00:16 DD-WRT daemon.err openvpn[1140]: Options error: Unrecognized option or missing or extra parameter(s) in /tmp/openvpncl/openvpn.conf:26: tls-remote (2.4.0)
Jan 1 01:00:16 DD-WRT daemon.warn openvpn[1140]: Use --help for more information.
Jan 21 03:33:07 DD-WRT user.info : cron : cron daemon successfully stopped
Jan 21 03:33:08 DD-WRT daemon.debug process_monitor[1135]: Restarting cron (time sync change)
Jan 21 03:33:08 DD-WRT daemon.debug process_monitor[1135]: We need to re-update after 3600 seconds
Jan 21 03:33:08 DD-WRT daemon.info process_monitor[1135]: set timer: 3600 seconds, callback: ntp_main()
Jan 21 03:33:08 DD-WRT user.info : cron : cron daemon successfully started
Jan 21 03:33:08 DD-WRT cron.info cron[1151]: (CRON) STARTUP (fork ok)
Jan 21 03:33:15 DD-WRT user.info : klogd : kernel log daemon successfully stopped
Jan 21 03:33:15 DD-WRT kern.notice kernel: klogd: exiting
System Log
Jan 21 03:33:15 DD-WRT user.info : resetbutton : resetbutton daemon successfully started
Jan 21 03:33:16 DD-WRT user.info : syslogd : syslog daemon successfully stopped
Jan 21 03:33:16 DD-WRT syslog.info syslogd exiting
Jan 21 03:33:16 DD-WRT syslog.info syslogd started: BusyBox v1.24.2
Jan 21 03:33:16 DD-WRT user.info : klogd : klog daemon successfully started
Jan 21 03:33:16 DD-WRT kern.notice kernel: klogd started: BusyBox v1.24.2 (2017-01-18 20:19:14 CET)
Jan 21 03:33:19 DD-WRT kern.info kernel: br0: port 3(eth2) entered forwarding state
Jan 21 03:33:19 DD-WRT kern.info kernel: br0: port 2(eth1) entered forwarding state
Jan 21 03:33:19 DD-WRT kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 21 03:33:20 DD-WRT user.debug : ttraff: data collection started
Jan 21 03:33:24 DD-WRT kern.notice kernel: random: nonblocking pool is initialized
Jan 21 04:01:17 DD-WRT kern.info kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.


Log
Clientlog:

ca /tmp/openvpncl/ca.crt management 127.0.0.1 16 management-log-cache 100 verb 3 mute 3 syslog writepid /var/run/openvpncl.pid client resolv-retry infinite nobind persist-key persist-tun script-security 2 dev tun1 proto tcp4-client cipher aes-256-cbc auth sha256 auth-user-pass /tmp/openvpncl/credentials remote lax-a01.ipvanish.com 443 comp-lzo yes tun-mtu 1500 mtu-disc yes persist-remote-ip auth SHA256 keysize 256 tls-remote lax-a01.ipvanish.com script-security 3 system
Sponsor
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 4:43    Post subject: Reply with quote
eibgrad wrote:
Code:
Jan 1 01:00:16 DD-WRT daemon.err openvpn[1140]: Options error: Unrecognized option or missing or extra parameter(s) in /tmp/openvpncl/openvpn.conf:26: tls-remote (2.4.0)


That seems to be the current problem. tls-remote is optional. Leave it out for now. In fact, leave everything out of Additional Config for now.


I can't seem to visit any other pages, except this one now, it says somehting about the dns not being able to be found.

I deleted the additional config and here is my log


Setup
Wireless
Services
Security
Access Restrictions
NAT / QoS
Administration
Status
Router
WAN
LAN
Wireless
OpenVPN
Bandwidth
Syslog
Sys-Info
State
Client: CONNECTED SUCCESS
Local Address: 172.21.28.131
Remote Address: 172.21.28.131

Status
VPN Client Stats
TUN/TAP read bytes 85912
TUN/TAP write bytes 12924
TCP/UDP read bytes 21624
TCP/UDP write bytes 97588
Auth read bytes 12924
pre-compress bytes 80469
post-compress bytes 79467
pre-decompress bytes 1139
post-decompress bytes 1168

Log
Clientlog:
20170121 05:39:55 W WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
20170121 05:39:55 I OpenVPN 2.4.0 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Jan 18 2017
20170121 05:39:55 I library versions: OpenSSL 1.0.2j 26 Sep 2016 LZO 2.09
20170121 05:39:55 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
20170121 05:39:55 W WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
20170121 05:39:55 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20170121 05:39:55 I TCP/UDP: Preserving recently used remote address: [AF_INET]64.145.76.2:443
20170121 05:39:55 Socket Buffers: R=[87380->87380] S=[16384->16384]
20170121 05:39:55 I Attempting to establish TCP connection with [AF_INET]64.145.76.2:443 [nonblock]
20170121 05:39:56 I TCP connection established with [AF_INET]64.145.76.2:443
20170121 05:39:56 I TCPv4_CLIENT link local: (not bound)
20170121 05:39:56 I TCPv4_CLIENT link remote: [AF_INET]64.145.76.2:443
20170121 05:39:56 TLS: Initial packet from [AF_INET]64.145.76.2:443 sid=5d3f213b 1d8ead39
20170121 05:39:56 W WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
20170121 05:39:56 VERIFY OK: depth=1 C=US ST=FL L=Winter Park O=IPVanish OU=IPVanish VPN CN=IPVanish CA emailAddress=support@ipvanish.com
20170121 05:39:56 VERIFY OK: depth=0 C=US ST=FL L=Winter Park O=IPVanish OU=IPVanish VPN CN=lax-a01.ipvanish.com emailAddress=support@ipvanish.com
20170121 05:39:57 Control Channel: TLSv1.2 cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384 2048 bit RSA
20170121 05:39:57 I [lax-a01.ipvanish.com] Peer Connection Initiated with [AF_INET]64.145.76.2:443
20170121 05:39:58 SENT CONTROL [lax-a01.ipvanish.com]: 'PUSH_REQUEST' (status=1)
20170121 05:39:58 PUSH: Received control message: 'PUSH_REPLY redirect-gateway def1 bypass-dhcp dhcp-option DNS 198.18.0.1 dhcp-option DNS 198.18.0.2 rcvbuf 262144 explicit-exit-notify 5 route-gateway 172.21.28.1 topology subnet ping 20 ping-restart 40 ifconfig 172.21.28.131 255.255.254.0'
20170121 05:39:58 W Option 'explicit-exit-notify' in [PUSH-OPTIONS]:5 is ignored by previous blocks
20170121 05:39:58 OPTIONS IMPORT: timers and/or timeouts modified
20170121 05:39:58 OPTIONS IMPORT: --explicit-exit-notify can only be used with --proto udp
20170121 05:39:58 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
20170121 05:39:58 Socket Buffers: R=[346880->360448] S=[46080->46080]
20170121 05:39:58 OPTIONS IMPORT: --ifconfig/up options modified
20170121 05:39:58 OPTIONS IMPORT: route options modified
20170121 05:39:58 OPTIONS IMPORT: route-related options modified
20170121 05:39:58 NOTE: --mute triggered...
20170121 05:39:58 1 variation(s) on previous 3 message(s) suppressed by --mute
20170121 05:39:58 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
20170121 05:39:58 Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
20170121 05:39:58 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
20170121 05:39:58 NOTE: --mute triggered...
20170121 05:39:58 1 variation(s) on previous 3 message(s) suppressed by --mute
20170121 05:39:58 I TUN/TAP device tun1 opened
20170121 05:39:58 TUN/TAP TX queue length set to 100
20170121 05:39:58 D do_ifconfig tt->did_ifconfig_ipv6_setup=0
20170121 05:39:58 I /sbin/ifconfig tun1 172.21.28.131 netmask 255.255.254.0 mtu 1500 broadcast 172.21.29.255
20170121 05:39:58 /sbin/route add -net 64.145.76.2 netmask 255.255.255.255 gw 98.150.208.1
20170121 05:39:58 /sbin/route add -net 0.0.0.0 netmask 128.0.0.0 gw 172.21.28.1
20170121 05:39:58 /sbin/route add -net 128.0.0.0 netmask 128.0.0.0 gw 172.21.28.1
20170121 05:39:58 I Initialization Sequence Completed
20170121 05:40:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20170121 05:40:29 D MANAGEMENT: CMD 'state'
20170121 05:40:29 MANAGEMENT: Client disconnected
20170121 05:40:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20170121 05:40:29 D MANAGEMENT: CMD 'state'
20170121 05:40:29 MANAGEMENT: Client disconnected
20170121 05:40:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20170121 05:40:29 D MANAGEMENT: CMD 'state'
20170121 05:40:29 MANAGEMENT: Client disconnected
20170121 05:40:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20170121 05:40:29 D MANAGEMENT: CMD 'status 2'
20170121 05:40:29 MANAGEMENT: Client disconnected
20170121 05:40:29 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20170121 05:40:29 D MANAGEMENT: CMD 'log 500'
19700101 01:00:00

ca /tmp/openvpncl/ca.crt management 127.0.0.1 16 management-log-cache 100 verb 3 mute 3 syslog writepid /var/run/openvpncl.pid client resolv-retry infinite nobind persist-key persist-tun script-security 2 dev tun1 proto tcp4-client cipher aes-256-cbc auth sha256 auth-user-pass /tmp/openvpncl/credentials remote lax-a01.ipvanish.com 443 comp-lzo yes tun-mtu 1500 mtu-disc yes
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 4:54    Post subject: Reply with quote
eibgrad wrote:
^^^ that should be working. It shows connected. The tunnel shows reads/writes.

Can you ping an internet address, say 8.8.8.8? It might just be a DNS issue.


yes I can ping it, it showed 4 sent, 4 received and none loss, how do I fix the dns side?
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 4:57    Post subject: Reply with quote
eibgrad wrote:
Do you have "Use DNSMasq for DNS" checked on the Setup page?


yes it is checked currently
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 5:17    Post subject: Reply with quote
eibgrad wrote:
If you're using DNSMasq for DNS, then your clients should be assigned the router's LAN ip for their DNS server. Verify this is the case.

For Windows:

Code:
ipconfig /all


Your OpenVPN log shows the following two DNS servers being pushed to the OpenVPN client. See if you can ping them.

Code:
198.18.0.1
198.18.0.2


Go to a telnet/ssh session, then post the results of these dumps.



Code:
route -n
ifconfig
cat /tmp/dnsmasq.conf
cat /tmp/resolv.dnsmasq
cat /tmp/resolv.dnsmasq_isp


Sorry I'm very new to this. When I type in telnet. Nothing opens up. It's giving me dns error. Check the firewall etc. I'm really confused now
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 5:19    Post subject: Reply with quote
Could it be that I have 2 routers plugged into my modem. 1 is stock modem and the other I'm trying to run the tunnel
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 5:33    Post subject: Reply with quote
eibgrad wrote:
warui111 wrote:
Could it be that I have 2 routers plugged into my modem. 1 is stock modem and the other I'm trying to run the tunnel


Could be anything at this point. I don't know the first thing about your configuration beyond what you've already told me (which is only the OpenVPN client config). That's why I'm trying to have you dump information, so I can figure it out. And the more information you provide, the better.

Are these routers connected WAN to LAN, or LAN to LAN?

As far as telnet...

Enabled the telnet client if you haven't already.

https://social.technet.microsoft.com/wiki/contents/articles/910.windows-7-enabling-telnet-client.aspx

To use it, go to a command prompt and type:

telnet 192.168.1.1

(or whatever your router's LAN ip is)

At the prompt, type "root" (no quotes) for username, and your GUI password for the password. At the prompt you can execute those commands. Usually you can just cut and paste them directly into the telnet window. And copy them back for posting.


Routers are both connected wan to LAN. Will start the dump now
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 5:40    Post subject: Reply with quote
eibgrad wrote:
warui111 wrote:
Could it be that I have 2 routers plugged into my modem. 1 is stock modem and the other I'm trying to run the tunnel


Could be anything at this point. I don't know the first thing about your configuration beyond what you've already told me (which is only the OpenVPN client config). That's why I'm trying to have you dump information, so I can figure it out. And the more information you provide, the better.

Are these routers connected WAN to LAN, or LAN to LAN?

As far as telnet...

Enabled the telnet client if you haven't already.

https://social.technet.microsoft.com/wiki/contents/articles/910.windows-7-enabling-telnet-client.aspx

To use it, go to a command prompt and type:

telnet 192.168.1.1

(or whatever your router's LAN ip is)

At the prompt, type "root" (no quotes) for username, and your GUI password for the password. At the prompt you can execute those commands. Usually you can just cut and paste them directly into the telnet window. And copy them back for posting.



DD-WRT v3.0-r31160M kongac (c) 2017 NewMedia-NET GmbH
Release: 01/18/17

DD-WRT login: root
Password:
==========================================================

___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/

DD-WRT v3.0
http://www.dd-wrt.com

==========================================================


BusyBox v1.24.2 (2017-01-18 20:19:14 CET) built-in shell (ash)

root@DD-WRT:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 172.21.26.1 128.0.0.0 UG 0 0 0 tun1
0.0.0.0 98.150.208.1 0.0.0.0 UG 0 0 0 vlan2
64.145.76.2 98.150.208.1 255.255.255.255 UGH 0 0 0 vlan2
98.150.208.0 0.0.0.0 255.255.248.0 U 0 0 0 vlan2
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
128.0.0.0 172.21.26.1 128.0.0.0 UG 0 0 0 tun1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0
172.21.26.0 0.0.0.0 255.255.254.0 U 0 0 0 tun1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
root@DD-WRT:~#
root@DD-WRT:~# ifconfig
br0 Link encap:Ethernet HWaddr 50:6A:03:C9:68:2A
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5801 errors:0 dropped:18 overruns:0 frame:0
TX packets:4763 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1097384 (1.0 MiB) TX bytes:2543716 (2.4 MiB)

br0:0 Link encap:Ethernet HWaddr 50:6A:03:C9:68:2A
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr 50:6A:03:C9:68:28
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:67774 errors:0 dropped:0 overruns:0 frame:0
TX packets:7600 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6625795 (6.3 MiB) TX bytes:3727353 (3.5 MiB)
Interrupt:179 Base address:0x4000

eth1 Link encap:Ethernet HWaddr 50:6A:03:C9:68:2A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:98371
TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:38400 (37.5 KiB)
Interrupt:163

eth2 Link encap:Ethernet HWaddr 50:6A:03:C9:68:27
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:34296
TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:38400 (37.5 KiB)
Interrupt:169

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:65536 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:576 (576.0 B) TX bytes:576 (576.0 B)

tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:172.21.26.155 P-t-P:172.21.26.155 Mask:255.255.254.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:1946 errors:0 dropped:0 overruns:0 frame:0
TX packets:2700 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1114970 (1.0 MiB) TX bytes:789530 (771.0 KiB)

vlan1 Link encap:Ethernet HWaddr 50:6A:03:C9:68:28
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5804 errors:0 dropped:0 overruns:0 frame:0
TX packets:4763 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1097522 (1.0 MiB) TX bytes:2543716 (2.4 MiB)

vlan2 Link encap:Ethernet HWaddr 50:6A:03:C9:68:29
inet addr:98.150.213.205 Bcast:98.150.215.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:61917 errors:0 dropped:823 overruns:0 frame:0
TX packets:2837 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4035019 (3.8 MiB) TX bytes:1153237 (1.0 MiB)

root@DD-WRT:~# cat /tmp/dnsmaq.conf
cat: can't open '/tmp/dnsmaq.conf': No such file or directory
root@DD-WRT:~# cat /tmp/dnsmasq.conf
interface=br0
resolv-file=/tmp/resolv.dnsmasq
strict-order
domain=hawaii.rr.com
dhcp-leasefile=/tmp/dnsmasq.leases
dhcp-lease-max=50
dhcp-option=br0,3,192.168.1.1
dhcp-authoritative
dhcp-range=br0,192.168.1.100,192.168.1.149,255.255.255.0,1440m
stop-dns-rebind
root@DD-WRT:~# cat /tmp/resolv.dnsmasq
nameserver 198.18.0.1
nameserver 198.18.0.2
nameserver 209.18.47.61
nameserver 24.25.227.55
root@DD-WRT:~# cat /tmp/resolv.dnsmasq_isp
nameserver 209.18.47.61
nameserver 24.25.227.55
root@DD-WRT:~#
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 5:56    Post subject: Reply with quote
eibgrad wrote:
Can you ping the IPVanish DNS servers?

198.18.0.1
198.18.0.2


Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\J>ping 198.18.0.1

Pinging 198.18.0.1 with 32 bytes of data:
Reply from 198.18.0.1: bytes=32 time=62ms TTL=63
Reply from 198.18.0.1: bytes=32 time=58ms TTL=63
Reply from 198.18.0.1: bytes=32 time=59ms TTL=63
Reply from 198.18.0.1: bytes=32 time=57ms TTL=63

Ping statistics for 198.18.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 62ms, Average = 59ms

C:\Users\J>ping 198.18.0.2

Pinging 198.18.0.2 with 32 bytes of data:
Reply from 198.18.0.2: bytes=32 time=58ms TTL=63
Reply from 198.18.0.2: bytes=32 time=58ms TTL=63
Reply from 198.18.0.2: bytes=32 time=78ms TTL=63
Reply from 198.18.0.2: bytes=32 time=57ms TTL=63

Ping statistics for 198.18.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 78ms, Average = 62ms
warui111
DD-WRT Novice


Joined: 21 Jan 2017
Posts: 14

PostPosted: Sat Jan 21, 2017 6:22    Post subject: Reply with quote
eibgrad wrote:
Go to a telnet session again and issue the following command:

touch /tmp/resolv.dnsmasq

See if it helps.


THANK YOU SO MUCH!!! IT WORKS
Appreciate you taking the time to help me!!!
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT 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