Jump to content
Not connected, Your IP: 18.97.14.89

Search the Community

Showing results for tags 'rules'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • DNS Lists
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 2 results

  1. Hello, I have this problem which is not going away since I installed Eddie. It occurs with stable Eddie 2.10 and the new 2.11.3 beta. Installed new windows 10 x64, no anti-virus software whatsoever, only windows firewall and windows defender (I somehow can't deactive windows defender) I did not changed windows firewall settings. The mainboard got only 1 ethernet port. Router is working with no errors. I did not configure the router - just installed and it worked 100%. Cut to the chase: Case 1: - My internet connection is only working, when Eddie is running and I'm connected to an airvpn-server. Whether Windows firewall is running or not, doesn't matter. Whether network lock is enabled/disabled doesn't matter. With this, I can do everything: browse internet, listen to internet radio stream, play online games. http://www.pic-upload.de/view-31678207/working.png.html Case 2: - Eddie is running but not connected to an airvpn server, network lock is deactivated; windows firewall enabled/disabled The tap-windows-adapter V9, which was installed during the Eddie installation, is disconnected (windows diagnosis: Ethernet cable is not connected). I can't browse website, listen to internet radio BUT I can play my online game unreal tournament 2004. Peculiar: I can't browse or whatsoever, BUT whenever I try to load a website, the orange mainboard LED (ethernet port) begins to blink - this means it's up and working. The green LED is always on, indicating that the hardware is working. http://www.pic-upload.de/view-31678297/notworking.png.html Case 3: - Eddie is closed, windows firewall enabled/disabled. Same result as in case 2, except again: UT2k4. Eddie is starting with windows. Even when I disable autostart and windows starts without eddie, I get same result as in case 2/3. As I already mentioned, there is one strange exception: it's the online game I play, u2k4. In case 2/3, I start the game, I go to the ingame tab "Servers" and the game is showing me the ut2004-servers, up and running, so I can connect to them and play online. But the even strager thing is: case 2/3 with network locked disabled (ofc. I need to disable network lock when Eddie is up and running, or else every traffic would got blocked). I start the game, go to "Join Game" and the "news feed" is showing me that the game can't connect to the "UT2k4 Master Server" -> "Querying Master Server: The UT2004 master server could not be reached. Please try again later." This normally means that I'm offline and can't connect, but as already mentioned: In the other tab, servers are shown to me and I can play online. So I thought that windows firewall/eddie set up some strange internet connection rules. I checked the windows firewall setting and reseted them to the default settings, but nothing changed. I checked HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules, there are ~100 registry keys. But as mentioned: I did not change anything. I think this is not how this Eddie is supposed to work. thanks in advance
  2. Hello and thank you in advance for any help with this. I have never ran a Tor relay before, but I would like to try to enable a "middle-man" relay through my VPN connection if it is possible. I am trying to configure the Tor "middle-man" relay using my /etc/tor/torrc file and iptables.rules file. (I have not edited the TBB torrc) My torrc is configured like this below: AutomapHostsOnResolve 1 AutomapHostsSuffixes .exit,.onion SocksPort 9050 TransPort 9040 DNSPort 9053 ##Tor-middleman Nickname ************(my secert name) ORPort 9001 DirPort 9030 BandwidthRate 256 KB # Throttle traffic to 20KB/s BandwidthBurst 4096 KB # But allow bursts up to 50KB/s ExitPolicy reject *:* and my current iptables.rules that work with AirVPN and TBB/Tor/Privoxy are: $ iptables -L -n --line-numbers Chain INPUT (policy DROP) num target prot opt source destination 1 icmp -- 0.0.0.0/0 0.0.0.0/0 icmptype 8 recent: SET name: ping_limiter side: source mask: 255.255.255.255 2 DROP icmp -- 0.0.0.0/0 0.0.0.0/0 icmptype 8 recent: UPDATE seconds: 4 hit_count: 6 name: ping_limiter side: source mask: 255.255.255.255 3 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmptype 8 4 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 5 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 6 DROP all -- 0.0.0.0/0 0.0.0.0/0 ctstate INVALID 7 UDP udp -- 0.0.0.0/0 0.0.0.0/0 ctstate NEW 8 TCP tcp -- 0.0.0.0/0 0.0.0.0/0 tcp flags:0x17/0x02 ctstate NEW 9 REJECT udp -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 10 REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 reject-with tcp-reset 11 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-proto-unreachable Chain FORWARD (policy DROP) num target prot opt source destination Chain OUTPUT (policy ACCEPT) num target prot opt source destination Chain TCP (1 references) num target prot opt source destination Chain UDP (1 references) num target prot opt source destination ----------------------------------------------------------------------------- $ iptables -t nat -L -n --line-numbers Chain PREROUTING (policy ACCEPT) num target prot opt source destination Chain INPUT (policy ACCEPT) num target prot opt source destination Chain OUTPUT (policy ACCEPT) num target prot opt source destination Chain POSTROUTING (policy ACCEPT) num target prot opt source destination If there is an easy way to do this then please let me know what I should do with ports-forward, iptables.rules, and torrc. thanks. ------------------------------------------------------------------- EDITED: I decided to edit this cause I added too much confusing info. So to keep things simple, I don't know if I need ports forwarded or if I just need some new iptables rules to make things work. (or both) Currently my Tor Browser Bundle (TBB) works on port 9150 and 9151 over my VPN connection and so does my Tor/Privoxy connection using Socks4a for port 9050 and 8118. When running both tor instances I have 6 EntryGuards to start. When I configure the "middle-man" relay in my linux /etc/tor/torrc file I get about 20-80 more ESTABLISHED connection with the original 6 ESTABLISHED EntryGuards. But after a few minutes I only have the original 6 EntryGuards as ESTABLISHED connections when using the netstat command.
×
×
  • Create New...