Gå til innhold

problemer med og PPP og dial up


Anbefalte innlegg

prøver og få til dial up med ppp på laptopen min som kjører Arch Linux. Jeg bruker en Nokia N80 med USB kabel. Jeg har samme oppsett som en kompis og hos han funker det utmerket.

 

fra log fila.. jeg får samma feilen hele tia.

Using interface ppp0
Connect: ppp0 <--> /dev/ttyACM0
PAP authentication succeeded
BSD Compression module registered
PPP Deflate Compression module registered
[B]LCP terminated by peer
Connection terminated.[/B]
Modem hangup
Exit.

 

KPPP gir error 16 som er "modem hangup" slenger med litt mere info i håp om det skal gi et bedre svar.

 

mknod /dev/ppp c 108 0
pppd /dev/ttyACM0

 

her er /etc/ppp/options fila:

Klikk for å se/fjerne innholdet nedenfor

# /etc/ppp/options

#

# Originally created by Jim Knoble <[email protected]>

# Modified for Debian by alvar Bray <[email protected]>

# Modified for PPP Server setup by Christoph Lameter <[email protected]>

# Modified for ArchLinux by Manolis Tzanidakis <[email protected]>

#

# To quickly see what options are active in this file, use this command:

# egrep -v '#|^ *$' /etc/ppp/options

 

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use

# Two Servers can be remotely configured

# ms-dns 192.168.1.1

# ms-dns 192.168.1.2

 

# Specify which WINS Servers the incoming connection Win95 or WinNT should use

# ms-wins 192.168.1.50

# ms-wins 192.168.1.51

 

# Run the executable or shell command specified after pppd has

# terminated the link. This script could, for example, issue commands

# to the modem to cause it to hang up if hardware modem control signals

# were not available.

#disconnect "chat -- \d+++\d\c OK ath0 OK"

 

# async character map -- 32-bit hex; each bit is a character

# that needs to be escaped for pppd to receive it. 0x00000001

# represents '\x01', and 0x80000000 represents '\x1f'.

asyncmap 0

 

# Require the peer to authenticate itself before allowing network

# packets to be sent or received.

# Please do not disable this setting. It is expected to be standard in

# future releases of pppd. Use the call option (see manpage) to disable

# authentication for specific peers.

auth

 

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data

# on the serial port.

crtscts

 

# Use software flow control (i.e. XON/XOFF) to control the flow of data

# on the serial port.

#xonxoff

 

# Specifies that certain characters should be escaped on transmission

# (regardless of whether the peer requests them to be escaped with its

# async control character map). The characters to be escaped are

# specified as a list of hex numbers separated by commas. Note that

# almost any character can be specified for the escape option, unlike

# the asyncmap option which only allows control characters to be

# specified. The characters which may not be escaped are those with hex

# values 0x20 - 0x3f or 0x5e.

#escape 11,13,ff

 

# Don't use the modem control lines.

#local

 

# Specifies that pppd should use a UUCP-style lock on the serial device

# to ensure exclusive access to the device.

lock

 

# Don't show the passwords when logging the contents of PAP packets.

# This is the default.

hide-password

 

# When logging the contents of PAP packets, this option causes pppd to

# show the password string in the log message.

#show-password

 

# Use the modem control lines. On Ultrix, this option implies hardware

# flow control, as for the crtscts option. (This option is not fully

# implemented.)

modem

 

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd

# will ask the peer to send packets of no more than <n> bytes. The

# minimum MRU value is 128. The default MRU value is 1500. A value of

# 296 is recommended for slow links (40 bytes for TCP/IP header + 256

# bytes of data).

#mru 542

 

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"

# notation (e.g. 255.255.255.0).

#netmask 255.255.255.0

 

# Disables the default behaviour when no local IP address is specified,

# which is to determine (if possible) the local IP address from the

# hostname. With this option, the peer will have to supply the local IP

# address during IPCP negotiation (unless it specified explicitly on the

# command line or in an options file).

#noipdefault

 

# Enables the "passive" option in the LCP. With this option, pppd will

