Our products listed at:


The premiere site for DotNetNuke modules and skins.

You are here > Support > Forums
Forum
 
ForumForumSoftwareSoftwareSeeleyWare.Auto...SeeleyWare.Auto...IP Lockdown by subnetIP Lockdown by subnet
Disabled 
Previous
 
Next Next
New Post
 3/8/2008 11:53 AM
 

Jon,

My appologies for not reading the QA at Snowcoverd more closely.  You did mention there, that IP ranges could be used.

New Post
 3/8/2008 1:50 PM
 

No problem at all... I really need to add it into my documentation (it is a fairly recent change, but not recent enough that I have any excuse to not have it in my documentation).

Let me know if there is anything else I can do to assist.  I'm still going to look into the subnetting, I think that would be a very nice addition.

New Post
 3/10/2008 9:24 AM
 

Jon,

I could not get the range entry to work.  Is it limited somehow to only 192.168.x.x networks.  I tried entering in 172.16.7.1-172.16.7.40 and I could not get it to work.  Any suggestions?

New Post
 3/10/2008 9:58 AM
 

Moving through the code line by line I identified the problem -- it wasn't checking the actual IP address into the range (I don't know how I never caught that before), but it was trying to parse the entire range into an IP address and check that against itself.

I have patched it and will be releasing the patch to SnowCovered shortly (and email to you directly as well). 

Thanks for the catch, and I apologize for that.


Jon Seeley
SeeleyWare, LLC
New Post
 3/10/2008 10:07 AM
 

No apology necessary.  This is great work.

Disabled 
Previous
 
Next Next
ForumForumSoftwareSoftwareSeeleyWare.Auto...SeeleyWare.Auto...IP Lockdown by subnetIP Lockdown by subnet