Problem dialing in from pocket pc phone - PPP

This is a discussion on Problem dialing in from pocket pc phone - PPP ; Hello, after a full day of trying to get my first dialin server to work properly, I finally got stuck. I've tried many different configurations and got list quite a bit. Please help! I want to dial in from a ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Problem dialing in from pocket pc phone

  1. Problem dialing in from pocket pc phone

    Hello,

    after a full day of trying to get my first dialin server to work
    properly, I finally got stuck. I've tried many different configurations
    and got list quite a bit. Please help!

    I want to dial in from a pocket pc phone (T-Mobile MDA compact) so I can
    use my DSL-connection with it. The connection itself is established and
    kept up until the peer hangs up, but all I can do is ping the
    dial-in-server and other clients in the local network. No DNS-Lookup,
    mail, www ...

    I'm running sarge with pppd 2.4.2 and pppdcapiplugin on an Asus
    P4P800-VM based system with an AVM B1 ISDN-controller. The system itself
    connects to the internet via an IPCop-Router. It has only eth0
    (192.168.2.1/255.255.255.0) and IPCop with DHCP and DNS is at 192.168.2.3.

    Here's more information:

    cat /etc/ppp/peers/incoming-cli

    lock
    debug
    name isdnin
    logfile /var/log/pppd_gsm.log
    plugin capiplugin.so
    inmsn 4200083
    auth
    login
    require-pap
    -detach
    protocol hdlc
    sync
    nodefaultroute
    192.168.2.1:192.168.2.39
    ms-dns 192.168.2.3
    ms-wins 192.168.2.1
    proxyarp
    ktune
    noipx
    nobsdcomp
    noccp
    nodeflate


    cat /var/log/pppd_gsm.log

    plci_change_state:0x101 4 -> 6 event=12
    controller 1: listen_change_state 2 -> 3
    controller 1: listen_change_state state=3 event=1 ????
    controller 1: listen_change_state state=3 event=1 ????
    controller 1: listen_change_state state=3 event=1 ????
    contr 1: listenconf Info=0x0000 (No additional information)
    infomask=0x144 cipmask=0x0 capimask2=0x0
    controller 1: listen_change_state 3 -> 0
    contr 1: listenconf Info=0x0000 (No additional information)
    infomask=0x144 cipmask=0x0 capimask2=0x0
    controller 1: listen_change_state state=0 event=3 ????
    contr 1: listenconf Info=0x0000 (No additional information)
    infomask=0x144 cipmask=0x0 capimask2=0x0
    controller 1: listen_change_state state=0 event=3 ????
    contr 1: listenconf Info=0x0000 (No additional information)
    infomask=0x144 cipmask=0x0 capimask2=0x0
    controller 1: listen_change_state state=0 event=3 ????
    plci_change_state:0x101 6 -> 3 event=6
    ncci_change_state:0x10101 0 -> 2 event=2
    ncci_change_state:0x10101 2 -> 3 event=6
    ncci_change_state:0x10101 3 -> 4 event=7
    ncci 0x10101 up
    capiplugin: connected: "177********" -> "42******" incoming
    (pcli=0x101/ncci=0x10101)
    capiplugin: using /dev/capi/0: "177********" -> "42******" incoming
    (pcli=0x101/ncci=0x10101)
    using channel 2
    Using interface ppp0
    Connect: ppp0 <--> /dev/capi/0
    sent [LCP ConfReq id=0x1
    ]
    capiplugin: phase establish (was serialconn).
    rcvd [LCP ConfReq id=0x0 ]
    sent [LCP ConfAck id=0x0 ]
    rcvd [LCP ConfAck id=0x1
    ]
    sent [LCP EchoReq id=0x0 magic=0x16247b86]
    capiplugin: phase authenticate (was establish).
    rcvd [PAP AuthReq id=0x0 user="tim" password=]
    user tim logged in
    sent [PAP AuthAck id=0x0 "Success"]
    PAP peer authentication succeeded for tim
    Script /etc/ppp/auth-up started (pid 1389)
    capiplugin: phase network (was authenticate).
    sent [IPCP ConfReq id=0x1 ]
    rcvd [LCP EchoRep id=0x0 magic=0x0]
    Script /etc/ppp/auth-up finished (pid 1389), status = 0x0
    rcvd [IPCP ConfReq id=0x0 0.0.0.0> ..0.0>]
    sent [IPCP ConfNak id=0x0
    8.2.1>]
    rcvd [IPV6CP ConfReq id=0x0 ]
    Unsupported protocol 0x8057 received
    sent [LCP ProtRej id=0x2 80 57 01 00 00 0e 01 0a d7 8c 9a 08 7d 94 5b 3e]
    rcvd [IPCP ConfAck id=0x1 ]
    rcvd [IPCP ConfReq id=0x1
    2.3> ]
    sent [IPCP ConfAck id=0x1
    2.3> ]
    found interface eth0 for proxy arp
    local IP address 192.168.2.1
    remote IP address 192.168.2.39
    capiplugin: phase running (was network).
    Script /etc/ppp/ip-up started (pid 1390)
    Script /etc/ppp/ip-up finished (pid 1390), status = 0x0
    rcvd [LCP TermReq id=0x1]
    LCP terminated by peer
    Script /etc/ppp/auth-down started (pid 1447)
    capiplugin: phase network (was running).
    Connect time 2.5 minutes.
    Sent 426 bytes, received 2669 bytes.
    Script /etc/ppp/ip-down started (pid 1448)
    capiplugin: phase establish (was network).
    sent [LCP TermAck id=0x1]
    Script /etc/ppp/auth-down finished (pid 1447), status = 0x0
    Script /etc/ppp/ip-down finished (pid 1448), status = 0x0
    capiplugin: phase dead (was establish).
    controller 1: listen_change_state 0 -> 1
    controller 1: listen_change_state state=1 event=1 ????
    controller 1: listen_change_state state=1 event=1 ????
    controller 1: listen_change_state state=1 event=1 ????
    ncci_change_state:0x10101 4 -> 6 event=12
    ncci_change_state:0x10101 6 -> 7 event=10
    ncci_change_state:0x10101 7 -> 0 event=13
    plci_change_state:0x101 3 -> 7 event=8
    DISCONNECT_IND reason 0x3490 (Normal call clearing) for plci 0x101
    plci_change_state:0x101 7 -> 8 event=9
    plci_change_state:0x101 8 -> 0 event=11
    capiplugin: disconnect(local): "177********" -> "42******" incoming
    (pcli=0x101/ncci=0x10101) 0x3490 (0x3301) - Normal call clear
    ing
    Connection terminated.
    Modem hangup
    capiplugin: phase disconnect (was dead).
    controller 1: listen_change_state state=1 event=1 ????
    controller 1: listen_change_state state=1 event=1 ????
    controller 1: listen_change_state state=1 event=1 ????
    controller 1: listen_change_state state=1 event=1 ????
    contr 1: listenconf Info=0x0000 (No additional information)
    infomask=0x144 cipmask=0x0 capimask2=0x0
    controller 1: listen_change_state 1 -> 0
    capiplugin: exit


    route -n
    Kernel IP Routentabelle
    Ziel Router Genmask Flags Metric Ref Use
    Iface
    192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
    0.0.0.0 192.168.2.3 0.0.0.0 UG 0 0 0 eth0


    cat /proc/sys/net/ipv4/ip_forward
    1


    lsmod

    Module Size Used by Not tainted
    nfsd 72624 8 (autoclean)
    capi 18080 10
    capifs 3856 1 [capi]
    nfs 70780 2 (autoclean)
    lockd 49520 1 (autoclean) [nfsd nfs]
    sunrpc 68576 1 (autoclean) [nfsd nfs lockd]
    b1pci 6596 1
    b1dma 11192 0 [b1pci]
    b1 17504 0 [b1pci b1dma]
    capidrv 26868 3
    kernelcapi 30144 7 [capi b1pci capidrv]
    capiutil 22048 0 [capidrv kernelcapi]
    bsd_comp 4248 0 (unused)
    isdn_bsdcomp 6316 0 (unused)
    ppp_async 6688 0
    ppp_deflate 3320 0 (unused)
    zlib_inflate 18628 0 [ppp_deflate]
    zlib_deflate 18968 0 [ppp_deflate]
    ppp_synctty 5256 0
    ppp_generic 17156 0 [bsd_comp ppp_async ppp_deflate
    ppp_synctty]
    isdn 102752 3 [capidrv isdn_bsdcomp]
    slhc 4784 0 [ppp_generic isdn]
    dvb-ttpci 279988 4
    ves1x93 4048 1
    alps_tdmb7 3240 0
    alps_tdlb7 4792 0
    grundig_29504-401 3596 0
    grundig_29504-491 2916 0
    stv0299 8332 0 (unused)
    ves1820 4256 0
    ttpci-eeprom 1232 0 [dvb-ttpci]
    dvb-core 36768 12 [dvb-ttpci ves1x93 alps_tdmb7
    alps_tdlb7 grundig_29504-401 grundig_29504-491 stv0299 ves1820]
    saa7146_vv 32604 0 [dvb-ttpci]
    saa7146 9952 0 [dvb-ttpci saa7146_vv]
    video-buf 9968 0 [saa7146_vv]
    v4l2-common 2848 0 [saa7146_vv]
    v4l1-compat 11912 0 [saa7146_vv]


    Thanks for any help

    Tim

  2. Re: Problem dialing in from pocket pc phone

    Tim Kaufmann writes:
    > I want to dial in from a pocket pc phone (T-Mobile MDA compact) so I
    > can use my DSL-connection with it. The connection itself is
    > established and kept up until the peer hangs up, but all I can do is
    > ping the dial-in-server and other clients in the local network. No
    > DNS-Lookup, mail, www ...


    In that case, it doesn't sound like you have a PPP problem at all.

    > I'm running sarge with pppd 2.4.2 and pppdcapiplugin on an Asus
    > P4P800-VM based system with an AVM B1 ISDN-controller. The system
    > itself connects to the internet via an IPCop-Router. It has only eth0
    > (192.168.2.1/255.255.255.0) and IPCop with DHCP and DNS is at
    > 192.168.2.3.


    Do you have NAT ("IP masquerade") configured? If not, then there's
    just no way that nodes using those RFC 1918 addresses can ever talk to
    anything on the Internet. Is it configured correctly?

    You probably want to go to a Linux group with this problem, as it
    sounds like the problem is related to Linux configuration, and not PPP
    itself.

    > Here's more information:
    >
    > cat /etc/ppp/peers/incoming-cli


    All that looks good.

    > cat /var/log/pppd_gsm.log


    As does that.

    > lsmod


    Not quite sure what I'm looking for there (as I'm no longer much of a
    Linux user), but I don't see anything that looks like NAT or IP
    masquerade.

    --
    James Carlson, KISS Interop
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  3. Re: Problem dialing in from pocket pc phone

    James Carlson wrote:

    > Do you have NAT ("IP masquerade") configured? If not, then there's
    > just no way that nodes using those RFC 1918 addresses can ever talk to
    > anything on the Internet. Is it configured correctly?


    No I had not configured anything alike, just ip forwarding.

    Tonight, I changed the peers address to 192.168.*8*.39. Now it seems to
    work. E-Mail-Checking via IMAP is fine, yet I have a problem browsing
    www.heise.de. Some html-code is transferred before the connection to
    "The Website" (pocket IE and it's precise error information ...) resets.
    Any idea?

    Thanks,

    Tim

  4. Re: Problem dialing in from pocket pc phone

    Tim Kaufmann writes:
    > James Carlson wrote:
    >
    > > Do you have NAT ("IP masquerade") configured? If not, then there's
    > > just no way that nodes using those RFC 1918 addresses can ever talk to
    > > anything on the Internet. Is it configured correctly?

    >
    > No I had not configured anything alike, just ip forwarding.


    In that case, there must be a NAT somewhere in your network. Those
    addresses cannot be routed on the public Internet.

    > Tonight, I changed the peers address to 192.168.*8*.39. Now it seems
    > to work.


    That seems really suspicious to me ... it likely means that proxy ARP
    was not enabled or working properly on your system.

    > E-Mail-Checking via IMAP is fine, yet I have a problem
    > browsing www.heise.de. Some html-code is transferred before the
    > connection to "The Website" (pocket IE and it's precise error
    > information ...) resets. Any idea?


    The upstream connection is a DSL link, right? That sounds like
    well-known Path MTU Discovery lossage that is caused by PPPoE's weird
    1492 MTU limit. Enabling TCP MSS hacks in your NAT (wherever it is)
    or just lowering the MTU on that client machine should fix this.

    --
    James Carlson, KISS Interop
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

+ Reply to Thread