# attempt to initiate a connection; if no reply is received from the

# peer, pppd will then just wait passively for a valid LCP packet from

# the peer (instead of exiting, as it does without this option).

#passive

 

# With this option, pppd will not transmit LCP packets to initiate a

# connection until a valid LCP packet is received from the peer (as for

# the "passive" option with old versions of pppd).

#silent

 

# Don't request or allow negotiation of any options for LCP and IPCP

# (use default values).

#-all

 

# Disable Address/Control compression negotiation (use default, i.e.

# address/control field disabled).

#-ac

 

# Disable asyncmap negotiation (use the default asyncmap, i.e. escape

# all control characters).

#-am

 

# Don't fork to become a background process (otherwise pppd will do so

# if a serial device is specified).

#-detach

 

# Disable IP address negotiation (with this option, the remote IP

# address must be specified with an option on the command line or in

# an options file).

#-ip

 

# Disable IPCP negotiation and IP communication. This option should

# only be required if the peer is buggy and gets confused by requests

# from pppd for IPCP negotiation.

#noip

 

# Disable magic number negotiation. With this option, pppd cannot

# detect a looped-back line.

#-mn

 

# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.

# 1500).

#-mru

 

# Disable protocol field compression negotiation (use default, i.e.

# protocol field compression disabled).

#-pc

 

# Require the peer to authenticate itself using PAP.

#+pap

 

# Don't agree to authenticate using PAP.

#-pap

 

# Require the peer to authenticate itself using CHAP [Cryptographic

# Handshake Authentication Protocol] authentication.

#+chap

 

# Don't agree to authenticate using CHAP.

#-chap

 

# Disable negotiation of Van Jacobson style IP header compression (use

# default, i.e. no compression).

#-vj

 

# Increase debugging level (same as -d). If this option is given, pppd

# will log the contents of all control packets sent or received in a

# readable form. The packets are logged through syslog with facility

# daemon and level debug. This information can be directed to a file by

# setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If

# pppd is compiled with extra debugging enabled, it will log messages

# using facility local2 instead of daemon).

#debug

 

# Append the domain name <d> to the local host name for authentication

# purposes. For example, if gethostname() returns the name porsche,

# but the fully qualified domain name is porsche.Quotron.COM, you would

# use the domain option to set the domain name to Quotron.COM.

#domain <d>

 

# Enable debugging code in the kernel-level PPP driver. The argument n

# is a number which is the sum of the following values: 1 to enable

# general debug messages, 2 to request that the contents of received

# packets be printed, and 4 to request that the contents of transmitted

# packets be printed.

#kdebug n

 

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer

# requests a smaller value via MRU negotiation, pppd will request that

# the kernel networking code send data packets of no more than n bytes

# through the PPP network interface.

#mtu <n>

 

# Set the name of the local system for authentication purposes to <n>.

# This is a privileged option. With this option, pppd will use lines in the

# secrets files which have <n> as the second field when looking for a

# secret to use in authenticating the peer. In addition, unless overridden

# with the user option, <n> will be used as the name to send to the peer

# when authenticating the local system to the peer. (Note that pppd does

# not append the domain name to <n>.)

#name <n>

 

# Enforce the use of the hostname as the name of the local system for

# authentication purposes (overrides the name option).

#usehostname

 

# Set the assumed name of the remote system for authentication purposes

# to <n>.

#remotename <n>

 

# Add an entry to this system's ARP [Address Resolution Protocol]

# table with the IP address of the peer and the Ethernet address of this

# system.

proxyarp

 

# Use the system password database for authenticating the peer using

# PAP. Note: mgetty already provides this option. If this is specified

# then dialin from users using a script under Linux to fire up ppp wont work.

# login

 

# If this option is given, pppd will send an LCP echo-request frame to the

# peer every n seconds. Normally the peer should respond to the echo-request

# by sending an echo-reply. This option can be used with the

# lcp-echo-failure option to detect that the peer is no longer connected.

lcp-echo-interval 30

 

