Woo ok so now I've made that change I am now able to get "Connected" (albeit, after about 30 seconds). But I can't access things in my home network like I could prior to changing to Bridged mode
Client log
Quote:
2016-02-18 18:09:01 TUN/TAP device /dev/tap0 opened
2016-02-18 18:09:01 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
2016-02-18 18:09:01 MANAGEMENT: >STATE:1455818941,ASSIGN_IP,,192.168.1.50,
2016-02-18 18:09:01 /sbin/ifconfig tap0 delete
ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
2016-02-18 18:09:01 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2016-02-18 18:09:01 /sbin/ifconfig tap0 192.168.1.50 netmask 255.255.255.0 mtu 1500 up
2016-02-18 18:09:01 /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -a -d -f -m -w -ptADGNWradsgnw tap0 1500 1573 192.168.1.50 255.255.255.0 init
**********************************************
Start of output from client.up.tunnelblick.sh
Configuring tap DNS via DHCP asynchronously
End of output from client.up.tunnelblick.sh
**********************************************
2016-02-18 18:09:03 Initialization Sequence Completed
2016-02-18 18:09:03 MANAGEMENT: >STATE:1455818943,CONNECTED,SUCCESS,192.168.1.50,79.68.12.129
Sleeping for 0 seconds to wait for DHCP to finish setup.
Sleeping for 1 seconds to wait for DHCP to finish setup.
Sleeping for 2 seconds to wait for DHCP to finish setup.
Sleeping for 3 seconds to wait for DHCP to finish setup.
Sleeping for 4 seconds to wait for DHCP to finish setup.
WARNING: No DNS information received from OpenVPN via DHCP, so no network/DNS configuration changes need to be made.
Will NOT monitor for other network configuration changes.
DNS servers '172.20.10.1' will be used for DNS queries when the VPN is active
The DNS servers do not include any free public DNS servers known to Tunnelblick. This may cause DNS queries to fail or be intercepted or falsified even if they are directed through the VPN. Specify only known public DNS servers or DNS servers located on the VPN network to avoid such problems.
Flushed the DNS cache via dscacheutil
/usr/sbin/discoveryutil not present. Not flushing the DNS cache via discoveryutil
Notified mDNSResponder that the DNS cache was flushed
2016-02-18 18:09:04 *Tunnelblick: No 'connected.sh' script to execute
2016-02-18 18:09:09 *Tunnelblick: This computer's apparent public IP address (85.255.235.244) was unchanged after the connection was made
Maybe something to do with the DHCP settings?
This is my ifconfig output on client, it has two IP addresses which I don't really understand.
tap0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether ee:14:7f:d5:a9:12
inet 192.168.1.50 netmask 0xffffff00 broadcast 192.168.1.255
inet 169.254.52.64 netmask 0xffff0000 broadcast 169.254.255.255
media: autoselect
status: active
open (pid 1273)
Nope, I can't ping by IP to my home freenas or router etc.
(request time out) but I can ping google.com
Adding those client params to my client config meant that I could not even access the internet anymore (ping google.com failed)
Quote:
2016-02-18 20:09:13 Tunnelblick[372] currentIPInfo(Name): IP address info could not be fetched within 16.0 seconds; the error was 'Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://www.tunnelblick.net/ipinfo, _kCFStreamErrorCodeKey=-2102, NSErrorFailingURLKey=https://www.tunnelblick.net/ipinfo, NSLocalizedDescription=The request timed out., _kCFStreamErrorDomainKey=4, NSUnderlyingError=0x784160 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSErrorFailingURLStringKey=https://www.tunnelblick.net/ipinfo, NSErrorFailingURLKey=https://www.tunnelblick.net/ipinfo, NSLocalizedDescription=The request timed out., _kCFStreamErrorDomainKey=4}}}'; the response was '(null)'
2016-02-18 20:09:13 Tunnelblick[372] tcp_connection_destination_perform_socket_connect 11 connectx to 205.233.73.116:80@0 failed: [65] No route to host
2016-02-18 20:09:13 Tunnelblick[372] tcp_connection_destination_perform_socket_connect 11 connectx to 205.233.73.116:80@0 failed: [65] No route to host
2016-02-18 20:09:14 Tunnelblick[372] tcp_connection_destination_perform_socket_connect 12 connectx to 205.233.73.116:80@0 failed: [65] No route to host
2016-02-18 20:09:14 Tunnelblick[372] tcp_connection_destination_perform_socket_connect 12 connectx to 205.233.73.116:80@0 failed: [65] No route to host
2016-02-18 20:09:15 Tunnelblick[372] tcp_connection_destination_perform_socket_connect 13 connectx to 205.233.73.116:80@0 failed: [65] No route to host
2016-02-18 20:09:15 Tunnelblick[372] tcp_connection_destination_perform_socket_connect 13 connectx to 205.233.73.116:80@0 failed: [65] No route to host
2016-02-18 20:09:16 Tunnelblick[372] tcp_connection_destination_perform_socket_connect 14 connectx to 205.233.73.116:80@0 failed: [65] No route to host
I can't seem to get it to work on my work laptop, I think there is a problem because of the virtual infrustructure getting in the way. Arghh I really need to get this working before I go away for a couple of weeks on Sunday ha. I'm going to work at it this evening
OK so I did some more tests while connected to the VPN, I still cannot ping any of my internal structure but this was interesting:
Jamies-MacBook-Pro:~ Jamie$ arp -a
...
? (192.168.1.1) at (incomplete) on tap0 ifscope [ethernet]
? (192.168.1.2) at (incomplete) on tap0 ifscope [ethernet]
? (192.168.1.4) at (incomplete) on tap0 ifscope [ethernet]
? (192.168.1.5) at (incomplete) on tap0 ifscope [ethernet]
? (192.168.1.100) at (incomplete) on tap0 ifscope [ethernet]
? (192.168.1.255) at (incomplete) on tap0 ifscope [ethernet]
The above addresses are the only addresses currently in use on my home network (.100 being my laptop) which is strange. I'm not really sure what this means though ha some problem with translation from internet layer to link layer ?
Also notices my netmask is represented different on my tap0 which is weird:
inet 192.168.1.50 netmask 0xffffff00 broadcast 192.168.1.255
Tried messing around with some firewall rules but nothing is working :/
Just to clarify, these are my current setups: (NO scripts in the Command section)
Quote:
remote *dyndnshere* 1194
client
dev tap
proto udp
resolv-retry infinite
nobind
persist-key
persist-tun
float
Edit: still no dice with the dhcp proxy option, Only change I see is my tap0 now only has one IP / broadcast instead of two like before:
tap0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 52:70:46:54:65:b3
inet 169.254.17.50 netmask 0xffff0000 broadcast 169.254.255.255
media: autoselect
status: active
open (pid 12813)
I can't see anything online saying that it doesn't support it. As far as I know, it's just an OSX implementation of openvpn client for windows
I need to head to sleep now, 2.30am my time. Thanks very much for your help. I'm going to try and crack on again tomorrow but I'm a bit lost with what to do now.
Here is my log from my client. I also noticed I have a tap0 and also a tap1 on my OSX which may be causing some problems. (When i restart my mac, I don't have any tap interfaces until I begin the vpn stuff.
Ok so I've reset the router to factory settings, and then configured the open vpn server, using exactly the same config as before and the same client config also.
Here's the output from my client log on pastern (if you can be bothered to look at it http://pastebin.com/Rfxb8Mwe ) . I can't see anything interesting in there, apart from perhaps the output of ifconfig might be significant (maybe theres some error still in bridging into my network).
Are there any other tests that you can think of that I can perform? I'm lost really.
