I was able to connect to the Internet in a simple manner using wvdial, but
then suddenly, about one month ago, it stopped working. I don't know why.
When I use the same ISP in Windows, it works perfectly. I'm using Mandrake
9.1 and a Conexant Winmodem.

"Eirik" <hannibalkannibal@yahoo.no> wrote in message
news:WsVzb.3840$Y06.66157@news4.e.nsc.no

> I was able to connect to the Internet in a simple manner using
> wvdial, but then suddenly, about one month ago, it stopped working. I
> don't know why.

What does "stopped working" mean?

    grep pppd /var/log/messages

and see what's logged. If you need help then post the lines that belong to a
single dialup attempt..

People can't read your mind, you know.


        tony


--
use hotmail for any email replies



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 100,000 Newsgroups - 19 Different Servers! =-----

On Fri, 5 Dec 2003 07:19:47 +0100,  "Eirik" <hannibalkannibal@yahoo.no> wrote:

> I'm using Mandrake
> 9.1 and a Conexant Winmodem.

'... "which" environment? kde/gnome/etc
..
-- 
///    Michael J. Tobler: motorcyclist, surfer, skydiver,    \\\ 
\\\ and author: "Inside Linux", "C++ HowTo", "C++ Unleashed" ///
If you make people think they're thinking, they'll love you; 
but if you really make them think they'll hate you.

> > I was able to connect to the Internet in a simple manner using
> > wvdial, but then suddenly, about one month ago, it stopped working. I
> > don't know why.
>
> What does "stopped working" mean?
>
>     grep pppd /var/log/messages

Dec  5 15:31:23 burk pppd[2013]: pppd 2.4.1 started by root, uid 0
Dec  5 15:31:23 burk pppd[2013]: Using interface ppp0
Dec  5 15:31:23 burk pppd[2013]: Connect: ppp0 <--> /dev/ttySHSF0
Dec  5 15:31:27 burk pppd[2013]: not replacing existing default route to
eth0 [192.168.0.2]
Dec  5 15:31:27 burk pppd[2013]: local  IP address 195.159.176.160
Dec  5 15:31:27 burk pppd[2013]: remote IP address 195.159.0.30
Dec  5 15:31:27 burk pppd[2013]: primary   DNS address 195.159.0.100
Dec  5 15:31:27 burk pppd[2013]: secondary DNS address 195.159.0.200
Dec  5 15:33:08 burk pppd[2013]: Terminating on signal 15.
Dec  5 15:33:08 burk pppd[2013]: Connection terminated.
Dec  5 15:33:08 burk pppd[2013]: Connect time 1.8 minutes.
Dec  5 15:33:08 burk pppd[2013]: Sent 110 bytes, received 104 bytes.
Dec  5 15:33:08 burk pppd[2013]: Exit.

>
> and see what's logged. If you need help then post the lines that belong to
a
> single dialup attempt..
>
> People can't read your mind, you know.
>
>
>         tony
>
>
> --
> use hotmail for any email replies
>
>
>
> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> -----==  Over 100,000 Newsgroups - 19 Different Servers! =-----

"Eirik" <hannibalkannibal@yahoo.no> wrote in message
news:IS0Ab.3990$Y06.67582@news4.e.nsc.no

> Dec  5 15:31:23 burk pppd[2013]: Connect: ppp0 <--> /dev/ttySHSF0
> Dec  5 15:31:27 burk pppd[2013]: not replacing existing default route
> to eth0 [192.168.0.2]

What does that mean to you, given your network topology? Is the machine
already connected to a network that has Internet access, and a default route
has already been declared? Does it have multiple modems, one of which is
already connected?

It may be helpful to examine "route -n" output in light of the other info
from your grep.


        tony


--
use hotmail for any email replies



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 100,000 Newsgroups - 19 Different Servers! =-----

"ynotssor" <"ynotssor"> skrev i melding
news:3fd194a9$1_5@corp.newsgroups.com...
> "Eirik" <hannibalkannibal@yahoo.no> wrote in message
> news:IS0Ab.3990$Y06.67582@news4.e.nsc.no
>
> > Dec  5 15:31:23 burk pppd[2013]: Connect: ppp0 <--> /dev/ttySHSF0
> > Dec  5 15:31:27 burk pppd[2013]: not replacing existing default route
> > to eth0 [192.168.0.2]
>
> What does that mean to you, given your network topology? Is the machine
> already connected to a network that has Internet access, and a default
route
> has already been declared? Does it have multiple modems, one of which is
> already connected?