# If this option is given, pppd will presume the peer to be dead if n

# LCP echo-requests are sent without receiving a valid LCP echo-reply.

# If this happens, pppd will terminate the connection. Use of this

# option requires a non-zero value for the lcp-echo-interval parameter.

# This option can be used to enable pppd to terminate after the physical

# connection has been broken (e.g., the modem has hung up) in

# situations where no hardware modem control lines are available.

lcp-echo-failure 4

 

# Set the LCP restart interval (retransmission timeout) to <n> seconds

# (default 3).

#lcp-restart <n>

 

# Set the maximum number of LCP terminate-request transmissions to <n>

# (default 3).

#lcp-max-terminate <n>

 

# Set the maximum number of LCP configure-request transmissions to <n>

# (default 10).

#lcp-max-configure <n>

 

# Set the maximum number of LCP configure-NAKs returned before starting

# to send configure-Rejects instead to <n> (default 10).

#lcp-max-failure <n>

 

# Set the IPCP restart interval (retransmission timeout) to <n>

# seconds (default 3).

#ipcp-restart <n>

 

# Set the maximum number of IPCP terminate-request transmissions to <n>

# (default 3).

#ipcp-max-terminate <n>

 

# Set the maximum number of IPCP configure-request transmissions to <n>

# (default 10).

#ipcp-max-configure <n>

 

# Set the maximum number of IPCP configure-NAKs returned before starting

# to send configure-Rejects instead to <n> (default 10).

#ipcp-max-failure <n>

 

# Set the PAP restart interval (retransmission timeout) to <n> seconds

# (default 3).

#pap-restart <n>

 

# Set the maximum number of PAP authenticate-request transmissions to

# <n> (default 10).

#pap-max-authreq <n>

 

# Set the maximum time that pppd will wait for the peer to authenticate

# itself with PAP to <n> seconds (0 means no limit).

#pap-timeout <n>

 

# Set the CHAP restart interval (retransmission timeout for

# challenges) to <n> seconds (default 3).

#chap-restart <n>

 

# Set the maximum number of CHAP challenge transmissions to <n>

# (default 10).

#chap-max-challenge

 

# If this option is given, pppd will rechallenge the peer every <n>

# seconds.

#chap-interval <n>

 

# With this option, pppd will accept the peer's idea of our local IP

# address, even if the local IP address was specified in an option.

#ipcp-accept-local

 

# With this option, pppd will accept the peer's idea of its (remote) IP

# address, even if the remote IP address was specified in an option.

#ipcp-accept-remote

 

# Disable the IPXCP and IPX protocols.

# To let pppd pass IPX packets comment this out --- you'll probably also

# want to install ipxripd, and have the Internal IPX Network option enabled

# in your kernel. /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.

noipx

 

# Exit once a connection has been made and terminated. This is the default,

# unless the `persist' or `demand' option has been specified.

#nopersist

 

# Do not exit after a connection is terminated; instead try to reopen

# the connection.

#persist

 

# Terminate after n consecutive failed connection attempts.

# A value of 0 means no limit. The default value is 10.

#maxfail <n>

 

# Initiate the link only on demand, i.e. when data traffic is present.

# With this option, the remote IP address must be specified by the user on

# the command line or in an options file. Pppd will initially configure

# the interface and enable it for IP traffic without connecting to the peer.

# When traffic is available, pppd will connect to the peer and perform

# negotiation, authentication, etc. When this is completed, pppd will

# commence passing data packets (i.e., IP packets) across the link.

#demand

 

# Specifies that pppd should disconnect if the link is idle for <n> seconds.

# The link is idle when no data packets (i.e. IP packets) are being sent or

# received. Note: it is not advisable to use this option with the persist

# option without the demand option. If the active-filter option is given,

# data packets which are rejected by the specified activity filter also

# count as the link being idle.

#idle <n>

 

# Specifies how many seconds to wait before re-initiating the link after

# it terminates. This option only has any effect if the persist or demand

# option is used. The holdoff period is not applied if the link was

