Search the Community
Showing results for tags 'local'.
Found 3 results
Hi, I cannot access or see my Ubuntu 16.04 computer without starting Eddie with network lock enabled. I access this computer remotely within my LAN. I installed Eddie/Airvpn remotely with no issues. I was able to activate network lock and access the VPN service. Once I restarted my Ubuntu machine I could not see it remotely. I have to enable the network lock to get access to my network. I am running the ubuntu machine headless. I have tried using commands to start the airvpn client automatically, as this would suffice. However, I cannot get that to work, and if it did, Eddie GUI has a password prompt that I cannot manipulate remotely. Anyone have an idea where I should start? PS: My ubuntu knowledge is limited to about 20 hours of intense googling, and successfully running samba/VNC with local connectivity. I am quite familiar with PC terminology though. EDIT: Semi-resolved: I added "iptables --policy INPUT ACCEPT" to rc.local. The accept policy is persistent even when Eddie is running(Eddie adds rules below it). Remote protocol is working. Samba server is no longer able to start due to upstart error if Eddie is not started with network lock on.
Goal: get https://github.com/jishi/node-sonos-http-api to find my local Sonos devices Mac: running AirVPN, Local IP: 10.0.1.150 Sonos: IP: 10.0.1.19 When AirVPN is not connected, and I run the node server from the URL above, the server quickly finds the Sonos speaker and connects. However, once I connect to AirVPN, the server endlessly loops with: scanning for players in ip 10.0.1.150 scanning for players in ip 10.4.18.107 <-- AirVPN IP If I go to AirVPN --> Preferences --> Routes --> "Not specified routes go: Outside the VPN tunnel," it works. However, I know that effectively stops the benefit of AirVPN. So, if I set AirVPN --> Preferences --> Routes --> Not specified routes go: Inside the VPN tunnel, and set an IP Range of 10.0.1.0/24, it does NOT work and endlessly loops scanning. Am I understanding the routes table correctly? I'm so not privy of CIDR formats, but I think I understand that 10.0.1.0/24 means 10.0.1.1 - 10.0.1.254, correct?
Hi there, I'm running Eddie AirVpn Client software version 2.8. I configured airvpn with some local traffic white listed (both Outside the VPN tunnel - 192.168.0.0/16 and manually in network lock). However, I cannot get any local traffic to pass through.. Upon inspecting the pf rules, I see the following: sh-3.2# sudo pfctl -sr No ALTQ support in kernel ALTQ related functions disabled block drop out inet all pass out quick inet from 10.0.0.0/8 to 10.0.0.0/8 flags S/SA keep state pass out quick on utun0 inet from 10.0.0.0/8 to any flags S/SA keep state pass out quick inet from any to <__automatic_bb554c31_0> flags S/SA keep state pass out quick inet from 172.16.0.0/12 to 172.16.0.0/12 flags S/SA keep state pass quick on utun0 inet from any to 10.0.0.0/8 flags S/SA keep state pass quick on lo0 all flags S/SA keep state It does not look like the 192.168.0.0 rule is there... However, The generated temp file in ~/.airvpn/1c1d81cef74e0d65fd179c59ad525579da19fc6d5e4142dbed5a8efd55b1041d.tmp.pf.conf correctly generates the rules: ... .... # Private networks pass out quick inet from 192.168.0.0/16 to 192.168.0.0/16 flags S/SA keep state pass out quick inet from 172.16.0.0/12 to 172.16.0.0/12 flags S/SA keep state pass out quick inet from 10.0.0.0/8 to 10.0.0.0/8 flags S/SA keep state # Allow all on lo0 pass quick on lo0 all # Everything tunneled pass out quick on utun0 inet from 10.0.0.0/8 to any flags S/SA keep state pass quick on utun0 inet from any to 10.0.0.0/8 flags S/SA keep state Any help will be appreciated.Thanks