Wingate as an ISP

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Wingate as an ISP

Postby administratorkaycee » Dec 26 03 10:16 pm

I am looking at setting up a small ISP and looking at using wingate with its NAT features to do this. Also I would have various hotspots around town to access this network via 802.11b.

I would like to know about how I can throttle bandwidth from the internet only to the individual users. They should have full access to the file servers on my network. Can wingate do this???

I am only expierimenting with various server designs at the moment.
administratorkaycee
 
Posts: 2
Joined: Dec 26 03 10:09 pm
Location: Napier

Postby administratorkaycee » Dec 26 03 10:19 pm

By throttling I mean sharing a 8000k internet connection and sharing it equally between the individual users so they can all access the net through the shared connection at, at least 128k

They should have full speed access to the servers on my network that I allow.
administratorkaycee
 
Posts: 2
Joined: Dec 26 03 10:09 pm
Location: Napier

Postby snake » Dec 27 03 4:54 am

Hello,

I already have a WISP using Wingate as my main gateway, and it works fine, though wingate doesn't have bandwidth throttling.

For primitive bandwidth throttling you can use Bandwidth Controller:

http://www.bandwidthcontroller.com

Bandwidth Controller only works on Windows 2000 and XP. Also, it currently supports only 50 shaping rules.

If you are going to use Wingate as your ISP's main gateway be aware of the following shortcomings:

-It doesn't route public IP addresses or address ranges.
-No bandwidth control
-no UPnP
-Many people have problems with the NAT after version 5.07 because Qbik changed the architecture after it split with Deerfield
snake
 
Posts: 4
Joined: Dec 22 03 3:21 am

Postby adrien » Dec 27 03 7:52 pm

Actually

a) WinGate does route public IPs. If you are having problems which led you to this conclusion, maybe we can help you sort those out
b) the change in architecture was nothing to do with splitting from Deerfield, it was coincidental. The main reasons we changed the architecture were due to compatibility issues with the old one. In a short time with the new system we have a higher level of stability than the old one which took 2 years to get to that stage. Once we sort out these special connection types, we are in a much better position to build on.

It is only certain types of connections that we have issues with as well, such as some satellite, and some USB network adapters.

As for bandwidth control, actually the driver that ships with 5.0.8 and later supports it, we just need to finalise a UI to allow the user to configure it, so that feature is not far off.

UPnP we are also investigating further as well.

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland


Return to WinGate

Who is online

Users browsing this forum: No registered users and 7 guests

cron