# terminated because it was idle.

#holdoff <n>

 

# Wait for up n milliseconds after the connect script finishes for a valid

# PPP packet from the peer. At the end of this time, or when a valid PPP

# packet is received from the peer, pppd will commence negotiation by

# sending its first LCP packet. The default value is 1000 (1 second).

# This wait period only applies if the connect or pty option is used.

#connect-delay <n>

 

# Packet filtering: for more information, see pppd(8)

# Any packets matching the filter expression will be interpreted as link

# activity, and will cause a "demand" connection to be activated, and reset

# the idle connection timer. (idle option)

# The filter expression is akin to that of tcpdump(1)

#active-filter <filter-expression>

 

# uncomment the line below this if you use PPPoE

#plugin /usr/lib/pppd/plugins/pppoe.so

 

# ---<End of File>---

 

er det noen som kan se noe feil i metode/config?

Lenke til kommentar
Videoannonse
Annonse
jeg har blåtann også ja.. men har ikke fått det til og funke.. Det hadde vert yperlig om du kunne legge ved scriptene dine krigun

9133612[/snapback]

 

OK, here goes:

 

Du må installere dbus, bluez-utils, bluez-libs, bluez-firmware og andre evt. dependencies som pacman sikkert forteller deg om.

 

Stapp inn en USB Bluetooth dings, eller hvis du har det innebygget i PC så trenger du ikke det. Kjør så:

/etc/rc.d/bluetooth start

 

Kan lønne seg å legge dette inn i daemons array på /etc/rc.conf (bluetooth)

 

Nå trenger du å vite to ting:

1: MAC adressen til telefonen din

2: RFCOMM kanalen for Dial Up Networking

 

Finn MAC adresse:

[root@xps ~]# hcitool scanning
Scanning ...
       00:16:20:XX:XX:XX       W800i

 

MAC adressen til min telefon er altså: 00:16:20:XX:XX:XX

 

Finn RFCOMM kanalen for Dial Up Networking:

[root@xps ~]# sdptool browse 00:16:20:XX:XX:XX
Browsing 00:16:20:XX:XX:XX ...
Service Description: Sony Ericsson W800
Service RecHandle: 0x10000
Service Class ID List:
 "PnP Information" (0x1200)

Service Name: Dial-up Networking
Service RecHandle: 0x10001
Service Class ID List:
 "Dialup Networking" (0x1103)
 "Generic Networking" (0x1201)
Protocol Descriptor List:
 "L2CAP" (0x0100)
 "RFCOMM" (0x0003)
   Channel: 1
Profile Descriptor List:
 "Dialup Networking" (0x1103)
   Version: 0x0100

....
....
....

 

Finn Service med navn "Dial-up Networking" eller lignende, og finn følgende:

Protocol Descriptor List:
 "L2CAP" (0x0100)
 "RFCOMM" (0x0003)
   Channel: 1

 

Altså, min telefon har RFCOMM kanal 1 for Dial up networking.

 

Oppdater så /etc/bluetooth/rfcomm.conf med dine egne verdier:

#
# RFCOMM configuration file.
#

rfcomm0 {
#       # Automatically bind the device at startup
       bind yes;
#
#       # Bluetooth address of the device
       device 00:16:20:XX:XX:XX;
#
#       # RFCOMM channel for the connection
       channel 1;
}

 

 

Min /etc/bluetooth/hcid.conf ser slik ut:

Klikk for å se/fjerne innholdet nedenfor

#
# HCI daemon configuration file.
#

# HCId options
options {
       # Automatically initialize new devices
       autoinit yes;

       # Security Manager mode
       #   none - Security manager disabled
       #   auto - Use local PIN for incoming connections
       #   user - Always ask user for a PIN
       #
       security auto;

       # Pairing mode
       #   none  - Pairing disabled
       #   multi - Allow pairing with already paired devices
       #   once  - Pair once and deny successive attempts
       pairing multi;

       # Default PIN code for incoming connections
       passkey "1111";
}