192.168.0.2 is my computer, and the other one, 192.168.0.1 is a 486(see the
thread "486 and Linux"). 192.168.0.2 is the only computer with a connection
to the Internet.
>
> It may be helpful to examine "route -n" output in light of the other info
> from your grep.
>
>
>         tony
>
>
> --
> use hotmail for any email replies
>
>
>
> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> -----==  Over 100,000 Newsgroups - 19 Different Servers! =-----

On Sat, 06 Dec 2003 12:12:02 +0100, Eirik without thinking wrote:

> "ynotssor" <"ynotssor"> skrev i melding
> news:3fd194a9$1_5@corp.newsgroups.com...
>> "Eirik" <hannibalkannibal@yahoo.no> wrote in message
>> news:IS0Ab.3990$Y06.67582@news4.e.nsc.no
>>
>> > Dec  5 15:31:23 burk pppd[2013]: Connect: ppp0 <--> /dev/ttySHSF0 Dec 
>> > 5 15:31:27 burk pppd[2013]: not replacing existing default route to
>> > eth0 [192.168.0.2]
>>
>> What does that mean to you, given your network topology? Is the machine
>> already connected to a network that has Internet access, and a default
> route
>> has already been declared? Does it have multiple modems, one of which is
>> already connected?
> 
> 192.168.0.2 is my computer, and the other one, 192.168.0.1 is a 486(see
> the thread "486 and Linux"). 192.168.0.2 is the only computer with a
> connection to the Internet.
>>
>> It may be helpful to examine "route -n" output in light of the other
>> info from your grep.
>>
>>

Neither this post or the "486 and Linux" posts make sense to me.  Did you
get the 486 running with RH4.1?  Now you are trying to make the 486
connect through the 192.168.0.2 machine's dial-up networking?  Is the
question that your 0.2 machine is connected to cable/DSL and you can't
make it connect to the internet?  Whatcha trying to do? 

>>         tony
>>
>>
>> --
>> use hotmail for any email replies
>>
>>
>>
>> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
>> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
>> -----==  Over 100,000 Newsgroups - 19 Different Servers! =-----

"Noi" <noi@siam.com> skrev i melding
news:pan.2003.12.06.16.53.06.344240@siam.com...
> On Sat, 06 Dec 2003 12:12:02 +0100, Eirik without thinking wrote:
>
> > "ynotssor" <"ynotssor"> skrev i melding
> > news:3fd194a9$1_5@corp.newsgroups.com...
> >> "Eirik" <hannibalkannibal@yahoo.no> wrote in message
> >> news:IS0Ab.3990$Y06.67582@news4.e.nsc.no
> >>
> >> > Dec  5 15:31:23 burk pppd[2013]: Connect: ppp0 <--> /dev/ttySHSF0 Dec
> >> > 5 15:31:27 burk pppd[2013]: not replacing existing default route to
> >> > eth0 [192.168.0.2]
> >>
> >> What does that mean to you, given your network topology? Is the machine
> >> already connected to a network that has Internet access, and a default
> > route
> >> has already been declared? Does it have multiple modems, one of which
is
> >> already connected?
> >
> > 192.168.0.2 is my computer, and the other one, 192.168.0.1 is a 486(see
> > the thread "486 and Linux"). 192.168.0.2 is the only computer with a
> > connection to the Internet.
> >>
> >> It may be helpful to examine "route -n" output in light of the other
> >> info from your grep.
> >>
> >>
>
> Neither this post or the "486 and Linux" posts make sense to me.  Did you
> get the 486 running with RH4.1?  Now you are trying to make the 486
> connect through the 192.168.0.2 machine's dial-up networking?  Is the
> question that your 0.2 machine is connected to cable/DSL and you can't
> make it connect to the internet?  Whatcha trying to do?

I was using the 0.2-machine to surf the Internet and other regular things,
the one day, it just wouldn't work any more. Now I want to get it to work
again, I don't like using Windows. The 486 is getting dusty in another
corner of my room, and is unimportant.
> >>
> >>
> >> --
> >> use hotmail for any email replies
> >>
> >>
> >>
> >> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
> >> http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
> >> -----==  Over 100,000 Newsgroups - 19 Different Servers! =-----
>

On Fri, 05 Dec 2003 15:45:18 +0100, Eirik wrote:

> 
>> > I was able to connect to the Internet in a simple manner using wvdial, but
>> > then suddenly, about one month ago, it stopped working. I don't know why.
>>
>> What does "stopped working" mean?
>>
>>     grep pppd /var/log/messages
> 
> Dec  5 15:31:23 burk pppd[2013]: pppd 2.4.1 started by root, uid 0 Dec  5
> 15:31:23 burk pppd[2013]: Using interface ppp0 Dec  5 15:31:23 burk pppd[2013]:
> Connect: ppp0 <--> /dev/ttySHSF0 Dec  5 15:31:27 burk pppd[2013]: not replacing
> existing default route to eth0 [192.168.0.2]
> Dec  5 15:31:27 burk pppd[2013]: local  IP address 195.159.176.160 Dec  5
> 15:31:27 burk pppd[2013]: remote IP address 195.159.0.30 Dec  5 15:31:27 burk
> pppd[2013]: primary   DNS address 195.159.0.100 Dec  5 15:31:27 burk pppd[2013]:
> secondary DNS address 195.159.0.200 Dec  5 15:33:08 burk pppd[2013]: Terminating
> on signal 15. Dec  5 15:33:08 burk pppd[2013]: Connection terminated. Dec  5
> 15:33:08 burk pppd[2013]: Connect time 1.8 minutes. Dec  5 15:33:08 burk
> pppd[2013]: Sent 110 bytes, received 104 bytes. Dec  5 15:33:08 burk pppd[2013]:
> Exit.
> 
> 

Hmmmm....I'd say the reference to eth0 is a red herring - it's saying it's
running ppp0 IN ADDITION TO, rather than INSTEAD OF, eth0 (which is probably
what you want). Only problem might be how you've set up your default route.

