Hi, its me again.
I tried different port and also different slots. It didn't help. By the way
where do you find system info on your serial ports? I can find about my PCI
devices.
I then went to net conf and then ppp/slip/plip/ and enabled ppp0 to start
at bootup. Also enabled pmfirewall to start at boot. When booting it gets to
ppp0 and starts dialing ---its says it failed and will retry. I noticed that
my modem is connected after trying to start KPPP. I then ran ./pmfirewall
restart and got the following results
Internal eth0: 192.168.100.1/255.255.255.0
External ppp0: 192.168.100.1/255.255.255.255
I can ping this mysterious 208.223.199.240 and my box successfully., but
nothing else.I haven't set up box 2 yet. I have to go to netconf to
disconnect modem. I played with "ip-up.local" some but will try some more.
Well, any ideas? is ppp0 suppose to start at boot without dialing out?
Thanks for all you help ,Greg.
Bob
----- Original Message -----
From: Greg Stewart <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 23, 2000 7:28 PM
Subject: Re: [newbie] Kppp and Networking
> I'm still thinking...but what's on /dev/ttyS0 (serial port 1)? Can you try
> moving the modem there?
>
> Also, have you tried removing the NIC and starting the machine to see if
all
> goes well? Did you try switching the PCI/ISA slot in which you have the
NIC?
>
> It's very strange that you have to take one device down to get the other
to
> intialise...It reeks of an IRQ conflict, but the two devices are defintely
> not sharing the same IRQ. Is there anything else on IRQ 3?
>
> I haven't used an external modem at all so I'm not familiar with how the
> system recognises it, nor how it's driven. But I can't figure it's that
> difficult to get going. Is the modem brought up at boot? If so, maybe
change
> that. pmfirewall should have no trouble seeing the modem when it does come
> up, even if pmfirewall is in the boot script--yeah, you'll get messages up
> arse in /var/log/messages, but you can ignore that if you don't mind a
large
> log file. I'm assuming you shutdown daily?
>
> For the "usepeerdns", of which I'm unsure, you can add a file in /etc/ppp
> called ip-up.local if you simply open it in vi. su to root first, vi
> ip-up.local, and andd whatever lines were suggested tou you. save the file
> and exit.
> Then do chmod +x ip-up.local. The ip-up script already has a line in it
> (well, it should) to call ip-up.local. This is for user configuration, as
> they suggest we leave our hands off ip-up.
>
> All I can think of right now, is that if you haven't areadly physically
> changed the position of the hardware (move the NIC to another slot, and
> change serial ports for the modem), then do so. Try booting with one out,
> then the other out, and see what happens. If you can do this, and give me
as
> much detail as possible about the resultsm and any log entries, that might
> help think.
>
> Sorry I don't have more for you to work with right now.
>
> --Greg
>
>
>
