Jump to content
Not connected, Your IP: 35.175.191.168

Search the Community

Showing results for tags 'netgear'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

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 4 results

  1. I have a Netgear Nighthawk R7800 that I am trying to run AIRVPN on. I'll admit I'm not the most computer savvy person but I can usually figure things out. This has me stumped. If anyone can help me out, I would really appreciate it. I've had my AIRVPN subscription for over a month now and I cannot get the thing figured out.
  2. Hi, Recently I re-used an old Netgear WNR3500 v2 I had lying around and put dd-wrt on. I followed the tutorial on here and got it all working :-) So my network at home is as followed *Cisco 867VAE-K9 as my VDSL router - connects to my ISP and offers DHCP for local devices. *Netgear WNR3500 plugged into Cisco router I use the range 192.168.0.0/24 for my home network such that :- 192.168.0.254 - ISP gateway via my CISCO - so most devices use this 192.168.0.251 - VPN tunnel gateway via Netgear - so any devices to use VPN point to this gateway and also change DNS server to be VPN DNS server etc. The Netgear's WAN port is configured to be 192.168.9.250 with its gateway pointing out to the CISCO on 192.168.0.254 My initial test is as below. Down: 17.289 Mbit/s Out, 6.271 Mbit/s In (36%), 20MB - Up: 6.585 Mbit/s Out, 3.183 Mbit/s In (48%), 20MB - Date: Sun, 13 Dec 2015 20:27:45 GMT - Buffers: 20MB/20MB - Laps: 3, Time: 178.81 secs Does this setup seem ok, I think my speed is limited by the CPU in the router or could it be I just need to try a different server etc ? CPU ModelBroadcom BCM4716 chip rev 1 CPU Clock453 MHz Thanks !!
  3. I looking through the forum archives to determine the best VPN router brand and OS. 1. Is a Sabai OS router "better" than DD-WRT? http://www.routersource.com/netgear-nighthawk-r7000-powered-by-sabai-os/ 2. Does anyone have experience with Sabai OS? 3. I am looking at the ASUS versus Netgear. I think I am looking at ASUS being the most popular amongst AirVPN users. Why? I just want to hear other person's thoughts on the matters above. Thanks ...
  4. People (who are involved in IT security in first place) read about the open port 32764 in routers from Cisco, Linksys, Netgear and Diamond having strange backdoor access to the configuration files of those routers. Long story short, there is a service listening on this port which accepts a variety of commands such as resetting the router or printing out all kinds of information, even passwords in plain text. Connecting to the router through telnet should return the string "ScMM" or "MMcS" if the service is running (it's for SerComm). It could be smart to check if your Cisco/Linksys/Netgear/Diamond router is listed here. Or use this python script. Or just connect to your router via telnet [your.router.ip] 32764 and see if you get one of the aforementioned strings back. Source #1 Source #2 ---- Update #1 ---- First statements of manufacturers Linksys and Netgear. Both of them allegedly are "going through all possible vulnerabilites" and will publish more information on this after they did some analyzing. Fact is that they didn't even warn the users of those routers... strange, too... Source ---- Update #2 ---- Cisco released a Security Advisory and is working on a fix. There are no workarounds so you have to wait for Cisco's update. ---- Update #3 ---- It's not over!
×
×
  • Create New...