Re: GPRS "Could not determine remote IP address" - PPP

This is a discussion on Re: GPRS "Could not determine remote IP address" - PPP ; What options do you have in the pppd configuration file? You should have a line like: :10.0.0.1 This tells pppd, that the phone will be addressed with 10.0.0.1. If I remember correctly, the r520 does not care with which address ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Re: GPRS "Could not determine remote IP address"

  1. Re: GPRS "Could not determine remote IP address"

    What options do you have in the pppd configuration file?

    You should have a line like:
    :10.0.0.1

    This tells pppd, that the phone will be addressed with 10.0.0.1. If I
    remember correctly, the r520 does not care with which address its
    addressed, so it gives and address of 0.0.0.0 to it self during IPCP, but
    pppd does not like this since 0.0.0.0 is not a valid IP address.

    -Mikko

  2. Re: GPRS "Could not determine remote IP address"

    In article <842dc172.0308271259.2ebcc596@posting.google.com>, James wrote:
    > Hi Mikko,
    > thanks for your response. I have tried it with this option in the pppd
    > options, however when I do this it simply assigns :10.0.0.1 to the
    > remote ip address and I still can't ping anything (other than the ip
    > address I have been assigned).


    Ahem, ICMP echo and echo responce, alias ping, messages may be filtered by
    your GPRS provider or by the hosts your trying to ping. If the PPP
    negotiations don't fail, interface stays up, routing tables point
    to the GPRS phone and your name servers have been properly set up (by pppd
    with option "usepeerdns" or manually by you to /etc/resolv.conf), then
    your connection should be up and running.

    If you now can't ping, try going to some webpage and dumping the
    interface traffic with tcpdump to see the actual packets on the move. It
    may even be, that your GPRS connection is actually a proxied WWW cage,
    and you need to setup your browser too before you see anything 'from the
    Internet'.

    -Mikko

    > Cheers,
    > James Fitzsimons


  3. Re: GPRS "Could not determine remote IP address"

    In Mikko Rapeli wrote:
    > In article <842dc172.0308271259.2ebcc596@posting.google.com>, James
    > wrote:
    >> Hi Mikko,
    >> thanks for your response. I have tried it with this option in the
    >> pppd options, however when I do this it simply assigns :10.0.0.1 to
    >> the remote ip address and I still can't ping anything (other than the
    >> ip address I have been assigned).

    >
    > Ahem, ICMP echo and echo responce, alias ping, messages may be
    > filtered by your GPRS provider or by the hosts your trying to ping.
    > If the PPP negotiations don't fail, interface stays up, routing
    > tables point to the GPRS phone and your name servers have been
    > properly set up (by pppd with option "usepeerdns" or manually by you
    > to /etc/resolv.conf), then your connection should be up and running.
    >
    > If you now can't ping, try going to some webpage and dumping the
    > interface traffic with tcpdump to see the actual packets on the move.
    > It may even be, that your GPRS connection is actually a proxied WWW
    > cage, and you need to setup your browser too before you see anything
    > 'from the Internet'.


    Hi Mikko and group,
    thanks again for your help. Here's where I'm at now. I have installed
    tcpdump (never used it before) and attempted to capture some information
    while requesting a web page while connected to the gprs network.

    I set my browsers proxy address to the default wap gateway (172.30.38.3)
    and port to the port specified by Vodafone (9021). Note, if I don't do
    this I simply get an immediate response that the host cannot be found.

    I then requested www.google.co.nz and captured the following using
    tcpdump.


    [root@Mandrake james]# tcpdump -i ppp0
    tcpdump: listening on ppp0
    20:46:59.865237 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    514985359(0)
    win 5840 (DF)
    20:47:02.861241 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    514985359(0)
    win 5840 (DF)
    20:47:08.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    514985359(0)
    win 5840 (DF)
    20:47:20.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    514985359(0)
    win 5840 (DF)
    20:47:44.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    514985359(0)
    win 5840 (DF)
    20:48:06.650897 10.240.60.39.who > 192.168.1.255.who: udp 156 (DF)
    20:50:07.155171 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    739078301(0)
    win 5840 (DF)
    20:50:07.779795 172.30.38.3.9201 > 10.240.60.39.32795: R 632958537:
    632958537(0)
    ack 514985360 win 33304 (DF)
    20:50:10.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    739078301(0)
    win 5840 (DF)
    20:50:16.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    739078301(0)
    win 5840 (DF)
    20:50:28.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    739078301(0)
    win 5840 (DF)
    20:50:52.151245 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    739078301(0)
    win 5840 (DF)
    20:51:06.680434 10.240.60.39.who > 192.168.1.255.who: udp 156 (DF)
    20:51:40.151245 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    739078301(0)
    win 5840 (DF)
    tcpdump: pcap_loop: recvfrom: Network is down
    [root@Mandrake james]#


    Unfortuantely the browser responds that the page contained no data, and
    the above doesn't mean too much to me...

    If anyone has any pointers I'd be very grateful.

    Thanks very much,
    James Fitzsimons

  4. Re: GPRS "Could not determine remote IP address"

    In article <20030828213140768+1200@news.paradise.net.nz>, James Fitzsimons wrote:
    > Hi Mikko and group,
    > thanks again for your help. Here's where I'm at now. I have installed
    > tcpdump (never used it before) and attempted to capture some information
    > while requesting a web page while connected to the gprs network.
    >
    > I set my browsers proxy address to the default wap gateway (172.30.38.3)
    > and port to the port specified by Vodafone (9021). Note, if I don't do
    > this I simply get an immediate response that the host cannot be found.


    Ok, I should have said this in my earlier post: to access Internet through
    GPRS, make shure you have a GPRS enabled SIM and the Access Point Name
    (APN) settings required for Internet access.

    Usually GPRS operators have two APN's; one for Internet and one for WAP
    connections. WAP is a proxied cage, where client browsers connect with
    WAP specific protocols over UDP (or not that often with TCP) to operators
    WAP gateway, a proxy sort of, and the WAP gateway connects to normal HTTP
    servers and downloads WML etc pages. The proxy then packs the WML
    content to the WSP (WAP Session Protocol) or something similar and sends
    the stuff to the browser over UDP (or TCP).

    So, with WAP the client can not send and receive IP or TCP or HTTP packets
    with Internet hosts.

    > I then requested www.google.co.nz and captured the following using
    > tcpdump.
    >
    >
    > [root@Mandrake james]# tcpdump -i ppp0
    > tcpdump: listening on ppp0
    > 20:46:59.865237 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    > 514985359(0)
    > win 5840 (DF)
    > 20:47:02.861241 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    > 514985359(0)
    > win 5840 (DF)
    > 20:47:08.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    > 514985359(0)
    > win 5840 (DF)
    > 20:47:20.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    > 514985359(0)
    > win 5840 (DF)
    > 20:47:44.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    > 514985359(0)
    > win 5840 (DF)
    > 20:48:06.650897 10.240.60.39.who > 192.168.1.255.who: udp 156 (DF)
    > 20:50:07.155171 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    > 739078301(0)
    > win 5840 (DF)
    > 20:50:07.779795 172.30.38.3.9201 > 10.240.60.39.32795: R 632958537:
    > 632958537(0)
    > ack 514985360 win 33304 (DF)
    > 20:50:10.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    > 739078301(0)
    > win 5840 (DF)
    > 20:50:16.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    > 739078301(0)
    > win 5840 (DF)
    > 20:50:28.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    > 739078301(0)
    > win 5840 (DF)
    > 20:50:52.151245 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    > 739078301(0)
    > win 5840 (DF)
    > 20:51:06.680434 10.240.60.39.who > 192.168.1.255.who: udp 156 (DF)
    > 20:51:40.151245 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    > 739078301(0)
    > win 5840 (DF)
    > tcpdump: pcap_loop: recvfrom: Network is down
    > [root@Mandrake james]#
    >
    >
    > Unfortuantely the browser responds that the page contained no data, and
    > the above doesn't mean too much to me...


    Yep, so the IP level connection to the operators network works. I may
    have missed something, but I don't see a nice way to access WWW through a
    WAP proxy without seeing only WAP specific content. And the WAP proxy may
    even block access to sites, that you don't pay the operotr for.

    > If anyone has any pointers I'd be very grateful.


    Pay for an Internet APN service and try again

    -Mikko

    > Thanks very much,
    > James Fitzsimons


  5. Re: GPRS "Could not determine remote IP address"

    > Ok, I should have said this in my earlier post: to access Internet
    > through GPRS, make shure you have a GPRS enabled SIM and the Access
    > Point Name (APN) settings required for Internet access.
    >


    I also didn't mention some things I should have earlier ;-) I do have a
    GPRS enabled SIM and a data APN (in this case it is www.vodafone.net.nz)
    I have tested this setup from a Compaq iPaq running pocketpc 2002 and
    have been able to browse the web (normal pages - not wap) connect to IRC,
    MSN messenger etc. so I know that my phone account is correct.

    > Usually GPRS operators have two APN's; one for Internet and one for
    > WAP connections. WAP is a proxied cage, where client browsers connect
    > with WAP specific protocols over UDP (or not that often with TCP) to
    > operators WAP gateway, a proxy sort of, and the WAP gateway connects
    > to normal HTTP servers and downloads WML etc pages. The proxy then
    > packs the WML content to the WSP (WAP Session Protocol) or something
    > similar and sends the stuff to the browser over UDP (or TCP).
    >
    > So, with WAP the client can not send and receive IP or TCP or HTTP
    > packets with Internet hosts.


    Right, vodafone NZ also has two APN's. A WAP and a data APN.


    >> Unfortuantely the browser responds that the page contained no data,
    >> and the above doesn't mean too much to me...

    >
    > Yep, so the IP level connection to the operators network works. I may
    > have missed something, but I don't see a nice way to access WWW
    > through a WAP proxy without seeing only WAP specific content. And the
    > WAP proxy may even block access to sites, that you don't pay the
    > operotr for.


    Right. I just changed the proxy address of the browser to the data APN (
    the www.vodafone.net.nz I mentioned earlier) with port 80, and tried
    again. Unfortuantely same result. The browser tried for a while, but
    never managed to display a page.

    >> If anyone has any pointers I'd be very grateful.

    >
    > Pay for an Internet APN service and try again


    Well, hopefully I have all the pieces, its just a matter of
    understanding how to put them all togeather under Linux ;-)

    Thank very much for your help,
    James Fitzsimons

  6. Re: GPRS "Could not determine remote IP address"

    James Fitzsimons writes:

    ]In Mikko Rapeli wrote:
    ]> In article <842dc172.0308271259.2ebcc596@posting.google.com>, James
    ]> wrote:
    ]>> Hi Mikko,
    ]>> thanks for your response. I have tried it with this option in the
    ]>> pppd options, however when I do this it simply assigns :10.0.0.1 to
    ]>> the remote ip address and I still can't ping anything (other than the
    ]>> ip address I have been assigned).
    ]>
    ]> Ahem, ICMP echo and echo responce, alias ping, messages may be
    ]> filtered by your GPRS provider or by the hosts your trying to ping.
    ]> If the PPP negotiations don't fail, interface stays up, routing
    ]> tables point to the GPRS phone and your name servers have been
    ]> properly set up (by pppd with option "usepeerdns" or manually by you
    ]> to /etc/resolv.conf), then your connection should be up and running.
    ]>
    ]> If you now can't ping, try going to some webpage and dumping the
    ]> interface traffic with tcpdump to see the actual packets on the move.
    ]> It may even be, that your GPRS connection is actually a proxied WWW
    ]> cage, and you need to setup your browser too before you see anything
    ]> 'from the Internet'.

    ]Hi Mikko and group,
    ]thanks again for your help. Here's where I'm at now. I have installed
    ]tcpdump (never used it before) and attempted to capture some information
    ]while requesting a web page while connected to the gprs network.

    ]I set my browsers proxy address to the default wap gateway (172.30.38.3)
    ]and port to the port specified by Vodafone (9021). Note, if I don't do
    ]this I simply get an immediate response that the host cannot be found.

    ]I then requested www.google.co.nz and captured the following using
    ]tcpdump.


    ][root@Mandrake james]# tcpdump -i ppp0
    ]tcpdump: listening on ppp0
    ]20:46:59.865237 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    ]514985359(0)
    ]win 5840 (DF)
    ]20:47:02.861241 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    ]514985359(0)
    ]win 5840 (DF)
    ]20:47:08.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    ]514985359(0)
    ]win 5840 (DF)
    ]20:47:20.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    ]514985359(0)
    ]win 5840 (DF)
    ]20:47:44.861242 10.240.60.39.32795 > 172.30.38.3.9201: S 514985359:
    ]514985359(0)
    ]win 5840 (DF)
    ]20:48:06.650897 10.240.60.39.who > 192.168.1.255.who: udp 156 (DF)
    ]20:50:07.155171 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    ]739078301(0)
    ]win 5840 (DF)
    ]20:50:07.779795 172.30.38.3.9201 > 10.240.60.39.32795: R 632958537:
    ]632958537(0)
    ]ack 514985360 win 33304 (DF)
    ]20:50:10.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    ]739078301(0)
    ]win 5840 (DF)
    ]20:50:16.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    ]739078301(0)
    ]win 5840 (DF)
    ]20:50:28.151242 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    ]739078301(0)
    ]win 5840 (DF)
    ]20:50:52.151245 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    ]739078301(0)
    ]win 5840 (DF)
    ]20:51:06.680434 10.240.60.39.who > 192.168.1.255.who: udp 156 (DF)
    ]20:51:40.151245 10.240.60.39.32796 > 172.30.38.3.9201: S 739078301:
    ]739078301(0)
    ]win 5840 (DF)
    ]tcpdump: pcap_loop: recvfrom: Network is down
    ][root@Mandrake james]#


    ]Unfortuantely the browser responds that the page contained no data, and
    ]the above doesn't mean too much to me...

    ]If anyone has any pointers I'd be very grateful.

    ]Thanks very much,
    ]James Fitzsimons
    It means that the problem is (probably) not pppd. You can send out
    messages and can get a response from the far machine. pppd exits, and is
    working.

    Why you get a blank page is unclear. Maybe teh page is blank. Try other
    www sites.




+ Reply to Thread