Networking Forums

Networking Forums > Computer Networking > Linux Networking > pppd connection problem

Reply
Thread Tools Display Modes

pppd connection problem

 
 
Johny Franslay
Guest
Posts: n/a

 
      10-06-2004, 02:36 AM
Hi,

I'm trying to connect to cingular's EDGE network using Sony GC82 card on
my Gentoo 2.4.26.
The pppd connection process went successfully and I was assigned an IP
address, however the server identified itself as 127.0.0.2.

Although it seemed that I am connected, I can't get or ping to anywhere.
The routing table while connected is as follow:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
127.0.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 127.0.0.2 0.0.0.0 UG 0 0 0 lo

as you can see, the default route uses 127.0.0.2 as its gateway but it
uses lo (loopback) device instead of ppp0, while 127.0.0.2 uses ppp0 device.

I tried to delete the default route entry and manually add it with ppp0
as the device:
bash-2.05b# route del default
bash-2.05b# route add default gw 127.0.0.2 dev ppp0
SIOCADDRT: Network is unreachable
bash-2.05b#

so it seemed that 127.0.0.2 is actually not connected to anywhere.

Have somebody has this problem? Or know any idea or suggestion on
possible solution?

Thanks.
Johny
 
Reply With Quote
 
 
 
 
Clifford Kite
Guest
Posts: n/a

 
      10-06-2004, 05:11 PM
Johny Franslay <(E-Mail Removed)> wrote:

> I'm trying to connect to cingular's EDGE network using Sony GC82 card on
> my Gentoo 2.4.26.
> The pppd connection process went successfully and I was assigned an IP
> address, however the server identified itself as 127.0.0.2.


If it really did that then Cingular is more broken than I would have
ever thought possible. The only way to be sure it did so is to add
the pppd debug option and look at the IPCP negotiation log messages.
More likely 127.0.0.2 comes from a mis-configured pppd option requesting
it as the remote's IP address, and the remote accepted it. But, hey,
I wouldn't completely rule out the possibility that Cingular would do
something that stupid.

Did the IP address you were assigned belong to a public or private
network?

> Although it seemed that I am connected, I can't get or ping to anywhere.
> The routing table while connected is as follow:
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 127.0.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
> 127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
> 0.0.0.0 127.0.0.2 0.0.0.0 UG 0 0 0 lo


> as you can see, the default route uses 127.0.0.2 as its gateway but it
> uses lo (loopback) device instead of ppp0, while 127.0.0.2 uses ppp0 device.


> I tried to delete the default route entry and manually add it with ppp0
> as the device:
> bash-2.05b# route del default
> bash-2.05b# route add default gw 127.0.0.2 dev ppp0
> SIOCADDRT: Network is unreachable
> bash-2.05b#


> so it seemed that 127.0.0.2 is actually not connected to anywhere.


It's a localhost address, perhaps for a name that's given to the
host. Check the /etc/hosts file. If there is such a default route
without a PPP link up then find where it's configured and remove it.
The 127.0.0.0/8 subnet is special and an IP address in it is not
handled in the same way that all other IP addresses are handled.

BTW, even if it's only up when a PPP link exists, the default route
was NOT assigned to lo by pppd.

Putting these lines

/sbin/ifconfig $IFNAME $IPLOCAL pointopoint 192.168.5.1
/sbin/route add default gw 192.168.5.1 $IFNAME

in /etc/ppp/ip-up *might* work if all else fails. The private IP
address 192.168.5.1 was arbitrarily chosen as the remote IP address
for pppd to use in IPCP negotiation. You are free to choose another
in another private IP address subnet. The environmental variables
in the lines are automatically assigned for the ip-up script by pppd.

> Have somebody has this problem? Or know any idea or suggestion on
> possible solution?


*Maybe* asking the remote to use a private IP address will cure the
problem. For example, the pppd option " :192.168.5.1 " causes pppd
to try and negotiate 192.168.5.1 as the peer's IP address. It really
shouldn't matter what IP address is assigned to the remote locally,
unless it's in the 127.0.0.0/8 subnet or the ISP is doing NAT.

