Success!!!
I took out my servername and address in /etc/hosts and am now able to
connect to internet.
/sbin/ifup ppp0 dials modem and connects
/sbin/ifconfig shows eth0.,lo,ppp0 with IP addressess
on ppp0 it shows the address the ISP gives me upon connection.
What is command to disconnect? Kppp will also work.
On Boot though "http" fails and has to set the servername. Bootup takes
forever. I will now enable network on box2 and try to figure out how to
mount.
What do I do next?
Thanks Greg
Bob
----- Original Message -----
From: Greg Stewart <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 25, 2000 12:07 AM
Subject: Re: [newbie] Kppp and Networking
> > Internal eth0: 192.168.100.1/255.255.255.0
> > External ppp0: 192.168.100.1/255.255.255.255
>
> OK, something is definitely wrong with this...Have you correctly
configured
> ppp0 for DHCP? 'Cause the system is encountering an IP conflict now.
> 192.168.x.x is a reserved address (you may know this already) for internal
> LAN usage along with 10.x.x.x and , i believe, 172.something..x.x .You
> definitely need to check to make sure there is no IP assignment for ppp0,
> only DHCP. Also, check /etc/hosts to make sure you only 127.0.0.1
> localhost.localdomain as the entry...no other IPs until we can figure out
> why there's this new conflict.
>
> Um... yes, if you configure ppp0 to start at boot, it wiil attempt to dial
> up unless you have demand dial enabled...let's not get into that yet,
> though.
>
> Disable the boot-time on ppp0 for now. You should be able to leave
> pmfirewall the way you have it.
>
> After boot, type /sbin/ifup ppp0 and see what happens. I negotiation
> occurs, wait a few seconds and then type /sbinf/ifconfig and see if ppp0
is
> listed. if it is, check the IP info. If you get assigned a 192.168.x.x
> number then we have to use a different range on the NIC (10.x.x.x maybe).
>
> Geez...it's 1am--I have to get to sleep now... I'll think some more on
this
> tomorrow.
>
> --Greg
>
>
>
> > 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
> > >
> > >
> > >
> >
> >
> >
>
>
>
____________________________________________________________________________
__
> message envoye depuis http://www.ifrance.com
> emails (pop)-sites persos (espace illimite)-agenda-favoris
(bookmarks)-forums
> Ecoutez ce message par tel ! : 08 92 68 92 15 (france uniquement)
>
>
>
>
