On 2002-01-18 6:57 PM, "M. Tamer �zsu" <[EMAIL PROTECTED]> wrote:
> On 1/18/02 11:49 AM, "Alain Bornibus" <[EMAIL PROTECTED]> wrote: > >> On 1/17/02 6:05 PM, "M. Tamer �zsu" <[EMAIL PROTECTED]> wrote: ... >> >> Why would you have a router and Airport running on the same network? >> >> With Airport you only need a hub/switch to connect your hard wired computers >> > > Correct -- you can have the setup such that your DSL is connected to the > hub, to which is connected the Airport and the printer. This is fine if you > don't wish to have some firewall protection that the router provides and all > of your machines talk to the Airport. The latter is due to the fact that you > are either assigning the static IP you get from your ISP to the Airport, or, > if you are using DHCP, the Airport has the client id. In other words, to > your ISP, it should appear as if only one machine is connected to the > Internet. Or you can buy a second IP. I have some wired computers as well > that I connect to the router, which also acts as a DHCP server. Tamer, My configuration is similar. I have my DSL "router" connected to a PowerMac 9600 which runs IPNetRouter. (See http://www.sustworks.com .) The 9600 has a second Ethernet interface (NIC) which connects to my Ethernet hub. Some computers (e.g. A Windows NT box) are "hardwired" to the hub, as is an HP JetDirect print server. I have an Airport Base Station also wired to the Ethernet hub. The Airport is a DHCP server for the wireless portion of my LAN, and the IPNetRouter on the 9600 is a DHCP server for the wired portion of my LAN. Enjoy -- Jim -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
