Community


All times are UTC - 5 hours




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: TAP configuration problem
PostPosted: Wed Nov 08, 2017 7:00 am 
Offline

Joined: Wed Nov 08, 2017 6:44 am
Posts: 3
Hi there, we've been using Neorouter Mesh very successfully for two years, and I've just started having problems. I seem to be able to log into Neorouter Explorer, and see all our devices listed ok, but I'm no longer connected properly to the 172.16.0.* VPN. It would appear that the TAP network adapter is not being set correctly with my assigned VPN ip address.

Looking at the NRService log, it's attempting to set the correct ipaddress, 172.16.0.2, as listed against my machine name 'XPS' in the configuration explorer...

Quote:
2017-11-08 11:42:15,192|03680|04984| |+[CNicDevice::RunCommand]
2017-11-08 11:42:15,192|03680|04984|D|"C:\WINDOWS\system32\netsh.exe" interface ipv4 set address 59 static 172.16.0.2 255.255.0.0
2017-11-08 11:42:15,243|03680|04984|D|ExitCode = 1
2017-11-08 11:42:15,243|03680|04984| |-[CNicDevice::RunCommand](hr=0x0)
2017-11-08 11:42:15,243|03680|04984|T|already initialized
2017-11-08 11:42:15,243|03680|04984|D|Setup NRTAP driver to set a static IP/netmask/gw of 172.16.0.2/255.255.0.0/172.16.0.2 on interface {CC368748-CF2F-4747-9AAC-344DA716228E}
2017-11-08 11:42:15,243|03680|04984|D|TAP is created.