No guarantee that any of these suggestions will work.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
 
Reply With Quote
 
Johny Franslay
Guest
Posts: n/a

 
      10-07-2004, 06:23 PM
Hey,
thanks a lot for the help.
I used the ":192.168.5.1" in the pppd option and it works.
Thanks again.

-Johny


Clifford Kite wrote:

> Johny Franslay <(E-Mail Removed)> wrote:
>
>
>>I'm trying to connect to cingular's EDGE network using Sony GC82 card on
>>my Gentoo 2.4.26.
>>The pppd connection process went successfully and I was assigned an IP
>>address, however the server identified itself as 127.0.0.2.

>
>
> If it really did that then Cingular is more broken than I would have
> ever thought possible. The only way to be sure it did so is to add
> the pppd debug option and look at the IPCP negotiation log messages.
> More likely 127.0.0.2 comes from a mis-configured pppd option requesting
> it as the remote's IP address, and the remote accepted it. But, hey,
> I wouldn't completely rule out the possibility that Cingular would do
> something that stupid.
>
> Did the IP address you were assigned belong to a public or private
> network?
>
>
>>Although it seemed that I am connected, I can't get or ping to anywhere.
>>The routing table while connected is as follow:
>>Kernel IP routing table
>>Destination Gateway Genmask Flags Metric Ref Use
>>Iface
>>127.0.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
>>127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
>>0.0.0.0 127.0.0.2 0.0.0.0 UG 0 0 0 lo

>
>
>>as you can see, the default route uses 127.0.0.2 as its gateway but it
>>uses lo (loopback) device instead of ppp0, while 127.0.0.2 uses ppp0 device.

>
>
>>I tried to delete the default route entry and manually add it with ppp0
>>as the device:
>>bash-2.05b# route del default
>>bash-2.05b# route add default gw 127.0.0.2 dev ppp0
>>SIOCADDRT: Network is unreachable
>>bash-2.05b#

>
>
>>so it seemed that 127.0.0.2 is actually not connected to anywhere.

>
>
> It's a localhost address, perhaps for a name that's given to the
> host. Check the /etc/hosts file. If there is such a default route
> without a PPP link up then find where it's configured and remove it.
> The 127.0.0.0/8 subnet is special and an IP address in it is not
> handled in the same way that all other IP addresses are handled.
>
> BTW, even if it's only up when a PPP link exists, the default route
> was NOT assigned to lo by pppd.
>
> Putting these lines
>
> /sbin/ifconfig $IFNAME $IPLOCAL pointopoint 192.168.5.1
> /sbin/route add default gw 192.168.5.1 $IFNAME
>
> in /etc/ppp/ip-up *might* work if all else fails. The private IP
> address 192.168.5.1 was arbitrarily chosen as the remote IP address
> for pppd to use in IPCP negotiation. You are free to choose another
> in another private IP address subnet. The environmental variables
> in the lines are automatically assigned for the ip-up script by pppd.
>
>
>>Have somebody has this problem? Or know any idea or suggestion on
>>possible solution?

>
>
> *Maybe* asking the remote to use a private IP address will cure the
> problem. For example, the pppd option " :192.168.5.1 " causes pppd
> to try and negotiate 192.168.5.1 as the peer's IP address. It really
> shouldn't matter what IP address is assigned to the remote locally,
> unless it's in the 127.0.0.0/8 subnet or the ISP is doing NAT.
>
> No guarantee that any of these suggestions will work.
>

 
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
Connection with pppd, but no traffic Doug Laidlaw Linux Networking 0 09-27-2005 06:54 AM
pppd-2.4.2 + kernel-2.6.7 problem Dimitris Mandalidis Linux Networking 13 07-18-2004 09:52 PM
pppd problem again???? Theophanis Kontogiannis Linux Networking 3 05-30-2004 01:54 PM
PPPD server routing problem? Mandrake/mgetty/pppd/D-link router martin02 Linux Networking 17 10-06-2003 03:06 PM
PPPD Connect Using Broadband Connection (problem) Spencer Linux Networking 2 09-11-2003 05:16 PM



1 2 3 4 5 6 7 8 9 10 11