Very Computer

I am very puzzled by some behavior I've noticed here regarding IP
masquerading and ISDN connections.

I have a local network at home which consists of four machines, three of
which are running Windows and one of which is running Linux 1.99.3.  The
Linux box (mental) acts as a gateway to the outside world either through
a 28.8K modem or via an ISDN link using a BitSurfr PRO.  The other
machines are able to access the outside world because mental is running
IP masquerading.

I have been using this setup with the modem for a month or so with no
problems.  I just switched to ISDN last week.

What I'm seeing is that when mental is connected via ISDN then
connections from the other machines to the rest of the internet are
*extremely* slow.  ftp takes five minutes to login where it took seconds
when mental was connected via the 28.8K modem.

If I cancel the ISDN connection and reinsitute a modem connection then
everything works wonderfully.

Can anyone give me a clue here as to what is going on here?  Obviously
I expected that the connection would be faster with ISDN.
--

Boston Business Computing  \\ VMS=>UNIX Solutions //       the real can be."

${SETSERIAL} -bg ${PORTS}

What happens is this, you uncomment and modify the entry for your ISDN
modem that is making use of a comm port, but the line above craps it
out and you end up with garbage, comment this puppy out and try this
setting in your entry for the ISDN modem

${SETSERIAL} /dev/cua0 ${AUTO_IRQ} skip_test autoconfig 16550A spd-vhi

For this longest time I could not understand why I was getting so many
packet errors, and in desperation, I looked at my file (DOH!)

I'm not getting much packet loss at all with the machine that is directly
connected via PPP.  It is only the masqueraded systems that are suffering.
--

Boston Business Computing  \\ VMS=>UNIX Solutions //       the real can be."