Very Computer

Arrrrrgh!

I have just received a new Indy. I have a very simple network, but I
can't get it to work. Here's the scenario:

I have an ISDN connection to my ISP. I am using the Indy as my T/A
(dialing out from it using PPP) It works fine. Using the Indy as a
workstation, I can reach Internet hosts without any problem.

I have the Indy connected to a small workgroup hub via the ec0
interface. Additionally, I have a Mac connected to the hub. My goal here
is to allow the Mac to access hosts on the Internet using the Indy as a
gateway.

I have a full range of 254 addresses from my ISP assigned to my domain,
and the Mac is set up correctly. All the basic stuff is correct.

When the Indy is connected to the ISP via a PPP connection, the local
network on ec0 (one Mac!) does not work. I can't ping the Mac from the
Indy or vice-versa. And the Indy runs REAL slow if both ec0 AND ppp0 are
active. It takes about two minutes (literally) to open a window from the
System Toolchest. As soon as I do a /etc/init.d/network off, the Indy
runs fine again. In other words, I can have ISDN or Ethernet, BUT NOT
BOTH.

When the PPP connection is NOT active, I can communicate just fine
between the Mac and the Indy.

**Has anyone set up an Indy to act as a gateway between an ISDN network
and an Ethernet network?** SGI is a great company, but I am in my third
day of waiting for a technician to return my calls.

Any help would be greatly appreciated, but I doubt it will help me grow
my hair back...

Jeff Phillips

J> I have an ISDN connection to my ISP. I am using the Indy as my T/A
J> (dialing out from it using PPP) It works fine. Using the Indy as a
J> workstation, I can reach Internet hosts without any problem.

J> I have the Indy connected to a small workgroup hub via the ec0
J> interface. Additionally, I have a Mac connected to the hub. My goal here
J> is to allow the Mac to access hosts on the Internet using the Indy as a
J> gateway.

J> I have a full range of 254 addresses from my ISP assigned to my domain,
J> and the Mac is set up correctly. All the basic stuff is correct.

J> When the Indy is connected to the ISP via a PPP connection, the local
J> network on ec0 (one Mac!) does not work. I can't ping the Mac from the
J> Indy or vice-versa. And the Indy runs REAL slow if both ec0 AND ppp0 are
J> active. It takes about two minutes (literally) to open a window from the
J> System Toolchest. As soon as I do a /etc/init.d/network off, the Indy
J> runs fine again. In other words, I can have ISDN or Ethernet, BUT NOT
J> BOTH.

J> When the PPP connection is NOT active, I can communicate just fine
J> between the Mac and the Indy.

Sounds like overlapping naming or routing or nameservice...

J> **Has anyone set up an Indy to act as a gateway between an ISDN network
J> and an Ethernet network?** SGI is a great company, but I am in my third
J> day of waiting for a technician to return my calls.

Not using PPP/ISDN, but I've helped a lot of people setup modem/PPP
networks.  Most things should be the same at the networking/routing
level.  See my Web pages:

        http://reality.sgi.com/scotth/dialup-support.html

--
---

 http://hoshi.corp.sgi.com/scotty.html / Garbage In -- Gospel out
  <a href="http://reality.sgi.com/employees/scotth/">home page</a>

 > **Has anyone set up an Indy to act as a gateway between an ISDN network
 > and an Ethernet network?** SGI is a great company, but I am in my third
 > day of waiting for a technician to return my calls.

(available at http://www-viz.tamu.edu/~sgi-faq/) list numerous
writeups on SLIP and PPP setup and troubleshooting.

--

http://web.mit.edu/pshuang/.plan;  PGP 1906684DD1537EC4 30876EACC18ADFC5
          Disclaimer: unless explicitly otherwise stated, my
          statements represent my personal viewpoints only.