# Default settings for HCI devices
device {
       # Local device name
       #   %d - device id
       #   %h - host name
       name "XPS M1770";

       # Local device class
       class 0x3e0100;

       # Default packet type
       #pkt_type DH1,DM1,HV1;

       # Inquiry and Page scan
       iscan enable; pscan enable;

       # Default link mode
       #   none   - no specific policy
       #   accept - always accept incoming connections
       #   master - become master on incoming connections,
       #            deny role switch on outgoing connections
       lm accept;

       # Default link policy
       #   none    - no specific policy
       #   rswitch - allow role switch
       #   hold    - allow hold mode
       #   sniff   - allow sniff mode
       #   park    - allow park mode
       lp rswitch,hold,sniff,park;
}

 

Kjør /etc/rc.d/bluetooth restart for å aktivere endringene.

 

 

Gå inn i /etc/ppp mappen, og opprett følgende filer, hvis de ikke allerede eksisterer:

/etc/ppp/pap-secrets

/etc/ppp/chap-secrets

 

Jeg har det samme i begge filene, men er ikke sikker på om de trengs i det hele tatt. Har Telenor, så jeg har skrevet mitt telefonnummer her:

Klikk for å se/fjerne innholdet nedenfor

# Secrets for authentication using PAP
# client        server  secret                  IP addresses
99XXXXXX * 99XXXXXX *

 

/etc/ppp/ip-up (Denne er nødvendig for meg iallefall, da dns-infoen ikke ble oppdatert i /etc/resolv.conf)

Klikk for å se/fjerne innholdet nedenfor

#!/bin/sh
#
# This script is run by pppd when there's a successful ppp connection.
#

echo "created by pppd" > /etc/resolv.conf
echo "nameserver ${DNS1}" >> /etc/resolv.conf
echo "nameserver ${DNS2}" >> /etc/resolv.conf
chmod go+r /etc/resolv.conf

route del default
route add default gw ${IPREMOTE}

 

Opprett mappen /etc/ppp/peers hvis den ikke allerede eksisterer.

 

Opprett konfigurasjonsfil /etc/ppp/peers/gprs, og oppdater med ditt telefonnummer helt nederst:

Klikk for å se/fjerne innholdet nedenfor

#!/bin/sh
# Description:
# Serial cable, IrDA, Bluetooth and USB pppd options for GPRS phones.
# See 'man pppd' for detailed option descriptions.

# Most GPRS phones don't reply to LCP echo's
lcp-echo-failure 0
lcp-echo-interval 0

# Keep pppd attached to the terminal:
# Comment this to get daemon mode pppd
nodetach

# Debug info from pppd:
# Comment this off, if you don't need more info
debug

# Show password in debug messages
show-password

# Connect script:
# scripts to initialize the GPRS modem and start the connection,
connect /etc/ppp/peers/gprs-connect-chat

# Disconnect script:
# AT commands used to 'hangup' the GPRS connection.
disconnect /etc/ppp/peers/gprs-disconnect-chat

# Serial device to which the GPRS phone is connected:
# /dev/ttyS0 for serial port (COM1 in Windows),
# /dev/ircomm0 for IrDA,
# /dev/ttyUB0 for Bluetooth (Bluez with rfcomm running) and
# /dev/ttyUSB0 #for USB
#/dev/ttyS0     # serial port one
#/dev/ttyS1     # serial port two
#/dev/ircomm0   # IrDA serial port one
/dev/rfcomm0    # Bluetooth serial port one
#/dev/ttyUSB0   # USB serial device, for example Orange SPV

# Serial port line speed
#460800
115200  # fast enough
#57600  # perhaps usefull with IrDA as some phones don't like
       # speeds higher than this

# Hardware flow control:
# Use hardware flow control with cable, Bluetooth and USB but not with IrDA.
crtscts  # serial cable, Bluetooth and USB, on some occations with IrDA too
#nocrtscts # IrDA

# Ignore carrier detect signal from the modem:
local

# pppd must not propose any IP address to the peer!
noipdefault

# Accept peers idea of our local address
ipcp-accept-local

