I'm having a little trouble setting MiamiDx up to act as a
bridge between a LAN and another Amiga.
The situation is this: I have an Amiga 3000 with a Hydra ethernet
card in it running MiamiDx. I have a CD32 with the SX32Pro
expansion running Miami. The A3000 and the CD32Pro are linked
together with the AmigaLink floppy port networking hardware. The
A3000's ethernet card is connected to my company's LAN.
As we're a small company and I'm the network administrator
(grin), there are plenty of IP's available on our network such
that I don't need to run MiamiDx in IP-NAT mode; I want it to
simply "bridge" traffic between the two hardware interfaces.
One thing I'm especially confused about is whether the two
hardware interfaces in a situation like this should have the
*same* or *different* IP's. At the moment, the A3000 is set up
with the same IP (192.168.1.31) on both hardware interfaces, and
the CD32 is using 192.168.1.32 (I couldn't resist :).
I have gotten the setup to the point where both Amigas can ping
each other, and the A3000 can ping machines on the ethernet LAN,
but I can't ping the rest of the network from the CD32Pro. If it
helps, I got this far by reading the file included with MiamiDx
about setting up IP-NAT and making what I hoped were reasonable
changes given my purpose, and then just testing different
settings from there.
Hints, tips, examples, pointers to FAQs that I missed from
boneheadedness, etc. would all be greatly appreciated. This is
the first time I've tried to do anything like this, and it's
clear I have quite a bit to learn. (I'm only glad I'm learning it
with MiamiDx, instead of something hostile.)
George Madison
----
[> George Madison <*> [EMAIL PROTECTED] <*> Just say NO to razors! <]
[> It's a BEAR thing -- you wouldn't understand <*> Copyright 2000 <]
--
To unsubscribe send "unsubscribe miamidx-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