But looking at the output of 'ipconfig /all' we see that it's not assigning it correctly anymore:
Quote:
Ethernet adapter Ethernet 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NeoRouter Virtual Network Interface
Physical Address. . . . . . . . . : 00-FF-CC-36-87-48
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2ddc:8263:fd69:65c7%59(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.101.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 989921228
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-75-C9-A1-34-17-EB-A8-46-93
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled


The logs show that it attempts this process several times.

Any ideas? I've uninstalled and reinstalled Neorouter Mesh and rebooted a bunch of times, to no avail, and I don't know how else to troubleshoot it.


Attachments:
NRService_20171108_113853_.log [194.08 KiB]
Downloaded 208 times
Top
 Profile  
 
 Post subject: Re: TAP configuration problem
PostPosted: Thu Nov 09, 2017 7:00 am 
Offline

Joined: Wed Nov 08, 2017 6:44 am
Posts: 3
Just to expand on the above, the VerifyTap function was returning many ip addresses:

Quote:
2017-11-08 11:42:15,243|03680|04984|D|TAP is created.
2017-11-08 11:42:15,243|03680|04984|D|NRTAP Driver Version 1.0
2017-11-08 11:42:15,243|03680|04984|D|NRTAP MTU=1300
2017-11-08 11:42:15,243|03680|04984|E|Tap is connected.
2017-11-08 11:42:15,243|03680|04984| |-[CNicDevice::InitDeviceWithStaticIP](hr=0x0)
2017-11-08 11:42:15,243|03680|04984| |-[CNicDevice::_InitializeTap](hr=0x0)
2017-11-08 11:42:20,244|03680|04984| |+[CNicDevice::VerifyTap]
2017-11-08 11:42:20,245|03680|04984|D|VerifyTap: found 192.168.232.1
2017-11-08 11:42:20,245|03680|04984|D|VerifyTap: found 192.168.220.1
2017-11-08 11:42:20,245|03680|04984|D|VerifyTap: found 192.168.169.1
2017-11-08 11:42:20,245|03680|04984|D|VerifyTap: found 192.168.240.1
2017-11-08 11:42:20,245|03680|04984|D|VerifyTap: found 192.168.44.1
2017-11-08 11:42:20,245|03680|04984|D|VerifyTap: found 192.168.207.1
2017-11-08 11:42:20,246|03680|04984|D|VerifyTap: found 192.168.0.15

2017-11-08 11:42:20,246|03680|04984| |-[CNicDevice::VerifyTap](hr=0x80004005)


But picking up attempting to troubleshoot again today, I've tried reinstalling Mesh, and now everything seems to be working normally:

Quote:
2017-11-09 11:51:43,744|11316|16836|D| "C:\WINDOWS\system32\netsh.exe" interface ipv4 set address 59 static 172.16.0.2 255.255.0.0
2017-11-09 11:51:43,921|11316|16836|D| ExitCode = 0
2017-11-09 11:51:43,921|11316|16836| | -[CNicDevice::RunCommand](hr=0x0)
2017-11-09 11:51:43,921|11316|16836|T| already initialized
2017-11-09 11:51:43,921|11316|16836|D| Setup NRTAP driver to set a static IP/netmask/gw of 172.16.0.2/255.255.0.0/172.16.0.2 on interface {08DB259B-5C8C-4AF9-AC59-AA4F0DC121C7}
2017-11-09 11:51:43,921|11316|16836|D| TAP is created.
2017-11-09 11:51:43,921|11316|16836|D| NRTAP Driver Version 1.0
2017-11-09 11:51:43,921|11316|16836|D| NRTAP MTU=1300
2017-11-09 11:51:43,921|11316|16836|E| Tap is connected.
2017-11-09 11:51:43,921|11316|16836| | -[CNicDevice::InitDeviceWithStaticIP](hr=0x0)
2017-11-09 11:51:43,921|11316|16836| | -[CNicDevice::_InitializeTap](hr=0x0)
2017-11-09 11:51:48,922|11316|16836| | +[CNicDevice::VerifyTap]
2017-11-09 11:51:48,930|11316|16836|D| VerifyTap: found 172.16.0.2
2017-11-09 11:51:48,930|11316|16836| | -[CNicDevice::VerifyTap](hr=0x0)


and 'ipconfig /all' returns:

Quote:
Ethernet adapter Ethernet 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NeoRouter Virtual Network Interface
Physical Address. . . . . . . . . : 00-FF-08-DB-25-9B
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::996e:b32f:8367:4ff1%59(Preferred)
IPv4 Address. . . . . . . . . . . : 172.16.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 989921032
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-75-C9-A1-34-17-EB-A8-46-93
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled


I've not changed anything! Just booted this morning as normal, and installed the latest Mesh... which is exactly what I tried yesterday when it didn't work. Weird. Will keep a close eye on it.


Attachments:
NRService_20171109_115140_.log [94.45 KiB]
Downloaded 208 times
Top
 Profile  
 
 Post subject: Re: TAP configuration problem
PostPosted: Thu Nov 09, 2017 9:44 am 
Offline

Joined: Sun Nov 16, 2008 6:41 am
Posts: 1868
Hi chris thomas,

Since Win10, it may take longer time to activate the network modules, especially the first reboot after Windows applied updates. By default NeoRouter will wait up to 3min for Windows to load its network modules, then continue. If it takes longer time, NR may not wait for it and the nrtap failed to assign the virtual IP. However you can change the settings in the Feature.ini , so that NR can wait for longer time.

Here are default settings:

[Default]
TapRetryTimes=12
TapRetryPeriod=10
TapVerifyInterval=5

TapRetryTimes - Max number of retry times to activate Tap
TapRetryPeriod - Before next Tap activation, it waits for n seconds
TapVerifyInterval - Before verifying Tap status, it waits for n seconds
It means that by default, NR wait up to 3 mins ((10+5) X 12) to assign VIP to nrtap. NR will check if the VIP gets assigned to the nrtap, if not , then try it again until the retry time's out.

I think you can try to change the parameter to longer time (say 5min or 10min) see if it works for you.

For more information, please refer to NeoRouterWiki:ConfigurationFiles

Thanks,
KevinZ - NeoRouter team


Top
 Profile  
 
 Post subject: Re: TAP configuration problem
PostPosted: Thu Nov 09, 2017 9:52 am 
Offline

Joined: Wed Nov 08, 2017 6:44 am
Posts: 3
Thanks Kevin. If I experience similar issues in future, I'll give this a try first.

Chris.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 1 guest


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 post attachments in this forum

Search for:
Jump to:  
cron