HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Communications and Wireless
- >
- Help with Wireless NAT on wifi module in 5400
Communications and Wireless
1836358
Members
2537
Online
110100
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2009 10:07 PM
01-22-2009 10:07 PM
Help with Wireless NAT on wifi module in 5400
I have a 5406zl with a wireless module installed. The goal is to use one IP from the ip pool from the private network (on the 5406) let's call it 10.20.30.10 and use a NAT to hand out a different range to publicly accessible wifi off the wireless module.
It's been 2 years since I touched the procurve stuff here as a former employee did most of this stuff...
I do have the wireless module up and going, and can get on my network with a dhcy relay, but need to setup the 'private' side using a NAT for public access that doesnt get to our private network.
Can someone explain what I need to do web or command line to setup a NAT for this? I spent considerable time goign through the ProCurve 1100 page manual and just dont get it...
It's been 2 years since I touched the procurve stuff here as a former employee did most of this stuff...
I do have the wireless module up and going, and can get on my network with a dhcy relay, but need to setup the 'private' side using a NAT for public access that doesnt get to our private network.
Can someone explain what I need to do web or command line to setup a NAT for this? I spent considerable time goign through the ProCurve 1100 page manual and just dont get it...
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2009 02:28 AM
01-26-2009 02:28 AM
Re: Help with Wireless NAT on wifi module in 5400
What's the reason to use NAT?
NAT is used
- when you got a limited number of public adresses to translate to local adresses
- when you DO want to access local hosts, but want to mask the real internal adresses to this "outside" network
So you don't really need NAT to do the thing you describe.
You need an ip-subnet on the wireless network, and you need a way not to allow trafic from the wireless to the private network.
one way to do the last thing is to NOT enable routing between those networks.
(not on the 5400 and not in the wireless module).
another way is to filter trafic using an accesslist.
a third is to separate trafic using vlan's.
In this process you also may configure the wireless module to be dhcp-server for the wireless network?
So wireles clients don't even need access to the private network to get an ip-adress.
NAT is used
- when you got a limited number of public adresses to translate to local adresses
- when you DO want to access local hosts, but want to mask the real internal adresses to this "outside" network
So you don't really need NAT to do the thing you describe.
You need an ip-subnet on the wireless network, and you need a way not to allow trafic from the wireless to the private network.
one way to do the last thing is to NOT enable routing between those networks.
(not on the 5400 and not in the wireless module).
another way is to filter trafic using an accesslist.
a third is to separate trafic using vlan's.
In this process you also may configure the wireless module to be dhcp-server for the wireless network?
So wireles clients don't even need access to the private network to get an ip-adress.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP