Feature Request for Wingate (IP BLOCKING)

[trialtester2999]

Hi, we are in the dormitory business and currently we are evaluating your Wingate 5.2.3 and Wingate 6.0 Beta 3, we really liked your software because internet through wingate is very fast as compared to winroute firewall 6.0 and its easier to manage however, my question or request for future development of your system to 6.1 is the IP BLOCKING feature, we have 40 tenants using the internet through wingate 5 & 6 but as soon as their subscription period is over, we have to use IP Blocking to block their usage in their PCs but sometimes this hard-headed tenants would just plainly change their IP address to access the internet again. Is there a possibility that multiple IP addresses would just be entered as one range so that input of single IP addresses would be phased out since this is very ineffective at some time? Your software has a very good potential for Hotel and Dormitories but you may have to look into this matter. I've seen some requests on the same topic and this new topic that I have created is just a follow up.

[dreamramon]

agreed , we would be very glad if wingate adds a function such like assumed by mac address of adapters..

[adrien]

You can enter whole ranges of IP addresses into the black hole list by using the network mask.

For instance to block all the range 192.168.0.1 to 192.168.0.254, you would specify address of 192.168.0.0 and mask of 255.255.255.0

This is similar to the way routes are created in routers.

Another option you could consider is making your users log in. WinGate 6.0 supports authentication through the WWW Proxy. Furthermore if your users are running Internet explorer, and have windows user accounts on the WinGate server, their authentication can be automatic.

Adrien

[mikebos]

Hi All,

Adrien your say "Furthermore if your users are running Internet explorer, and have windows user accounts on the WinGate server, their authentication can be automatic."

Do you mean the NT User database? How is this done? or do you mean they can be assumed automatically?

I have been trying to get MAC verification to work to stop clients changing their IP addresses and Computer names to pirate traffic with unpredictable results.

If I set DHCP policy IP=MAC it refuses to assign an IP OK, but if client sets fixed IP WG serves traffic anyway.

If I set WG policy Everyone assumed and, user1 = assume + MAC1, user2 = assume + MAC2, etc. I get mixed results.
First user1 works perfectly.
Adding user2 etc. usually stops everyone sometimes it doesn't.
Sometimes a user with a legit assumed name but different MAC gets in.
If I set everyone authenticate, user1 assume etc. no-one gets in.

A simple assume by MAC address would be secure heaven.

Till then, How do we lock an assume to a MAC address.

Regards
Mike Bos.