×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I presume that this is on an internal network already protected by a firewall.
It sounds to me like you really want an "access point" rather than a
router. The difference is that an access point is just a substitute
for a wire, whereas a "broadband router" typically does DHCP, network
address translation, and basic firewall functions. You probably do
NOT want that internally.
The Linksys WAP54G might be a better choice of hardware. You can also
probably set the WRT54GL to be an "access point" rather than a router,
but I do not know how. What I would probably do is plug a switch into
the existing ethernet line, plug the two workstations and the WAP54G
into the switch.
For wireless settings, you should turn on security; WPA is better than
WEP if you have it. Also, you should turn OFF the broadcasting of the
SSID. This will prevent your network from showing up on the Windows
wireless network screen of every computer passing by; you will have to
provide the SSID and access key to any computer that is to have
access. I would not worry about any port blocking internally.
On Nov 13, 2007 7:22 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:
Bob Anderson wrote:
It is a the far end of the plant with a Cisco switch and a
4-port hub between it and the Data Center
Ok, if it's hard wired, it's location doesn't really mater.
I would suggest that you give the wireless router it's own external IP
address, block outbound port 25, and just open it up.
david
midrange.com
