Wireless Access

There's got to be a way to do this:

760WL manages the AP 420s on my "public" side. All wireless connections are NAT'd and the APs are sitting on VLAN 2.

i.e.

Network is 192.168.x.x VLAN 1
APs are 42.0.x.x VLAN 2
Everyone is behind the firewall, including the web server.
Users on wireless need to access our web server - but can't (web page not found, blah, blah...)

It isn't a DNS issue, it's a routing issue. Is it possible to write a filter that will redirect requests for our web server that's on VLAN 1?

(I am configured this way to provide public access for our customers but keep them from seeing our company LAN.)

Mark

Hi

What kind of authentication you have, if you have integrated IAM with LDAP so it uses Windows domain users, then all guests are not allowed to access anything in your Trusted network (LAN) except the Internet, and all the users login to the IAM using their Windows Domain account will be having access to all resources.

This is the Default procedure, i have implemented a same scenario using the IAM 760 and it works fine.

Anyway, you can use a new Access Policy for Guests to allow them access the Web Server.

Anyway you can use the : HTTP Proxy Filters,
within the Access Policy (under the HTTP Proxy Tab), to add a new server.

Note:
Routing between Trusted and Untrusted worlds is controlled by the ACCESS POLICIES, not by static route or routing table.


Don;t forget to assign points.

Good Luck !!!

Authentication: currently, just the Guest access. I don't want anyone on the public side of the net to see the private side - except for the web server. I do have future plans for LDAP, but not at this time.

(If the rest of your message is dependent on LDAP authentication, then it looks like my problem isn't fixable with the scenario I want to implement. )

>Anyway, you can use a new Access Policy for Guests to allow them access the Web Server.

This is what I've been trying to do. Do I need to create a "guest" account in my AD and use LDAP autentication to get this to work?

>Anyway you can use the : HTTP Proxy Filters,

I'll play with the HTTP Proxy Filters and see if I can force it to work for Guests.

>Note:
Routing between Trusted and Untrusted worlds is controlled by the ACCESS POLICIES,

This is what I was trying to do.

I'll keep playing with it.

Thanks.

Hi Mark

If your case is only Guest Account, and you want tp prevent them to access your LAN (Which is default), you dont need to play with their default account.

What you need exactly is the: The Redirected Traffic Filters, in the Access Policy page.

There you configure a new redirected filter to guide the Guest after login to your Web Server.

Please refer to the management and Configuration Guide :
ftp://ftp.hp.com/pub/networking/software/700wl-Mgmt-and-Config-v4-1-3-93.pdf

Don;t forget to assign points to the posts.

Good Luck !!!

Thanks for the reference. That's the document I was using (I need to check the version number...) and Redirection was what I was trying to configure. I just couldn't get it to work. Now that I know it should, I'll just keep hammering away at it until I beat it into submission!

You've been a big help. I'll get the points assigned.