Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Restrict IP addressRestrict IP address
Previous
 
Next
New Post
10/10/2013 11:11 AM
 

I want to restrict acces for a specific user (or role) based in it's IP address.

This functionality is said to be new in DNN 7.1.0. I'm currently running 7.1.2, but I can't find where/how I could configure such a restriction. Where can I fint this?

(FYI: I want to limit access to my web service)

 
New Post
10/10/2013 1:39 PM
 

Host Settings -> Advanced Settings -> Login IP filters

But to be honest, it is useless IMHO because you can block me by my current IP address but I'll be back through a proxy...

 
New Post
10/10/2013 3:17 PM
 

you can find the setup details in the help - http://www.dnnsoftware.com/help#Docum... filters .

IP blocking is intended for scenarios where a network has both a public IP (e.g. 82.24.96.98) and a private IP (e.g. 192.168.27.0/24) and you want to ensure that only users on the private IP address range can log in. In that case you would access the site from an internal address (192.168.27.0/24) and then set 82.24.96.98 as a deny - you can now remove the * -this configuration will mean admin/host users can only log in when on the 192.168.27.0/24 private network.

There is no current way to block an IP you are accessing on (such as 192.168.27.0/24) as that would stop you from logging in and changing the settings (this differs from the IP restrictions in say IIS which will allow you to block your current IP)

Note: it also supports only allowing certain public IPs e.g. if I accessed dnnsoftware.com via my IP (82.24.96.98) I could set an allow rule for that IP address and then delete the * - now only I can login as admin/host if I am accessing via 82.24.96.98 i.e. no other public or private IP's/IP ranges can log in. However as Mariette correctly stated, a public IP address can be spoofed (via a http proxy/altered request/vpn etc.), so if a hacker can guess the right IP/IP range to use this is of limited protection (unlike the public/private divide as private IP's such as 10.0.0.1 are non internet routable)


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
10/11/2013 3:44 AM
 

Yes, it would be useless to block a small amount of IP addresses (or even a whole continent), but I would like to use it to block everything and only allow a small range, to allow the webservice user only access from our server(s) and to allow access to a certain module only when inside the builiding.

To breach that, you would need a proxy inside our server/building.

 
New Post
10/11/2013 4:35 AM
 

Thank you both for the location of the setting and the documentation.

I've read that the IP filter only applies to host and admin users, although the documentation speaks of ip adresses logging in. (And are you allowed to stay logged in when switching to a blocked ip address? Does this hide the login link? questons ,questions..) Anyway, a filter for all users together is of little use. I had hoped for (and expected) a role based filter.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Restrict IP addressRestrict IP address


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out