# Add the ppp interface as default route to the IP routing table
defaultroute

# DNS servers from the phone:
# some phones support this, some don't.
usepeerdns

# ppp compression:
# ppp compression may be used between the phone and the pppd, but the
# serial connection is usually not the bottleneck in GPRS, so the
# compression is useless (and with some phones need to disabled before
# the LCP negotiations succeed).
novj
nobsdcomp
novjccomp
nopcomp
noaccomp

# The phone is not required to authenticate:
noauth

# Username and password:
# If username and password are required by the APN, put here the username
# and put the username-password combination to the secrets file:
# /etc/ppp/pap-secrets for PAP and /etc/ppp/chap-secrets for CHAP
# authentication. See pppd man pages for details.
# Example, Airtel operator pap-secrets:
# user "mobile number"
user "99XXXXXX"

 

Har ikke eksperimentert for mye med diverse settings her, men du kan jo prøve. Funker iallefall.

 

Opprett filen /etc/ppp/peers/gprs-connect-chat (Ren CTRL-C -> CTRL-V):

Klikk for å se/fjerne innholdet nedenfor

#!/bin/sh

exec chat                                               \
       TIMEOUT         5                               \
       ECHO            ON                              \
       ABORT           '\nBUSY\r'                      \
       ABORT           '\nERROR\r'                     \
       ABORT           '\nNO ANSWER\r'                 \
       ABORT           '\nNO CARRIER\r'                \
       ABORT           '\nNO DIALTONE\r'               \
       ABORT           '\nRINGING\r\n\r\nRINGING\r'    \
       ''              \rAT                            \
       TIMEOUT         12                              \
       SAY             "Press CTRL-C to close the connection at any stage!"    \
       SAY             "\ndefining PDP context...\n"   \
       OK              ATH                             \
       OK              ATE1                            \
       OK              'AT+CGDCONT=1,"IP","internet","",0,0'   \
       OK              ATD*99#                         \
       TIMEOUT         22                              \
       SAY             "\nwaiting for connect...\n"    \
       CONNECT         ""                              \
       SAY             "\nConnected." \
       SAY             "\nIf the following ppp negotiations fail,\n"   \
       SAY             "try restarting the phone.\n"

 

Opprett filen /etc/ppp/peers/gprs-disconnect-chat (Ren CTRL-C -> CTRL-V):

Klikk for å se/fjerne innholdet nedenfor

#!/bin/sh

exec /usr/sbin/chat -V -s -S    \
ABORT           "BUSY"          \
ABORT           "ERROR"         \
ABORT           "NO DIALTONE"   \
SAY             "\nSending break to the modem\n"        \
""              "\K"            \
""              "\K"            \
""              "\K"            \
""              "+++ATH"        \
""              "+++ATH"        \
""              "+++ATH"        \
SAY             "\nPDP context detached\n"

 

 

Så, er det bare å kjøre følgende script som root (kall den hva du vil), og håpe på det beste:

#!/bin/bash
#

rfcomm bind all
mknod /dev/ppp c 108 0
pppd call gprs

 

 

Som sagt, dette funker fint for meg med en W800i og Telenor Mobil.v

 

 

PS: Samme script fungerer også med HUAWEI 3G USB kort, hvis man endrer device i /etc/ppp/peers/gprs (/dev/ttyUSB0)

Endret av krigun
Lenke til kommentar
Bookmarked!

 

Personlig har jeg brukt denne tidligere:

http://www.howtoforge.com/linux_internet_a...tooth_gsm_phone

 

Sammen med Telenor sine GPRS-oppsett-sider samt litt inteligent lesing av configfilene (det er f.eks. mulig å få en dialog som ber om passordet i dag...)

9145889[/snapback]

 

Godt å høre at det er nyttig for noen :) Har prøvd flere modem scripts som jeg har funnet på nett, men de som jeg postet var eneste jeg fikk til å fungere knirkefritt med min telefon over bluetooth og et 3G modem over USB.

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
×
×
  • Opprett ny...