Networking Forums

Networking Forums > Computer Networking > Linux Networking > connection problem w/ ISP via PPP

Reply
Thread Tools Display Modes

connection problem w/ ISP via PPP

 
 
Adam
Guest
Posts: n/a

 
      01-20-2004, 06:12 PM
Are they any experts out there that can help? I am attempting to
connect to an ISP via dialup in Debian. I open the connection in
minicom give my user/pass info and start ppp, and then start the pppd
daemon on my machine as root and it seems to connect fine, but I cannot
ping the address of host given by pppd (or anywhere else). Here is the
pppd debug information. As far as I've read on newsgroups, 'Can't
locate module ppp-compress-21' and 'Cannot determine ethernet address
for proxy ARP' are not the cause of the problem. Any help is much
appreciated. Thank you,

-A

log file:
taco pppd[234]: pppd 2.4.1 started by root, uid 0
Jan 19 19:01:28 taco pppd[234]: using channel 2
Jan 19 19:01:28 taco pppd[234]: Using interface ppp0
Jan 19 19:01:28 taco pppd[234]: Connect: ppp0 <--> /dev/ttyS3
Jan 19 19:01:28 taco pppd[234]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0xa278ff5> <pcomp> <accomp>]
Jan 19 19:01:28 taco pppd[234]: rcvd [LCP ConfReq id=0x3 <asyncmap 0xa0000>
<magic 0xed8c21ee> <pcomp> <accomp>]
Jan 19 19:01:28 taco pppd[234]: sent [LCP ConfAck id=0x3 <asyncmap 0xa0000>
<magic 0xed8c21ee> <pcomp> <accomp>]
Jan 19 19:01:28 taco pppd[234]: rcvd [LCP ConfReq id=0x4 <asyncmap 0xa0000>
<magic 0xed8c21ee> <pcomp> <accomp>]
Jan 19 19:01:28 taco pppd[234]: sent [LCP ConfAck id=0x4 <asyncmap 0xa0000>
<magic 0xed8c21ee> <pcomp> <accomp>]
Jan 19 19:01:28 taco pppd[234]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>
<magic 0xa278ff5> <pcomp> <accomp>]
Jan 19 19:01:28 taco pppd[234]: sent [LCP EchoReq id=0x0 magic=0xa278ff5]
Jan 19 19:01:28 taco pppd[234]: kernel does not support PPP filtering
Jan 19 19:01:28 taco pppd[234]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0>
<compress VJ 0f 01>]
Jan 19 19:01:28 taco modprobe: modprobe: Can't locate module ppp-compress-21
Jan 19 19:01:28 taco modprobe: modprobe: Can't locate module ppp-compress-21
Jan 19 19:01:28 taco pppd[234]: sent [CCP ConfReq id=0x1 <deflate 15>
<deflate(old#) 15>]
Jan 19 19:01:29 taco pppd[234]: rcvd [LCP EchoRep id=0x0 magic=0xed8c21ee]
Jan 19 19:01:29 taco pppd[234]: rcvd [IPCP ConfReq id=0x1 <compress VJ 0f
00> <addr 142.150.128.50>]
Jan 19 19:01:29 taco pppd[234]: sent [IPCP ConfAck id=0x1 <compress VJ 0f
00> <addr 142.150.128.50>]
Jan 19 19:01:29 taco pppd[234]: rcvd [IPCP ConfNak id=0x1 <addr
142.150.134.132>]
Jan 19 19:01:29 taco pppd[234]: sent [IPCP ConfReq id=0x2 <addr
142.150.134.132> <compress VJ 0f 01>]
Jan 19 19:01:29 taco pppd[234]: rcvd [LCP ProtRej id=0x5 80 fd 01 01 00 0c
1a 04 78 00 18 04 78 00]
Jan 19 19:01:29 taco pppd[234]: rcvd [IPCP ConfAck id=0x2 <addr
142.150.134.132> <compress VJ 0f 01>]
Jan 19 19:01:29 taco pppd[234]: Cannot determine ethernet address for proxy
ARP
Jan 19 19:01:29 taco pppd[234]: local IP address 142.150.134.132
Jan 19 19:01:29 taco pppd[234]: remote IP address 142.150.128.50
Jan 19 19:01:29 taco pppd[234]: Script /etc/ppp/ip-up started (pid 239)
Jan 19 19:01:29 taco pppd[234]: Script /etc/ppp/ip-up finished (pid 239),
status = 0x0
Jan 19 19:01:58 taco pppd[234]: sent [LCP EchoReq id=0x1 magic=0xa278ff5]
Jan 19 19:01:58 taco pppd[234]: rcvd [LCP EchoRep id=0x1 magic=0xed8c21ee]
Jan 19 19:02:28 taco pppd[234]: sent [LCP EchoReq id=0x2 magic=0xa278ff5]
Jan 19 19:02:28 taco pppd[234]: rcvd [LCP EchoRep id=0x2 magic=0xed8c21ee]
Jan 19 19:02:58 taco pppd[234]: sent [LCP EchoReq id=0x3 magic=0xa278ff5]
Jan 19 19:02:58 taco pppd[234]: rcvd [LCP EchoRep id=0x3 magic=0xed8c21ee]
Jan 19 19:03:28 taco pppd[234]: sent [LCP EchoReq id=0x4 magic=0xa278ff5]
Jan 19 19:03:28 taco pppd[234]: rcvd [LCP EchoRep id=0x4 magic=0xed8c21ee]
Jan 19 19:03:58 taco pppd[234]: sent [LCP EchoReq id=0x5 magic=0xa278ff5]
Jan 19 19:03:58 taco pppd[234]: rcvd [LCP EchoRep id=0x5 magic=0xed8c21ee]
Jan 19 19:04:28 taco pppd[234]: sent [LCP EchoReq id=0x6 magic=0xa278ff5]
Jan 19 19:04:28 taco pppd[234]: rcvd [LCP EchoRep id=0x6 magic=0xed8c21ee]
Jan 19 19:04:58 taco pppd[234]: sent [LCP EchoReq id=0x7 magic=0xa278ff5]
Jan 19 19:04:59 taco pppd[234]: rcvd [LCP EchoRep id=0x7 magic=0xed8c21ee]
Jan 19 19:05:28 taco pppd[234]: sent [LCP EchoReq id=0x8 magic=0xa278ff5]
Jan 19 19:05:28 taco pppd[234]: rcvd [LCP EchoRep id=0x8 magic=0xed8c21ee]
Jan 19 19:05:58 taco pppd[234]: sent [LCP EchoReq id=0x9 magic=0xa278ff5]
Jan 19 19:05:58 taco pppd[234]: rcvd [LCP EchoRep id=0x9 magic=0xed8c21ee]
Jan 19 19:06:28 taco pppd[234]: sent [LCP EchoReq id=0xa magic=0xa278ff5]
Jan 19 19:06:28 taco pppd[234]: rcvd [LCP EchoRep id=0xa magic=0xed8c21ee]
Jan 19 19:05:51 taco ntpd[186]: time reset -60.509948 s
Jan 19 19:05:51 taco ntpd[186]: kernel time discipline status change 41
Jan 19 19:05:51 taco ntpd[186]: synchronisation lost
Jan 19 19:06:58 taco pppd[234]: sent [LCP EchoReq id=0xb magic=0xa278ff5]
Jan 19 19:06:58 taco pppd[234]: rcvd [LCP EchoRep id=0xb magic=0xed8c21ee]
Jan 19 19:07:28 taco pppd[234]: sent [LCP EchoReq id=0xc magic=0xa278ff5]
Jan 19 19:07:28 taco pppd[234]: rcvd [LCP EchoRep id=0xc magic=0xed8c21ee]
Jan 19 19:07:58 taco pppd[234]: sent [LCP EchoReq id=0xd magic=0xa278ff5]
Jan 19 19:07:58 taco pppd[234]: rcvd [LCP EchoRep id=0xd magic=0xed8c21ee]
Jan 19 19:08:28 taco pppd[234]: sent [LCP EchoReq id=0xe magic=0xa278ff5]
Jan 19 19:08:28 taco pppd[234]: rcvd [LCP EchoRep id=0xe magic=0xed8c21ee]
Jan 19 19:08:58 taco pppd[234]: sent [LCP EchoReq id=0xf magic=0xa278ff5]
Jan 19 19:08:58 taco pppd[234]: rcvd [LCP EchoRep id=0xf magic=0xed8c21ee]
Jan 19 19:09:28 taco pppd[234]: sent [LCP EchoReq id=0x10 magic=0xa278ff5]
Jan 19 19:09:28 taco pppd[234]: rcvd [LCP EchoRep id=0x10 magic=0xed8c21ee]
Jan 19 19:09:58 taco pppd[234]: sent [LCP EchoReq id=0x11 magic=0xa278ff5]
Jan 19 19:09:58 taco pppd[234]: rcvd [LCP EchoRep id=0x11 magic=0xed8c21ee]
Jan 19 19:10:28 taco pppd[234]: sent [LCP EchoReq id=0x12 magic=0xa278ff5]
Jan 19 19:10:29 taco pppd[234]: rcvd [LCP EchoRep id=0x12 magic=0xed8c21ee]
Jan 19 19:10:58 taco pppd[234]: sent [LCP EchoReq id=0x13 magic=0xa278ff5]
Jan 19 19:10:59 taco pppd[234]: rcvd [LCP EchoRep id=0x13 magic=0xed8c21ee]
Jan 19 19:11:28 taco pppd[234]: sent [LCP EchoReq id=0x14 magic=0xa278ff5]
Jan 19 19:11:29 taco pppd[234]: rcvd [LCP EchoRep id=0x14 magic=0xed8c21ee]
Jan 19 19:11:58 taco pppd[234]: sent [LCP EchoReq id=0x15 magic=0xa278ff5]
Jan 19 19:11:59 taco pppd[234]: rcvd [LCP EchoRep id=0x15 magic=0xed8c21ee]
Jan 19 19:12:23 taco pppd[234]: Terminating on signal 15.
Jan 19 19:12:23 taco pppd[234]: Script /etc/ppp/ip-down started (pid 275)
Jan 19 19:12:23 taco pppd[234]: sent [LCP TermReq id=0x2 "User request"]
Jan 19 19:12:23 taco pppd[234]: Script /etc/ppp/ip-down finished (pid 275),
status = 0x0
Jan 19 19:12:23 taco pppd[234]: rcvd [LCP TermAck id=0x2]
Jan 19 19:12:23 taco pppd[234]: Connection terminated.
Jan 19 19:12:23 taco pppd[234]: Connect time 11.0 minutes.
Jan 19 19:12:23 taco pppd[234]: Sent 7672 bytes, received 1070 bytes.
Jan 19 19:12:24 taco pppd[234]: Exit.
Jan 19 19:12:29 taco ntpd[186]: sendto(137.82.1.3): Network is unreachable


 
Reply With Quote
 
 
 
 
Horst Knobloch
Guest
Posts: n/a

 
      01-20-2004, 11:41 PM
Adam <(E-Mail Removed)> wrote:

> Are they any experts out there that can help? I am attempting to
> connect to an ISP via dialup in Debian. I open the connection in
> minicom give my user/pass info and start ppp, and then start the pppd
> daemon on my machine as root and it seems to connect fine, but I cannot
> ping the address of host given by pppd (or anywhere else).


I see in the below log, that your are not given the entries for
the ISP's name servers. So, you should add usepeerdns to the
ppp options file. If you do so and dial-up again, you will find
the DNS server entries in /etc/pppd/resolv.conf. Create a link
from /etc/resolv.conf to this file.

Check whether you have the "defaultroute" option in the ppp
options file. If not, add it.

BTW: Posting the ppp options file would have been a good
idea. ;-)

However it is still not understandable why you can't even ping
your own or the peer's IP address. So check again, call ifconfig
ppp0 and ping both IP adresses listed. If this doesn't work
check whether you have some packet filter rules in place
blocking ICMP by doing a "iptables-save" or "iptables -nvL".

If you see some rules listed, the easiest would be to get rid
of them by invoking "iptables -F" for a short test.


> Here is the
> pppd debug information. As far as I've read on newsgroups, 'Can't
> locate module ppp-compress-21' and 'Cannot determine ethernet address
> for proxy ARP' are not the cause of the problem. Any help is much
> appreciated. Thank you,


Remove the proxy-arp option from your ppp configuration file, add
"alias ppp-compress-21 bsd_comp" to /etc/modules.conf and the log
file should look a little nicer.

[...]
> Jan 19 19:01:29 taco pppd[234]: local IP address 142.150.134.132
> Jan 19 19:01:29 taco pppd[234]: remote IP address 142.150.128.50
> Jan 19 19:01:29 taco pppd[234]: Script /etc/ppp/ip-up started (pid 239)
> Jan 19 19:01:29 taco pppd[234]: Script /etc/ppp/ip-up finished (pid 239),
> status = 0x0

[...]

And last but not least, have a look to
http://axion.physics.ubc.ca/ppp-linux.html

HTH

Ciao, Horst
--
»When pings go wrong (It hurts me too)« E.Clapton/E.James/P.Tscharn
 
Reply With Quote
 
Fred Ferd
Guest
Posts: n/a

 
      01-22-2004, 12:45 PM

"Adam" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Are they any experts out there that can help? I am attempting to
> connect to an ISP via dialup in Debian. I open the connection in
> minicom give my user/pass info and start ppp, and then start the pppd
> daemon on my machine as root and it seems to connect fine, but I cannot
> ping the address of host given by pppd (or anywhere else). Here is the
> pppd debug information. As far as I've read on newsgroups, 'Can't
> locate module ppp-compress-21' and 'Cannot determine ethernet address
> for proxy ARP' are not the cause of the problem. Any help is much
> appreciated. Thank you,
>
> -A



Well the log file appears normal, the connection was negotiated and ended 10
minutes later because of sig 15 - you killed it.


The two errors you get are not important. proxy arp is to make the remote
end of the PPP link appear to be on your local LAN, for the benefit of other
computers on your local LAN.

Not important as you arent the PPP server.

If you cant use the link, you may have a firewall in place.

find the firewalls /etc/init.d/* script and stop it

eg run
/etc/init.d/shorewall stop






 
Reply With Quote
 
Adam
Guest
Posts: n/a

 
      01-23-2004, 02:16 PM
I tried the above suggestions with no success. I've tried every suggested
change in ppp options to no avail. People have suggested ip filtering, but
i don't even have it installed in my kernel (iptables isn't there).

'options'
defaultroute
-detach
asyncmap a0000
crtscts
lock
hide-password
noipdefault
debug


'route -n'
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
142.150.128.47 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
0.0.0.0 142.150.128.47 0.0.0.0 UG 0 0 0 ppp0


'ifconfig -a'
eth0 Link encap:Ethernet HWaddr 00:C0:A8:47:F7:85
BROADCAST NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:684 (684.0 b)
Interrupt:9 Base address:0x300

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1252 (1.2 KiB) TX bytes:1252 (1.2 KiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:142.150.134.89 P-t-P:142.150.128.47
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:3 errors:1 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:42 (42.0 b) TX bytes:48 (48.0 b)

tunl0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

"Fred Ferd" <(E-Mail Removed)> wrote in message
news:400fd40d$(E-Mail Removed)...
>
> "Adam" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Are they any experts out there that can help? I am attempting to
> > connect to an ISP via dialup in Debian. I open the connection in
> > minicom give my user/pass info and start ppp, and then start the pppd
> > daemon on my machine as root and it seems to connect fine, but I cannot
> > ping the address of host given by pppd (or anywhere else). Here is the
> > pppd debug information. As far as I've read on newsgroups, 'Can't
> > locate module ppp-compress-21' and 'Cannot determine ethernet address
> > for proxy ARP' are not the cause of the problem. Any help is much
> > appreciated. Thank you,
> >
> > -A

>
>
> Well the log file appears normal, the connection was negotiated and ended

10
> minutes later because of sig 15 - you killed it.
>
>
> The two errors you get are not important. proxy arp is to make the remote
> end of the PPP link appear to be on your local LAN, for the benefit of

other
> computers on your local LAN.
>
> Not important as you arent the PPP server.
>
> If you cant use the link, you may have a firewall in place.
>
> find the firewalls /etc/init.d/* script and stop it
>
> eg run
> /etc/init.d/shorewall stop
>
>
>
>
>
>



 
Reply With Quote
 
Horst Knobloch
Guest
Posts: n/a

 
      01-23-2004, 05:51 PM
Adam <(E-Mail Removed)> wrote:

> I tried the above suggestions with no success. I've tried every
> suggested
> change in ppp options to no avail. People have suggested ip filtering,
> but i don't even have it installed in my kernel (iptables isn't there).
>
> 'options'
> defaultroute
> -detach
> asyncmap a0000
> crtscts
> lock
> hide-password
> noipdefault
> debug


There's still usepeerdns missing. So if you don't have valid
name servers already in /etc/resolv.conf you can't use names
to access the Internet, eg. for ping'ing.


> 'route -n'
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 142.150.128.47 0.0.0.0 255.255.255.255 UH 0 0 0
> ppp0
> 0.0.0.0 142.150.128.47 0.0.0.0 UG 0 0 0
> ppp0


Where is the entry for the lo-interface? Did you leave it out or
wasn't it there? Otherwise it looks good.


> 'ifconfig -a'

[eth0 & lo]
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:142.150.134.89 P-t-P:142.150.128.47
> Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:3 errors:1 dropped:0 overruns:0 frame:0
> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:3
> RX bytes:42 (42.0 b) TX bytes:48 (48.0 b)


Do you have tried to ping both of the IP adresses listed
in the ppp0 output? Ping by host names and IP address. Please
copy-and-paste the exact output.


> tunl0 Link encap:IPIP Tunnel HWaddr
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


Do you need this IPIP Tunnel? If not I would get rid of
it. (However this should not cause your problems).


Ciao, Horst
--
»When pings go wrong (It hurts me too)« E.Clapton/E.James/P.Tscharn
 
Reply With Quote
 
Adam
Guest
Posts: n/a

 
      01-23-2004, 07:56 PM
But i should still be able to ping the other end of the PPP connection by ip
address correct? I can only ping my own address by IP. I can't ping the
other end of the ppp connection. I have the nameserver in /etc/resolv.conf
but i will try usepeerdns but i don't know why i can't ping the remote
machine using the IP address given by pppd. 'iptables' doesn't exist on my
system (debian w/ 2.4 series kernel), i think because i don't have filtering
support built into my kernel.

there was no 'lo' entry in route -n, but there was one in 'ifconfig -a'
could this be a problem? if so what should i do? what else should i post?

no i don't need the ip tunnel, but i don't know how to turn it off. My
machine is at home so i will try posting more output tomorrow.

"Horst Knobloch" <(E-Mail Removed)> wrote in message
news:burqeo$1b2l$(E-Mail Removed)...
> Adam <(E-Mail Removed)> wrote:
>
> > I tried the above suggestions with no success. I've tried every
> > suggested
> > change in ppp options to no avail. People have suggested ip filtering,
> > but i don't even have it installed in my kernel (iptables isn't there).
> >
> > 'options'
> > defaultroute
> > -detach
> > asyncmap a0000
> > crtscts
> > lock
> > hide-password
> > noipdefault
> > debug

>
> There's still usepeerdns missing. So if you don't have valid
> name servers already in /etc/resolv.conf you can't use names
> to access the Internet, eg. for ping'ing.
>
>
> > 'route -n'
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 142.150.128.47 0.0.0.0 255.255.255.255 UH 0 0 0
> > ppp0
> > 0.0.0.0 142.150.128.47 0.0.0.0 UG 0 0 0
> > ppp0

>
> Where is the entry for the lo-interface? Did you leave it out or
> wasn't it there? Otherwise it looks good.
>
>
> > 'ifconfig -a'

> [eth0 & lo]
> > ppp0 Link encap:Point-to-Point Protocol
> > inet addr:142.150.134.89 P-t-P:142.150.128.47
> > Mask:255.255.255.255
> > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> > RX packets:3 errors:1 dropped:0 overruns:0 frame:0
> > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:3
> > RX bytes:42 (42.0 b) TX bytes:48 (48.0 b)

>
> Do you have tried to ping both of the IP adresses listed
> in the ppp0 output? Ping by host names and IP address. Please
> copy-and-paste the exact output.
>
>
> > tunl0 Link encap:IPIP Tunnel HWaddr
> > NOARP MTU:1480 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

>
> Do you need this IPIP Tunnel? If not I would get rid of
> it. (However this should not cause your problems).
>
>
> Ciao, Horst
> --
> »When pings go wrong (It hurts me too)« E.Clapton/E.James/P.Tscharn



 
Reply With Quote
 
Clifford Kite
Guest
Posts: n/a

 
      01-23-2004, 09:28 PM
Adam <(E-Mail Removed)> wrote:
> But i should still be able to ping the other end of the PPP
> connection by ip address correct?


Yes, unless the peer (ISP connection host) is configured to block ping
requests.

-- Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* In his wisdom RMS decided that people need no man pages when they
can use GNU's beautiful info system.
Unfortunately, everybody I know greatly prefers man pages.
- From the man-pages-1.55/man1/README */
 
Reply With Quote
 
Horst Knobloch
Guest
Posts: n/a

 
      01-24-2004, 10:44 AM
Adam <(E-Mail Removed)> wrote:

> But i should still be able to ping the other end of the PPP connection by
> ip
> address correct?


Yes.

> I can only ping my own address by IP. I can't ping the
> other end of the ppp connection.

[...]
> there was no 'lo' entry in route -n, but there was one in 'ifconfig -a'
> could this be a problem?


I guess it is the other way around, you can ping the remote
address but not your own, since it seems that the lo interface
isn't up.

Invoke as root:

ifconfig lo up
route add -net 127.0.0.0 netmask 255.0.0.0 dev lo

and try again the pings.

You should also check your network settings, because it is
a "little" bit unusual that the local loopback interface
isn't configured properly. I'm sure that your distribution
has some nice GUI tool for this.

BTW: Do you have configure and compiled the kernel on your own,
or is it Debian's plain vanilla kernel.

Ciao, Horst
--
»When pings go wrong (It hurts me too)« E.Clapton/E.James/P.Tscharn
 
Reply With Quote
 
Sarah
Guest
Posts: n/a

 
      01-24-2004, 03:18 PM

Horst Knobloch <(E-Mail Removed)> wrote in message
news:butlq6$1r3p$(E-Mail Removed)...
> Adam <(E-Mail Removed)> wrote:
>
> > But i should still be able to ping the other end of the PPP connection

by
> > ip
> > address correct?

>
> Yes.
>
> > I can only ping my own address by IP. I can't ping the
> > other end of the ppp connection.

> [...]
> > there was no 'lo' entry in route -n, but there was one in 'ifconfig -a'
> > could this be a problem?

>
> I guess it is the other way around, you can ping the remote
> address but not your own, since it seems that the lo interface
> isn't up.
>
> Invoke as root:
>
> ifconfig lo up
> route add -net 127.0.0.0 netmask 255.0.0.0 dev lo
>
> and try again the pings.
>
> You should also check your network settings, because it is
> a "little" bit unusual that the local loopback interface
> isn't configured properly. I'm sure that your distribution
> has some nice GUI tool for this.
>
> BTW: Do you have configure and compiled the kernel on your own,
> or is it Debian's plain vanilla kernel.


No i configured and compiled the kernel on my own. I could be missing some
important modules i suppose but i thought i got everything.

>
> Ciao, Horst
> --
> »When pings go wrong (It hurts me too)« E.Clapton/E.James/P.Tscharn



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Help: Connection Problem Amy Lee Linux Networking 4 03-20-2008 06:58 PM
Connection problem Joe Windows Networking 7 12-20-2004 12:14 AM
Odd connection problem msmcg Broadband Hardware 1 07-22-2004 05:56 AM
W98 to XP connection problem Jeff Malka Wireless Internet 3 12-25-2003 11:01 PM
internet connection problem with MS TV/video connection adapter Carl Windows Networking 0 08-08-2003 09:37 PM



1 2 3 4 5 6 7 8 9 10 11