Weellll... I'd personally argue that TCP/IP-based networking is still an
arcane-enough field that any NAT setup is sort of kludgy.
For example, a friend of mine just got a cable modem, a mini-hub, and one
DHCP IP address to share amongst a 7300 and 8500 (and now a new Pismo, which
he's invited me to play Quake with this weekend, heh-heh). So we have the
7300 running IPNetRouter, doing NAT for the others, all attached onto the
same hub. So we don't have a separation between the LAN and the Internet-
we're dependent on the cable modem not passing on packets from the
192.168.x.x range, but still passing on packets from the DHCP client.
Kludgy. A cleaner solution would be to use a dedicated NAT router sitting
between the LAN and the Internet as a gateway. This way, all traffic on the
local LAN isn't dependent on a quirk of the TCP/IP standard for protection
from outside interference- plus, setting up a firewall becomes a bit more
practical.
You're really right about flexibility not being a corporate strongpoint.
Having worked as tech support before, you're always caught between a rock
(instructions from management) and a hard place (the customer), so even if
you're remotely competent and know your stuff, it's still not always enough
to satisfy both at the same time.
But to the original poster of this thread- please keep in mind that you've
asked a difficult question, one which I hope you've gleaned enough
information to answer from my ramblings and others' practical comments. I
hope this link also helps:
http://www.macnn.com/contributions/airportrev.shtml
Good luck, and if problems arise, you know on which list we all reside!
-Nathan
>The problem is that Airport setup is sort of kludgy. First you set up
>a Mac and then xfer the connection info to the Airport base station.
>So you would have to inform the upstream of the Airport's MAC
>(ethernet hardware) address. I'd be willing to bet that the cable guy
>would freak at having to install/test at a desktop only to have it
>all move to a "console-less" device like the Airport base station....
>with a different MAC address.
>
>Not saying that it shouldn't or wouldn't work! Just that the
>install/service/whatever folks are not allowed to deviate from the
>"script" when installing service at customer locations. Flexibility
>is not a corporate strongpoint.
>
>--chuck
----------
Duo/2400 List, The friendliest place on the Net!
A listserv for users and fans of Mac subportables.
FAQ at <http://www.themacintoshguy.com/lists/DuoListFAQ.shtml>
Be sure to visit Mac2400! <http://www.sineware.com/mac2400>
X-Router | Share your DSL or cable modem between multiple computers!
Dr. Bott | <http://www.drbott.com/prod/MIH120.html>
PowerBook Guy is | Click here!
Everything PowerBook! | http://www.powerbookguy.com
Midwest Mac Parts ][ <http://www.midwestmac.com>
After-market parts for Macs. ][ 888-356-1104 ][
MacResQ Reader Specials: 2.5GB Seagate SCSI: $119, 4GB IBM SCSI: $199,
Norton Util. 4.0: $29, Mac Parts, Systems & Repairs <http://www.macresq.com>
