m (2 IP addresses) |
(→2 IP addresses: respond) |
||
| Line 1: | Line 1: | ||
| ⚫ | |||
This is a great article. Can't you avoid the problem of needing 2 IP addresses for the onboard PC by installing an onboard AP/router like the Linksys WRT54G, and then connecting it's WAN port to the Bridge? This seems to work for me using an EnGenius 3220 bridge - or am I missing something? |
This is a great article. Can't you avoid the problem of needing 2 IP addresses for the onboard PC by installing an onboard AP/router like the Linksys WRT54G, and then connecting it's WAN port to the Bridge? This seems to work for me using an EnGenius 3220 bridge - or am I missing something? |
||
| + | --[[User:John Howell|John Howell]] 09:04, 7 April 2007 |
||
| + | :Thank you. |
||
| ⚫ | |||
| + | :The problem of needing two IP addresses on the PC is due to: |
||
| + | :# IP address assigned by DHCP for access to the Internet. |
||
| + | :# IP address needed for management of a wireless Ethernet (client) bridge (''e.g.,'' EnGenius 3220) that won't necessarily be on the same subnet as IP #1. This could be avoided if the wireless Ethernet (client) bridge were smart enough to obtain its LAN management IP address from the remote DHCP server (and would thus be on the same subnet as the address assigned to the PC), but I don't know of any such devices that are smart enough to do that. |
||
| + | :If you're using the WRT54G as a: |
||
| + | :# ''Router'', then what you're doing is "double NAT", NAT #1 being the remote router and NAT #2 being your WRT54G, which will get a private IP address from the remote DHCP server, and assign its own private address to the PC. That usually works, but can cause Internet access problems, so I don't recommend it. |
||
| + | :# ''Wireless access point'' (as suggested in this article, [http://wireless.wikia.com/wiki/Wi-Fi_How_To#Use_a_wireless_router_as_a_wireless_access_point configured thusly]), then the WRT54G needs no IP address (except for management) and the PC gets its IP address from the remote DHCP server. |
||
| + | :Either way you have the problem of how to access the LAN management port of the EnGenius 3220 bridge (''e.g.,'' to select the Wi-Fi network you wish to connect to). If in config #2, for example, the remote DHCP server assigns the PC the address 192.168.1.102, gateway 192.168.1.1, and subnet mask 255.255.255.0, and if the LAN management port is (say) 192.168.0.240 (and no other appropriate IP address is available to the PC), then the PC will be unable to access the LAN management port of the wireless Ethernet (client) bridge. |
||
| + | |||
| + | :For the LAN management port be on the same subnet as the PC, you either need to have a wireless Ethernet (client) bridge smart enough to get that address from the remote DHCP server, be lucky enough to just have them match, or configure it manually to match. |
||
| + | :Is the LAN management port of the EnGenius 3220 bridge being assigned an IP address by the remote DHCP server, or is it assigned manually? |
||
| − | . |
||
| + | --[[User:JNavas|John Navas]] 17:29, 7 April 2007 (UTC) |
||
Revision as of 17:29, 7 April 2007
2 IP addresses
This is a great article. Can't you avoid the problem of needing 2 IP addresses for the onboard PC by installing an onboard AP/router like the Linksys WRT54G, and then connecting it's WAN port to the Bridge? This seems to work for me using an EnGenius 3220 bridge - or am I missing something? --John Howell 09:04, 7 April 2007
- Thank you.
- The problem of needing two IP addresses on the PC is due to:
- IP address assigned by DHCP for access to the Internet.
- IP address needed for management of a wireless Ethernet (client) bridge (e.g., EnGenius 3220) that won't necessarily be on the same subnet as IP #1. This could be avoided if the wireless Ethernet (client) bridge were smart enough to obtain its LAN management IP address from the remote DHCP server (and would thus be on the same subnet as the address assigned to the PC), but I don't know of any such devices that are smart enough to do that.
- If you're using the WRT54G as a:
- Router, then what you're doing is "double NAT", NAT #1 being the remote router and NAT #2 being your WRT54G, which will get a private IP address from the remote DHCP server, and assign its own private address to the PC. That usually works, but can cause Internet access problems, so I don't recommend it.
- Wireless access point (as suggested in this article, configured thusly), then the WRT54G needs no IP address (except for management) and the PC gets its IP address from the remote DHCP server.
- Either way you have the problem of how to access the LAN management port of the EnGenius 3220 bridge (e.g., to select the Wi-Fi network you wish to connect to). If in config #2, for example, the remote DHCP server assigns the PC the address 192.168.1.102, gateway 192.168.1.1, and subnet mask 255.255.255.0, and if the LAN management port is (say) 192.168.0.240 (and no other appropriate IP address is available to the PC), then the PC will be unable to access the LAN management port of the wireless Ethernet (client) bridge.
- For the LAN management port be on the same subnet as the PC, you either need to have a wireless Ethernet (client) bridge smart enough to get that address from the remote DHCP server, be lucky enough to just have them match, or configure it manually to match.
- Is the LAN management port of the EnGenius 3220 bridge being assigned an IP address by the remote DHCP server, or is it assigned manually?
--John Navas 17:29, 7 April 2007 (UTC)