Seems like it established a ppp connection for 1,8 minutes (what is "signal
15"?). If you're not getting "out", try this:

1. Dial out, and check ifconfig for a ppp0 entry. Once it's there, try to ping
the "other" side of the connection (in the above case, 195.159.0.30). If that
works, you have a connection: check your routing (route -n) and DNS.

2. you could try "ifconfig eth0 down" to remove eth0 for the "equation" - this
will drop out any routing you've set up with eth0 that may be conflicting with
the routing to ppp0.

3. Check ifconfig regularly to see if ppp0 is staying up, or dropping out.

Lloyd

"Eirik" <hannibalkannibal@yahoo.no> wrote in message
news:LQiAb.4151$Y06.69598@news4.e.nsc.no

> 192.168.0.2 is my computer, and the other one, 192.168.0.1 is a
> 486(see the thread "486 and Linux"). 192.168.0.2 is the only computer
> with a connection to the Internet.
>>
>> It may be helpful to examine "route -n" output in light of the other
>> info from your grep.

If you won't provide route -n output then it seems you are unwilling to be
helped.

--
use hotmail for any email replies



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 100,000 Newsgroups - 19 Different Servers! =-----

> >>     grep pppd /var/log/messages
> >
> > Dec  5 15:31:23 burk pppd[2013]: pppd 2.4.1 started by root, uid 0 Dec
5
> > 15:31:23 burk pppd[2013]: Using interface ppp0 Dec  5 15:31:23 burk
pppd[2013]:
> > Connect: ppp0 <--> /dev/ttySHSF0 Dec  5 15:31:27 burk pppd[2013]: not
replacing
> > existing default route to eth0 [192.168.0.2]
> > Dec  5 15:31:27 burk pppd[2013]: local  IP address 195.159.176.160 Dec
5
> > 15:31:27 burk pppd[2013]: remote IP address 195.159.0.30 Dec  5 15:31:27
burk
> > pppd[2013]: primary   DNS address 195.159.0.100 Dec  5 15:31:27 burk
pppd[2013]:
> > secondary DNS address 195.159.0.200 Dec  5 15:33:08 burk pppd[2013]:
Terminating
> > on signal 15. Dec  5 15:33:08 burk pppd[2013]: Connection terminated.
Dec  5
> > 15:33:08 burk pppd[2013]: Connect time 1.8 minutes. Dec  5 15:33:08 burk
> > pppd[2013]: Sent 110 bytes, received 104 bytes. Dec  5 15:33:08 burk
pppd[2013]:
> > Exit.
> >
> >
>
> Hmmmm....I'd say the reference to eth0 is a red herring - it's saying it's
> running ppp0 IN ADDITION TO, rather than INSTEAD OF, eth0 (which is
probably
> what you want). Only problem might be how you've set up your default
route.
>
> Seems like it established a ppp connection for 1,8 minutes (what is
"signal
> 15"?).
EWS> Signal 15 is when the application is terminated by the user, ^C.

 If you're not getting "out", try this:
>
> 1. Dial out, and check ifconfig for a ppp0 entry. Once it's there, try to
ping
> the "other" side of the connection (in the above case, 195.159.0.30). If
that
> works, you have a connection: check your routing (route -n) and DNS.
EWS> The ping worked fine, and I did a route -n afterwards:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0        0 eth0

>
> 2. you could try "ifconfig eth0 down" to remove eth0 for the "equation" -
this
> will drop out any routing you've set up with eth0 that may be conflicting
with
> the routing to ppp0.
EWS> I did this, and this is what the routing table looked like after that:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0        0 ppp0

>
> 3. Check ifconfig regularly to see if ppp0 is staying up, or dropping out.
EWS> The ppp0-connection didn't drop out until I killed wvdial.
> Lloyd
Thanks for all attempts to help me, I appreciate it!
>

On Sun, 07 Dec 2003 15:53:43 +0100, Eirik wrote:

> EWS> The ping worked fine, and I did a route -n afterwards:
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0        0 eth0
> 
> 
>> 2. you could try "ifconfig eth0 down" to remove eth0 for the "equation" -
> this
>> will drop out any routing you've set up with eth0 that may be conflicting
> with
>> the routing to ppp0.
> EWS> I did this, and this is what the routing table looked like after that:
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0        0 ppp0
> 
> 
> 
Well, there's yer problem, b'y!

The eth0 config is setting up a default route (192.168.0.2). I'm guessing when
you shut down eth0, your Internet connection worked fine. That's one workaround:
just shut down eth0 when you want to use the Internet connection. The other is
find where the default route is set for eth0 and remove it (unless 192.168.0.2
is a gateway/router, it's not correct anyway).

In general, you need 3 things for an Internet connection: a path, a default
route, and a DNS. You check the first by pinging the ISP. You check the second
by pinging a NUMBERED host (like the DNS), or checking the routing tables. You
check the third by pinging the DNS or pinging a known site (such as
www.yahoo.com)

Lloyd
MR FISH
MR NOT FISH
MR TOO FISH: CDBDI'S?
WHALE OIL BEEF HOOKED! MR FISH!

"Lloyd Sumpter" <lsumpter@dccnet.com> skrev i melding
news:vt6t1e9ftnji8f@corp.supernews.com...
> On Sun, 07 Dec 2003 15:53:43 +0100, Eirik wrote:
>
> > EWS> The ping worked fine, and I did a route -n afterwards:
> >
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
> > 195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0        0
ppp0
> > 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0
eth0
> > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0
lo
> > 0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0        0
eth0
> >
> >
> >> 2. you could try "ifconfig eth0 down" to remove eth0 for the
"equation" -
> > this
> >> will drop out any routing you've set up with eth0 that may be
conflicting
> > with
> >> the routing to ppp0.
> > EWS> I did this, and this is what the routing table looked like after
that:
> >
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
> > 195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0        0
ppp0
> > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0
lo
> > 0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0        0
ppp0
> >
> >
> >
> Well, there's yer problem, b'y!
>
> The eth0 config is setting up a default route (192.168.0.2). I'm guessing
when
> you shut down eth0, your Internet connection worked fine. That's one
workaround:
> just shut down eth0 when you want to use the Internet connection.
EWS> I don't think it worked when I tried it.
The other is
> find where the default route is set for eth0 and remove it (unless
192.168.0.2
> is a gateway/router, it's not correct anyway).
>
> In general, you need 3 things for an Internet connection: a path, a
default
> route, and a DNS. You check the first by pinging the ISP. You check the
second
> by pinging a NUMBERED host (like the DNS), or checking the routing tables.
You
> check the third by pinging the DNS or pinging a known site (such as
> www.yahoo.com)
>
> Lloyd
> MR FISH
> MR NOT FISH
> MR TOO FISH: CDBDI'S?
> WHALE OIL BEEF HOOKED! MR FISH!

> > > EWS> The ping worked fine, and I did a route -n afterwards:
> > >
> > > Kernel IP routing table
> > > Destination     Gateway         Genmask         Flags Metric Ref
Use
> Iface
> > > 195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0
0
> ppp0
> > > 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
0
> eth0
> > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
0
> lo
> > > 0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0
0
> eth0
> > >
> > >
> > >> 2. you could try "ifconfig eth0 down" to remove eth0 for the
> "equation" -
> > > this
> > >> will drop out any routing you've set up with eth0 that may be
> conflicting
> > > with
> > >> the routing to ppp0.
> > > EWS> I did this, and this is what the routing table looked like after
> that:
> > >
> > > Kernel IP routing table
> > > Destination     Gateway         Genmask         Flags Metric Ref
Use
> Iface
> > > 195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0
0
> ppp0
> > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
0
> lo
> > > 0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0
0
> ppp0
> > >
> > >
> > >
> > Well, there's yer problem, b'y!
> >
> > The eth0 config is setting up a default route (192.168.0.2). I'm
guessing
> when
> > you shut down eth0, your Internet connection worked fine. That's one
> workaround:
> > just shut down eth0 when you want to use the Internet connection.
> EWS> I don't think it worked when I tried it.
> The other is
> > find where the default route is set for eth0 and remove it (unless
> 192.168.0.2
> > is a gateway/router, it's not correct anyway).
> >
> > In general, you need 3 things for an Internet connection: a path, a
> default
> > route, and a DNS. You check the first by pinging the ISP. You check the
> second
> > by pinging a NUMBERED host (like the DNS), or checking the routing
tables.
> You
> > check the third by pinging the DNS or pinging a known site (such as
> > www.yahoo.com)

I can ping the computer on the other side, but I can't do anything else,
even if I shut down the network. Also, I know that it has worked fine
before, I sat at the old 486 and ssh'd with a computer on the Internet, so
that can't be the reason.

IT STILL ISN'T WORKING, SOMEONE PLEASE HELP ME!!! I need to use Linux, I
hate having to use Windows whenever I want to surf the Web or check my
email!

"Eirik" <hannibalkannibal@yahoo.no> skrev i melding
news:c%dBb.4428$n31.77215@news2.e.nsc.no...
>
> > > > EWS> The ping worked fine, and I did a route -n afterwards:
> > > >
> > > > Kernel IP routing table
> > > > Destination     Gateway         Genmask         Flags Metric Ref
> Use
> > Iface
> > > > 195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0
> 0
> > ppp0
> > > > 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
> 0
> > eth0
> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
> 0
> > lo
> > > > 0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0
> 0
> > eth0
> > > >
> > > >
> > > >> 2. you could try "ifconfig eth0 down" to remove eth0 for the
> > "equation" -
> > > > this
> > > >> will drop out any routing you've set up with eth0 that may be
> > conflicting
> > > > with
> > > >> the routing to ppp0.
> > > > EWS> I did this, and this is what the routing table looked like
after
> > that:
> > > >
> > > > Kernel IP routing table
> > > > Destination     Gateway         Genmask         Flags Metric Ref
> Use
> > Iface
> > > > 195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0
> 0
> > ppp0
> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
> 0
> > lo
> > > > 0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0
> 0
> > ppp0
> > > >
> > > >
> > > >
> > > Well, there's yer problem, b'y!
> > >
> > > The eth0 config is setting up a default route (192.168.0.2). I'm
> guessing
> > when
> > > you shut down eth0, your Internet connection worked fine. That's one
> > workaround:
> > > just shut down eth0 when you want to use the Internet connection.
> > EWS> I don't think it worked when I tried it.
> > The other is
> > > find where the default route is set for eth0 and remove it (unless
> > 192.168.0.2
> > > is a gateway/router, it's not correct anyway).
> > >
> > > In general, you need 3 things for an Internet connection: a path, a
> > default
> > > route, and a DNS. You check the first by pinging the ISP. You check
the
> > second
> > > by pinging a NUMBERED host (like the DNS), or checking the routing
> tables.
> > You
> > > check the third by pinging the DNS or pinging a known site (such as
> > > www.yahoo.com)
>
> I can ping the computer on the other side, but I can't do anything else,
> even if I shut down the network. Also, I know that it has worked fine
> before, I sat at the old 486 and ssh'd with a computer on the Internet, so
> that can't be the reason.
>
>

On Wed, 10 Dec 2003 21:05:42 +0100, Eirik wrote:

> IT STILL ISN'T WORKING, SOMEONE PLEASE HELP ME!!! I need to use Linux, I
> hate having to use Windows whenever I want to surf the Web or check my
> email!
> 

Eirik, try 'route add default gw 195.159.0.32' (or whatever here)

On Wed, 10 Dec 2003 21:05:42 +0100, Eirik without thinking wrote:

> IT STILL ISN'T WORKING, SOMEONE PLEASE HELP ME!!! I need to use Linux, I
> hate having to use Windows whenever I want to surf the Web or check my
> email!
> 

I missed your previous posts but looking at the route below I'll guess:
You're using a dialup modem (195.159) to connect as in ppp0 then try
adding the default route.  sudo route add default dev ppp0

If you've done that and you can ping www.redhat.com or www.yahoo.com
then your connection is working then something else prevents your internet
connection like iptables.  So if you can ping yahoo then post output
sanitized output from sudo iptables -L.  

Check for errors with "less /var/log/secure" and "less /var/log/messages".

> "Eirik" <hannibalkannibal@yahoo.no> skrev i melding
> news:c%dBb.4428$n31.77215@news2.e.nsc.no...
>>
>> > > > EWS> The ping worked fine, and I did a route -n afterwards:
>> > > >
>> > > > Kernel IP routing table
>> > > > Destination     Gateway         Genmask         Flags Metric Ref
>> Use
>> > Iface
>> > > > 195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0
>> 0
>> > ppp0
>> > > > 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
>> 0
>> > eth0
>> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
>> 0
>> > lo
>> > > > 0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0
>> 0
>> > eth0
>> > > >
>> > > >
>> > > >> 2. you could try "ifconfig eth0 down" to remove eth0 for the
>> > "equation" -
>> > > > this
>> > > >> will drop out any routing you've set up with eth0 that may be
>> > conflicting
>> > > > with
>> > > >> the routing to ppp0.
>> > > > EWS> I did this, and this is what the routing table looked like
> after
>> > that:
>> > > >
>> > > > Kernel IP routing table
>> > > > Destination     Gateway         Genmask         Flags Metric Ref
>> Use
>> > Iface
>> > > > 195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0
>> 0
>> > ppp0
>> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
>> 0
>> > lo
>> > > > 0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0
>> 0
>> > ppp0
>> > > >
>> > > >
>> > > >
>> > > Well, there's yer problem, b'y!
>> > >
>> > > The eth0 config is setting up a default route (192.168.0.2). I'm
>> guessing
>> > when
>> > > you shut down eth0, your Internet connection worked fine. That's one
>> > workaround:
>> > > just shut down eth0 when you want to use the Internet connection.
>> > EWS> I don't think it worked when I tried it. The other is
>> > > find where the default route is set for eth0 and remove it (unless
>> > 192.168.0.2
>> > > is a gateway/router, it's not correct anyway).
>> > >
>> > > In general, you need 3 things for an Internet connection: a path, a
>> > default
>> > > route, and a DNS. You check the first by pinging the ISP. You check
> the
>> > second
>> > > by pinging a NUMBERED host (like the DNS), or checking the routing
>> tables.
>> > You
>> > > check the third by pinging the DNS or pinging a known site (such as
>> > > www.yahoo.com)
>>
>> I can ping the computer on the other side, but I can't do anything else,
>> even if I shut down the network. Also, I know that it has worked fine
>> before, I sat at the old 486 and ssh'd with a computer on the Internet,
>> so that can't be the reason.
>>
>>
>>

I missed your previous posts but looking at the route below I'll guess:
> You're using a dialup modem (195.159) to connect as in ppp0 then try
> adding the default route.  sudo route add default dev ppp0
>
> If you've done that and you can ping www.redhat.com or www.yahoo.com
> then your connection is working then something else prevents your internet
> connection like iptables.  So if you can ping yahoo then post output
> sanitized output from sudo iptables -L.

It doesn't work.

> Check for errors with "less /var/log/secure" and "less /var/log/messages".

The part of /var/log/messages concerning this:

Dec 11 20:26:24 burk pppd[2383]: pppd 2.4.1 started by root, uid 0
Dec 11 20:26:24 burk pppd[2383]: Using interface ppp0
Dec 11 20:26:24 burk pppd[2383]: Connect: ppp0 <--> /dev/ttySHSF0
Dec 11 20:26:28 burk pppd[2383]: not replacing existing default route to
eth0 [192.168.0.2]
Dec 11 20:26:28 burk pppd[2383]: local  IP address 195.159.184.241
Dec 11 20:26:28 burk pppd[2383]: remote IP address 195.159.0.34
Dec 11 20:26:28 burk pppd[2383]: primary   DNS address 195.159.0.100
Dec 11 20:26:28 burk pppd[2383]: secondary DNS address 195.159.0.200
Dec 11 20:32:23 burk pppd[2383]: Terminating on signal 15.
Dec 11 20:32:23 burk pppd[2383]: Connection terminated.
Dec 11 20:32:23 burk pppd[2383]: Connect time 6.0 minutes.
Dec 11 20:32:23 burk pppd[2383]: Sent 362 bytes, received 248 bytes.
Dec 11 20:32:23 burk pppd[2383]: Exit.

I hope this can help.

>
> > "Eirik" <hannibalkannibal@yahoo.no> skrev i melding
> > news:c%dBb.4428$n31.77215@news2.e.nsc.no...
> >>
> >> > > > EWS> The ping worked fine, and I did a route -n afterwards:
> >> > > >
> >> > > > Kernel IP routing table
> >> > > > Destination     Gateway         Genmask         Flags Metric Ref
> >> Use
> >> > Iface
> >> > > > 195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0
> >> 0
> >> > ppp0
> >> > > > 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
> >> 0
> >> > eth0
> >> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
> >> 0
> >> > lo
> >> > > > 0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0
> >> 0
> >> > eth0
> >> > > >
> >> > > >
> >> > > >> 2. you could try "ifconfig eth0 down" to remove eth0 for the
> >> > "equation" -
> >> > > > this
> >> > > >> will drop out any routing you've set up with eth0 that may be
> >> > conflicting
> >> > > > with
> >> > > >> the routing to ppp0.
> >> > > > EWS> I did this, and this is what the routing table looked like
> > after
> >> > that:
> >> > > >
> >> > > > Kernel IP routing table
> >> > > > Destination     Gateway         Genmask         Flags Metric Ref
> >> Use
> >> > Iface
> >> > > > 195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0
> >> 0
> >> > ppp0
> >> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
> >> 0
> >> > lo
> >> > > > 0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0
> >> 0
> >> > ppp0
> >> > > >
> >> > > >
> >> > > >
> >> > > Well, there's yer problem, b'y!
> >> > >
> >> > > The eth0 config is setting up a default route (192.168.0.2). I'm
> >> guessing
> >> > when
> >> > > you shut down eth0, your Internet connection worked fine. That's
one
> >> > workaround:
> >> > > just shut down eth0 when you want to use the Internet connection.
> >> > EWS> I don't think it worked when I tried it. The other is
> >> > > find where the default route is set for eth0 and remove it (unless
> >> > 192.168.0.2
> >> > > is a gateway/router, it's not correct anyway).
> >> > >
> >> > > In general, you need 3 things for an Internet connection: a path, a
> >> > default
> >> > > route, and a DNS. You check the first by pinging the ISP. You check
> > the
> >> > second
> >> > > by pinging a NUMBERED host (like the DNS), or checking the routing
> >> tables.
> >> > You
> >> > > check the third by pinging the DNS or pinging a known site (such as
> >> > > www.yahoo.com)
> >>
> >> I can ping the computer on the other side, but I can't do anything
else,
> >> even if I shut down the network. Also, I know that it has worked fine
> >> before, I sat at the old 486 and ssh'd with a computer on the Internet,
> >> so that can't be the reason.
> >>
> >>
> >>
>

On Thu, 11 Dec 2003 20:48:18 +0100, Eirik without thinking wrote:

> I missed your previous posts but looking at the route below I'll guess:
>> You're using a dialup modem (195.159) to connect as in ppp0 then try
>> adding the default route.  sudo route add default dev ppp0
>>
>> If you've done that and you can ping www.redhat.com or www.yahoo.com
>> then your connection is working then something else prevents your
>> internet connection like iptables.  So if you can ping yahoo then post
>> output sanitized output from sudo iptables -L.
> 
> It doesn't work.

Sorry pls try again
$ sudo route del default 192.168.0.2
$ sudo route del 0.0.0.0 192.168.0.2 
$ sudo route add default dev ppp0  # execute after deletes

Also your sudo iptables -L
should have a line like:

Chain RH-Firewall-50-INPUT (2 references)
ACCEPT  all  --  anywhere anywhere  state RELATED,ESTABLISHED


post 
> 
>> Check for errors with "less /var/log/secure" and "less
>> /var/log/messages".
> 
> The part of /var/log/messages concerning this:
> 
Dec 11 20:26:24 burk pppd[2383]: pppd 2.4.1 started by root, uid 0 
Dec 11 20:26:24 burk pppd[2383]: Using interface ppp0 
Dec 11 20:26:24 burk pppd[2383]: Connect: ppp0 <--> /dev/ttySHSF0 
Dec 11 20:26:28 burk pppd[2383]: not replacing existing default route to
eth0 [192.168.0.2] 
Dec 11 20:26:28 burk pppd[2383]: local  IP address 195.159.184.241 
Dec 11 20:26:28 burk pppd[2383]: remote IP address 195.159.0.34 
Dec 11 20:26:28 burk pppd[2383]: primary   DNS address 195.159.0.100 
Dec 11 20:26:28 burk pppd[2383]: secondary DNS address 195.159.0.200 
Dec 11 20:32:23 burk pppd[2383]: Terminating on signal 15. 
Dec 11 20:32:23 burk pppd[2383]: Connection terminated. 
Dec 11 20:32:23 burk pppd[2383]: Connect time 6.0 minutes. 
Dec 11 20:32:23 burk pppd[2383]: Sent 362 bytes, received 248 bytes. 
Dec 11 20:32:23 burk pppd[2383]: Exit.
> 
> I hope this can help.
> 
> 
>> > "Eirik" <hannibalkannibal@yahoo.no> skrev i melding
>> > news:c%dBb.4428$n31.77215@news2.e.nsc.no...
>> >>
>> >> > > > EWS> The ping worked fine, and I did a route -n afterwards:
>> >> > > >
>> >> > > > Kernel IP routing table
>> >> > > > Destination     Gateway         Genmask         Flags Metric
>> >> > > > Ref
>> >> Use
>> >> > Iface
>> >> > > > 195.159.0.32    0.0.0.0         255.255.255.255 UH    0      0
>> >> 0
>> >> > ppp0
>> >> > > > 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0
>> >> 0
>> >> > eth0
>> >> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
>> >> 0
>> >> > lo
>> >> > > > 0.0.0.0         192.168.0.2     0.0.0.0         UG    0      0
>> >> 0
>> >> > eth0
>> >> > > >
>> >> > > >
>> >> > > >> 2. you could try "ifconfig eth0 down" to remove eth0 for the
>> >> > "equation" -
>> >> > > > this
>> >> > > >> will drop out any routing you've set up with eth0 that may be
>> >> > conflicting
>> >> > > > with
>> >> > > >> the routing to ppp0.
>> >> > > > EWS> I did this, and this is what the routing table looked
>> >> > > > like
>> > after
>> >> > that:
>> >> > > >
>> >> > > > Kernel IP routing table
>> >> > > > Destination     Gateway         Genmask         Flags Metric
>> >> > > > Ref
>> >> Use
>> >> > Iface
>> >> > > > 195.159.0.38    0.0.0.0         255.255.255.255 UH    0      0
>> >> 0
>> >> > ppp0
>> >> > > > 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0
>> >> 0
>> >> > lo
>> >> > > > 0.0.0.0         195.159.0.38    0.0.0.0         UG    0      0
>> >> 0
>> >> > ppp0
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > Well, there's yer problem, b'y!
>> >> > >
>> >> > > The eth0 config is setting up a default route (192.168.0.2). I'm
>> >> guessing
>> >> > when
>> >> > > you shut down eth0, your Internet connection worked fine. That's
> one
>> >> > workaround:
>> >> > > just shut down eth0 when you want to use the Internet
>> >> > > connection.
>> >> > EWS> I don't think it worked when I tried it. The other is
>> >> > > find where the default route is set for eth0 and remove it
>> >> > > (unless
>> >> > 192.168.0.2
>> >> > > is a gateway/router, it's not correct anyway).
>> >> > >
>> >> > > In general, you need 3 things for an Internet connection: a
>> >> > > path, a
>> >> > default
>> >> > > route, and a DNS. You check the first by pinging the ISP. You
>> >> > > check
>> > the
>> >> > second
>> >> > > by pinging a NUMBERED host (like the DNS), or checking the
>> >> > > routing
>> >> tables.
>> >> > You
>> >> > > check the third by pinging the DNS or pinging a known site (such
>> >> > > as www.yahoo.com)
>> >>
>> >> I can ping the computer on the other side, but I can't do anything
> else,
>> >> even if I shut down the network. Also, I know that it has worked
>> >> fine before, I sat at the old 486 and ssh'd with a computer on the
>> >> Internet, so that can't be the reason.
>> >>
>> >>
>> >>
>> >>
>>

"Eirik" <hxaxnxnxixbxaxlxkxaxnxnxixbxaxlx@xyxaxhxoxo.no> writes:

[...]

>The part of /var/log/messages concerning this:

>Dec 11 20:26:24 burk pppd[2383]: pppd 2.4.1 started by root, uid 0
>Dec 11 20:26:24 burk pppd[2383]: Using interface ppp0
>Dec 11 20:26:24 burk pppd[2383]: Connect: ppp0 <--> /dev/ttySHSF0
>Dec 11 20:26:28 burk pppd[2383]: not replacing existing default route to
>eth0 [192.168.0.2]

[...]

Well, why don't you stop ignoring what you have been told before?

DELETE the existing deafult route to your LAN. It is not needed,
and in your case, hindering you from getting out of your LAN. 
pppd will not replace an existing default route, and thus, no
packet will ever leave your machine outbound into the Internet.

Michael

-- 
Michael Buchenrieder * mibu@scrum.greenie.muc.de * http://www.muc.de/~mibu
          Lumber Cartel Unit #456 (TINLC) & Official Netscum
    Note: If you want me to send you email, don't munge your address.

I got tired of this whole matter, formatted the disk and installed Slackware
9. It works fine, but I've found out that the drivers for my Conexant HSF
modem no longer are offered for free at www.conexant.com. I downloaded an
older version(hsflinmodem-5.03.03.L3mbsibeta02062500), but it doesn't
function(it says that it can't find my modem).

I also wonder where the networking scripts of Slackware are. Are there none?