Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 4 subscribers
  • Views 4768 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is it possible to use an internal "walled garden" for data capture post logon?

BassManager

We use our UTM9 to provide 3 wifi guest networks and a private staff network. The three guest networks have different features and services, all dependent upon the price paid to get access. I would like to be able to record names and email information after logon. I've experimented with creating another network and defining this as a "walled garden" and then putting a small server on this network to capture the information. I've then set the guest networks to redirect to this server post logon. The problem is I can't seem to get this to work as expected. After the normal logon screen is display, after voucher code entry, there is a message saying that you have tried to be directed to xxxx webpage, but you will be directed to 172.16.27.1 (which is my data capture server). If you then click on the link to the ip address an error message is created saying the device cannot be reached.

I've used the tools on the web admin page and my server 172.16.27.1 quite happily responds to pings, and when I plug it into another network I can verify that the server is running properly. So I guess I have two questions really.

1. Is there anything I can do to get the post login to redirect automatically without it printing a link that you have to click onto, because no user is really going to do that. They just want to get on with surfing the web.

2. Am I making bad assumptions in the first place, and an an internally located "walled garden" is the wrong way of doing this? Is this kind of re-direction never going to work and I really need to have an external server that collects emails and names post logon?



This thread was automatically locked due to age.
  • 0

    "I've then set the guest networks to redirect to this server post logon." - Please insert a picture of this.

    Isn't the information in the Wireless Protection log adequate, but just not organized to fit your needs?

    Cheers - Bob

  • 0 in reply to BAlfson

    The data retention regulations 2009 (EC859) say I need to log the name of the user associated with the IP I issue them with on our network. The only way I see that I can do this is to get the user to redirect to another page after logon and get them to enter their details. This information is also useful from a mailing list point of view. Of course, if there is a better way of doing this I'm open to suggestions

  • 0 in reply to BassManager

    Why not just use DHCP from the Windows server?  See DNS Best Practice.

    Cheers - Bob

  • 0

    Thanks for the replies. I have managed to get everything working as expected, but not as I want. There were a few things I had to "tweak" but nothing major that I should have remembered anyway. I ended up setting the data capture server in a walled garden network that was accessible from all wifi networks.

    I then became confused because the redirection was taking place, but only on the "password of the day" network. As soon as I tried with a voucher access network, no redirection was taking place. After digging through the documentation I found this :(maybe I should have done that earlier, but you know what they say about documentation and techies)

    Redirect to URL after login: If selected, after entering the password or the voucher data, the users will be redirected automatically to a particular URL, e.g., your hotel's website or a webpage stating your portal system policies.

    • URL: URL to which the user is redirected.

    Note – When you select hotspot type Voucher the Redirect to URL after login does not automatically redirect to the configured URL. Users will be redirected to a statistics page which contains important information about the voucher, e.g. period of validity. Users will be able to continue to the configured URL when they click on the link: You will be redirected to [URL].

    Now IMHO this is completely useless. If I want a user to go to my custom page and see the portal policies, as indicated in the first paragraph, then there is no way I can force them to do it. They just simply ignore the link at the bottom of the statistics page and go on their merry way. So how come I can force users who logon to the POD network to go where I want to first, and those with vouchers can do whatever they want.

    Personally, I think this is a mad idea and I would like it changed.

    Who can I talk to to get this "fixed"?