|
|||||||
|
|
|
 |
|
|
Strumenti |
17-06-2005, 10:39
|
#1 |
|
Senior Member
Iscritto dal: Jan 2005
Città: Roma
Messaggi: 4870
|
[urgente] modem isdn
scusate per l'urgente ma è una settimana che ci sto impazzendo e devo consegnare il computer!
la distro è ubuntu 5.04 Hoary il modem è un Hamlet con chipset hfc-2bso ho installato isdnutils faccio caricare il modulo inserendo in /etc/modules/ la seguente riga: modprobe hisax type=35 protocol=2 ho creato uno script di caricamento di ippp0: /etc/init.d/isdnup che è eseguibile Codice:
export PATH=/sbin:/usr/sbin:/bin:/usr/bin isdnctrl addif ippp0 isdnctrl addphone ippp0 out 7027020000 isdnctrl secure ippp0 on isdnctrl huptimeout ippp0 300 isdnctrl l2_prot ippp0 hdlc isdnctrl l3_prot ippp0 trans isdnctrl encap ippp0 syncppp isdnctrl pppbind ippp0 0 hisaxctrl HiSax 1 4 isdnlog /dev/isdnctrl0 -D echo 1 > /proc/sys/net/ipv4/ip_dynaddr ifconfig ippp0 -arp -bradcast ipppd file /etc/ppp/ioptions.ippp0 isdnctrl dialmode ippp0 auto sleep 2 route add default ippp0 Codice:
# Options file for ipppd. # ipppd will not read /etc/ppp/options or /etc/ppp/ioptions or any other # config file. Everything has to be in here. # "peer" is the name for our syncppp partner. # STANDARD OPTIONS #debug # enable debugging #kdebug X # set kernel debugging level to X #nodetach # (no) fork to the background #callback X # ask for callback (parameter X ?) #lock # create a lock file for device #domain X # add domain X to a given hostname #pidfile X # save pid in file X #call X # take options from privileges file (???) #idle X # idle time limit (seconds) #holdoff X # holdoff time limit (seconds) #maxconnect X # set maximum connection time (in seconds ?) +mp # enable multi line ppp #+pwlog # log password (WARNING: possible security hole) #nomagic # magic number negotiation # ppp handshake : tuning #silent # don't even try to initiate the connection #passive # wait for the peer to initiate the connection #lcp-echo-failure X # consecutive echo failures #lcp-echo-interval X # time for lcp echo events lcp-restart 1 # Set timeout for LCP #lcp-max-terminate X # Set max #xmits for term-reqs #lcp-max-configure X # Set max #xmits for conf-reqs #lcp-max-failure X # Set max #conf-naks for LCP # AUTHENTICATION name [email protected] #user X # set name for auth with peer; default is value for name #usehostname # use hostname for auth #remotename X # set remote name for auth remotename 7027020000 noauth # (dont) require peer (the other) to auth #require-pap # allow only pap authentication (dialin only) #require-chap # allow only chap authentication (dialin only) #login # use system password database for pap #papcrypt # pap passwords are encrypted # AUTHENTICATION TUNING #pap-restart X # Set retransmit timeout for PAP #pap-max-authreq X # Set max #xmits for auth-reqs #pap-timeout X # Set time limit for peer PAP auth. #chap-restart X # Set timeout for CHAP #chap-max-challenge X # Set max #xmits for challenge #chap-interval X # Set interval for rechallenge # COMPRESSION #noaccomp # address compression on/off #nopcomp # protocol field compression on/off #novj # van jacobsen compression on/off #novjccomp # van jacobsen connection-ID compression on/off #vj-max-slots X # tune maximum vj header slots #nobsdcomp # bsd compression on/off #nodeflate # deflate compression on/off #nopredictor1 # predictor1 compression in/off noccp # compression negotation on/off nolzs # LZS compression off (not yet supported fully) # IP NETWORKING #noip # (do not) disable ip transfer #X:Y # (do not) set local ip to X, remote ip to Y noipdefault # do not use name for default ip addr #useifip # (do) use ip addresses from interface #usefirstip # (do) use first ip from auth file for remote netmask 255.255.255.255 # do set netmask, 255.255.255.255 for pointopoint #defaultroute # (do not) set default route (for Debian config, don't uncomment) nohostroute # do not set host route #proxyarp # (do not) set an proxy arp entry mru 1524 # do set maximum size of receive units to X #default-mru # (do not) enable mru negotation mtu 1500 # do set max size of transmit units (1500 is OK) #useifmtu # (do not) use mtu from interface #ipparam X # (do not) set ip parameters in script X #ms-dns X # (do not) set dns addr for the peers use (dialin only) #ms-wins X # (do not) wins address for the peers use (dialin only) #ms-get-dns # (do not) accept peers suggestion of dns addr (dialout) #set_userip # (do not) define valid ip addrs in /etc/ppp/useriptab usepeerdns # Get Name Server address from remote #ipcp-restart X # Set timeout for IPCP #ipcp-max-terminate X # Set max #xmits for term-reqs #ipcp-max-configure X # Set max #xmits for conf-reqs #ipcp-max-failure X # Set max #conf-naks for IPCP ipcp-accept-local # Accept peer's address for us ipcp-accept-remote # Accept peer's address for it # IPX NETWORKING #noipx # en/disable ipx #ipx-network X # IPX network number #ipxcp-accept-network # Accept peer netowrk #ipx-node X # IPX node number #ipxcp-accept-local # Accept our address #ipxcp-accept-remote # Accept peer's address #ipx-routing X # IPX routing proto number #ipx-router-name X # IPX router name #ipxcp-restart X # Set timeout for IPXCP #ipxcp-max-terminate X # max #xmits for term-reqs #ipxcp-max-configure X # max #xmits for conf-reqs #ipxcp-max-failure X # max #conf-naks for IPXCP Codice:
#!/bin/sh
# Instructions: read the comments for each command, and if necessary, edit
# the command (e.g. replace EAZ with your real EAZ or MSN). Look for lines
# marked with XXX_, which is probably all you need to change.
# If the command is commented out, remove the leading '#' to enable it if
# the command is needed.
#
# After you have configured this file, remove the "Warning!" line above to
# enable this file.
# If using dynamic IP addresses:
# Check out the /etc/ppp/ip-up.d/isdnutils and /etc/ppp/ip-down.d/isdnutils
# scripts, to ensure that any routing is done correctly there (the
# ip-up.d/isdnutils script is run after a syncPPP link is established, and the
# ip-down.d/isdnutils script is run after the link goes down).
# You need to have the ppp package installed for those scripts to work.
# set -e # exit on _any_ error
# Get the device name
device=`basename $0`; device=${device#*.}
# this used to be simple, but POSIX is a bit more limited
# ippp0+8 -> devtype=ippp
devtype=${device%%[0-9]*}
# ippp0+8 -> devnums=0+8
devnums=${device##$devtype}
# ippp0+8 -> device=ippp8
device=$devtype${devnums#[0-9]*+}
dowhat="$1"
masterslave="$2"
case "x$masterslave" in
xmaster) master=true; slave=false;;
xslave) master=false; slave=true; masterdevice="$3";;
x) master=false; slave=false;;
*) echo "Error, $0 called with unknown 2nd arg '$masterslave', aborting!"
exit 1;;
esac
# The (dummy) IP addresses
#
# Use 192.25.206.10 for LOCALIP and 10.0.0.2 for REMOTEIP if you have
# dynamic IP addresses; with static address fill in the real values!
LOCALIP=192.25.206.10 # XXX_
REMOTEIP=10.0.0.2 # XXX_
# Phone numbers (without the leading zero)
#
# REMOTEMSN may be a list of numbers to dial, separated by a space.
# If you do that, DO put quotes around the whole value! Like:
# REMOTEMSN='221345788 221345789'
#
# The REMOTEMSN must be the areacode (without the leading zero) + phonenumber!
#
# Example: areacode: 0221 phonenumber: 345789
# => REMOTEMSN='221345789'
#
# EXPLANATION:
# A zero is added below when it is used as the outgoing number;
# when it it used as the incoming number, it must be without a leading zero
# (which is why you must leave that leading zero out below).
# The local number must also be given without the leading zero!
#
# EXCEPTION:
# In countries where there are NO areacodes, this leading zero must NOT be
# added. In that case, change the value of LEADINGZERO below to ''
# LEADINGZERO could conceivably need to be something else in certian
# situations, so it is configurable.
LOCALMSN="*06620xxxx"
REMOTEMSN="7027020000"
LEADINGZERO='' # XXX_ use LEADINGZERO='' if you have no areacodes.
# DIALMODE:
# New with kernel 2.0.36 is the `dialmode' setting.
# dialmode=auto is compatible with the old behaviour (dial-on-demand enabled).
# Read the isdnctrl manpage for more info.
# Change the value below if you want a different setting when the interface is
# started.
# For slave devices (channel bundling) dialmode _must_ be auto,
# so for slave devices this setting is ignored.
DIALMODE=auto # XXX_ other values can be 'on' and 'off'
# Encapsulation (default is syncppp for ipppX devices, rawip for isdnX devices)
# Change the next four lines if you need some other value.
if expr ${device} : ippp > /dev/null
then ENCAP=syncppp
else ENCAP=rawip
fi
# Configuration (start)
case "$dowhat" in
start)
# XXX_
# If running kernel 2.0.31 or higher, enable the IP dynamic hack
# (if needed). See linux/Documentation/networking/ip_dynaddr.txt .
# Default is: enabled. If you have static IP numbers, you can remove
# the next line.
[ -f /proc/sys/net/ipv4/ip_dynaddr ] && echo 5 > /proc/sys/net/ipv4/ip_dynaddr
# First you need to create the interface
if $slave
then isdnctrl addslave ${masterdevice} ${device}
else isdnctrl addif ${device}
fi
# eaz name num
# Set the EAZ (German 1TR6 protocol) or MSN (Euro-ISDN E-DSS1) for
# interface "name" to "num". For an EAZ this is only one digit, for a
# MSN "num" is the whole MSN.
# In the Netherlands this includes the areacode, but not the leading 0.
# (other countries?)
isdnctrl eaz ${device} "$LOCALMSN"
# addphone name out num
# Set the phone number(s) of the remote site for the IP-interface
# "name". More than one number can be set by calling isdnctrl addphone
# repeatedly. If more than one number is set these will be tried one
# after another. When using an german SPV-type connection, with a
# ICN-card, the number has to be preceeded by a capital S.
# This is the "normal" number.
if [ ! -z "$REMOTEMSN" ]; then
for MSN in $REMOTEMSN; do
isdnctrl addphone ${device} out "$LEADINGZERO$MSN"
done
fi
# addphone name in num
# Set the phone number(s) that the IP-interface "name" is supposed to
# accept for incoming calls. If no number is given, incoming calls are
# disabled. More than one number can be set by calling isdnctrl addphone
# repeatedly. Also wildcards can be used (see below).
# In the Netherlands (and elsewhere?),
# this is with areacode but without leading 0
#if [ ! -z "$REMOTEMSN" ]; then
# for MSN in $REMOTEMSN; do
# isdnctrl addphone ${device} in $MSN
# done
#fi
# secure name on|off
# Turns on or off the security feature for interface "name". If set to
# on, incoming calls will only be accepted if the calling number has
# been added to the access list with isdnctrl addphone name in.
isdnctrl secure ${device} on
# huptimeout name seconds
# Set the hangup timeout for interface "name" to "seconds". If there
# is inactivity (i.e. no traffic on the interface) for the given time
# the driver automatically shuts down the connection.
# Default is 60 seconds
isdnctrl huptimeout ${device} 60 # XXX_
# dialmax name num
# Set the number of dial atempts for interface "name" to "num". If
# dialing, each phonenumber is tried this many times before giving up.
#isdnctrl dialmax ${device} NUM
# ihup name on|off
# Turn on or off the hangup timeout for incoming calls on interface name
#isdnctrl ihup ${device} on
# encap name encapname
# Set the encapsulation mode for interface "name". Possible modes for
# encapname are: rawip ip cisco-h ethernet syncppp uihdlc
# (most people use rawip, syncppp or cisco-h; syncppp is normal for
# ISP's, rawip is normal for semi-fixed linux-linux connections)
isdnctrl encap ${device} $ENCAP
# l2_prot name protocol
# Set the layer-2 protocol for interface "name". Possible values for
# "protocol" are x75i, x75ui, x75bui and hdlc
# (most people use hdlc)
isdnctrl l2_prot ${device} hdlc
# l3_prot name protocol
# Set the layer-3 protocol for interface "name". At the moment only
# trans is supported. If protocol is omitted the current setting is
# printed.
isdnctrl l3_prot ${device} trans
# verbose num
# Set verbosity level to <num>.
# (2 shows the first package of every connection, that is very useful.)
# WARNING: this is a global parameter, that affects all isdn devices!
isdnctrl verbose 2
# CHARGEHUP FUNCTION
# chargehup name on|off
# Turn on or off hangup before next charge info for interface name. This
# can only be used if the ISDN provider transmits charge info during and
# after the connection. If set to on, the driver will close the
# connection just before the next charge info will be received if the
# interface is inactive.
#isdnctrl chargehup ${device} on
# chargeint name seconds
# When "seconds" are given, the charge interval for the given interface
# is set. This may be of use on ISDN lines with no chargeinfo or no
# online chargeinfo. The connection will only be closed 2 seconds before
# the end of the next charge interval and only, if huptime out seconds
# of inactivity have been reached. If ihup is on, also incomming
# connections are closed by this mechanism.
#isdnctrl chargeint ${device} NUM
# CALLBACK FUNCTION
# callback name off|in|out
# Selects callback mode for interface "name". If call-back mode is in,
# then after getting an incoming call, a callback is triggered. If
# callback mode is out, then this system does the initial call, then
# waiting for callback of the remote machine.
#isdnctrl callback ${device} MODE
# cbdelay name seconds
# Set the callback delay for interface "name" to "seconds". If callback
# mode for this interface is in, dialing is delayed the given time. If
# the callback mode is out, after dialing out and waiting the given
# time, a hangup is issued to free the line for the incoming callback
# from the remote machine. This hangup-after-dial is disabled by setting
# cbdelay to 0.
#isdnctrl cbdelay ${device} SECONDS
# cbhup name on|off
# Turns on or off Hangup (Reject) for interface "name" before starting
# Callback.
#isdnctrl cbhup ${device} MODE
# OTHER OPTIONS
# There are other options not used by most people. You can insert these
# options here.
# See also : isdnctrl(8), isdnctrl help text
# pppbind is needed when using one ipppd per ippp interface
# (like Debian does)
bindnum=`expr $device : 'ippp\(.*\)'` || true
if [ ! -z "$bindnum" ]; then
isdnctrl pppbind ${device} $bindnum
fi
# NETWORK SETUP
# Network device setup as usual (not applicable to slave devices!)
# See also : ifconfig(8) route(8) or any book about unix networking.
if ! $slave; then
ifconfig ${device} $LOCALIP pointopoint $REMOTEIP netmask 255.255.255.255
set +e # ignore errors from here on
route del -host $REMOTEIP ${device} 2>/dev/null
route add -host $REMOTEIP ${device}
# setting default route here is only useful if this is your only
# outside connection... The default is ippp0 for the default route.
# NOTE: default route for ippp0 is also set in /etc/ppp/ip-up.d/00-ipppd
# and /etc/ppp/ip-down.d/99-ipppd ! So if you don't want the
# default route over ippp0, edit those scripts as well.
# Another solution is not to use ippp0 at all; this is only done
# for ippp0 so by skipping that (and starting with ippp1 for
# example) you don't have to edit anything to avoid changing the
# default route!
if [ "$bindnum" = 0 ]; then
route del default 2>/dev/null
route add default netmask 0 ${device}
fi
# FIREWALL RULES XXX_
# Explicitly list what's allowed, and then deny the rest.
# I'm assuming kernel 2.2.x here, hence ipchains
# instead of ipfwadm or iptables. Note also that this is pretty
# simple-minded, and offers only rudimentary protection.
#
# The firewall rules below will only work here if using static IP
# addresses!!! For dynamic addresses the rules should be added in
# /etc/ppp/ip-up.d/00-isdnutils and deleted in
# /etc/ppp/ip-down.d/99-isdnutils .
# Also note you usually only want a setup as below for the interface
# facing the internet, not if you're using the interface to connect a
# local subnet (unless you're using masquerading).
# Also be sure to check the config to make sure it fits what you want.
#
# ipchains -A input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} 1000:
# ipchains -A input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} ssh
# ipchains -A input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} smtp
# ipchains -A input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} ident
# ipchains -A input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} ftp
# ipchains -A input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} http
# ipchains -A input -j ACCEPT -i ${device} -p UDP -d ${LOCALIP} 1024:
# ipchains -A input -j ACCEPT -i ${device} -p ICMP -d ${LOCALIP}
# ipchains -A input -j DENY -i ${device}
# If you don't have masquerading set up yet, try the following
# (I recommend the ipmasq package).
# Replace 192.168.1 with the network number you use on the hosts
# that will use masquerading.
# ipchains -I forward -j MASQ -s 192.168.1.0/24
fi # not slave
# ignore errors in case of older kernel
if $slave
then isdnctrl dialmode $device auto >/dev/null 2>&1
else isdnctrl dialmode $device $DIALMODE >/dev/null 2>&1
fi
;;
# Delete the interface
stop)
set +e # ignore errors from here on
isdnctrl dialmode $device off >/dev/null 2>&1
if ! $slave; then
# FIREWALL RULES XXX_
# Undo the things done above.
#
# ipchains -D input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} 1000:
# ipchains -D input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} ssh
# ipchains -D input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} smtp
# ipchains -D input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} ident
# ipchains -D input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} ftp
# ipchains -D input -j ACCEPT -i ${device} -p TCP -d ${LOCALIP} http
# ipchains -D input -j ACCEPT -i ${device} -p UDP -d ${LOCALIP} 1024:
# ipchains -D input -j ACCEPT -i ${device} -p ICMP -d ${LOCALIP}
# ipchains -D input -j DENY -i ${device}
# If you don't have masquerading set up yet, try the following.
# Replace 192.168.1 with the network number you use on the hosts
# that will use masquerading.
# ipchains -D forward -j MASQ -s 192.168.1.0/24
# Commands to undo the network stuff
route del $REMOTEIP $device 2> /dev/null
# only delete default route if set above!
# The default is to use ippp0 for your default route.
bindnum=`expr $device : 'ippp\(.*\)'`
if [ "$bindnum" = 0 ]; then
route del default netmask 0 2>/dev/null
fi
ifconfig $device down 2> /dev/null
isdnctrl delif $device 2> /dev/null
# If this was the master device,
# the delif will also have removed the slaves.
fi
;;
# the rest is generic, don't touch
*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac
exit 0
# vim:set sw=4 si:
Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory /dev/isdnctrl: No such file or directory ippp0: ERROR while getting interface flags: No such device -bradcast: Host name lookup failure ifconfig: `--help' gives usage information. In file /etc/ppp/ioptions.ippp0: unrecognized command /dev/ippp0 Can't open /dev/isdninfo or /dev/isdn/isdninfo: No such file or directory Sono disperato, secondo me non mi carica il modulo del kernel e quindi tutto il resto non funziona...vi prego datemi una mano.... 
|
|
|
|
17-06-2005, 15:01
|
#2 |
|
Senior Member
Iscritto dal: Jan 2005
Città: Roma
Messaggi: 4870
|
Nel frattempo che voi ci pensate...io ho rimediato un'altro modem un modem su seriale ASUSCOM ISDNLink TA, ho installato kubuntu su un'altra macchina... dove ho attaccato l'auscom, KPPP e wvdial che mi vedono questo modem perfettamente, quando faccio conneti con KPPP, mi rimane fermi su ITIALIZING HARDWARE....
L'unica distro con cui sono riuscito a far partire il tutto è knoppix...che però mi da un sacco di problema con samba, che non ne vuole sapere di partire, quando la installo su HD transformadola in KANOPIX... CONSIDERATE CHE SONO 30 ORE CHE NON DORMO PER COMBATTERE CON QUESTO DIAVOLO DI LINEA ISDN...per favore qualcuno mi da una mano....vi prego... Devo fare una macchina che faccia da router con dial on demand su una linea ISDN e gestisca anche un dominio con macchine WIN XP SP2...e vorrei andare a casa a dormire..... aiuto 
|
|
|
|
|
17-06-2005, 15:13
|
#3 |
|
Senior Member
Iscritto dal: Jan 2005
Città: Roma
Messaggi: 4870
|
Scusate se insisto...
è possibile installare il tool "RedHat ISDN config" che è presente in Knoppix che è l'unica che riuscita a farmi vedere il modem (l'HFC) attivandolo su k/ubuntu? essndo entrambi debian based, magari non ci sono molti problemi... |
|
|
|
|
17-06-2005, 16:58
|
#4 |
|
Senior Member
Iscritto dal: Jan 2005
Città: Roma
Messaggi: 4870
|
io vado avanti nelle prove....
mi sto impegnando tutto per tutto sull'asus ISDNLink. se wvdialconf pippo, questo è il risultato: Codice:
ttyS0<*1>: ATQ0 V1 E1 -- OK ttyS0<*1>: ATQ0 V1 E1 Z -- ERROR ttyS0<*1>: ATQ0 V1 E1 S0=0 -- OK ttyS0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyS0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyS0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyS0<*1>: Modem Identifier: ATI -- ISDN TA S/T-Interface Version: 1.26.1 ttyS0<*1>: ATI5 -- ISDN TA;ASU2001 ttyS0<*1>: Speed 4800: AT -- OK ttyS0<*1>: Speed 9600: AT -- OK ttyS0<*1>: Speed 19200: AT -- OK ttyS0<*1>: Speed 38400: AT -- OK ttyS0<*1>: Speed 57600: AT -- OK ttyS0<*1>: Speed 115200: AT -- OK ttyS0<*1>: Max speed is 115200; that should be safe. ttyS0<*1>: ATB40 -- OK ttyS1<*1>: ATB40 -- failed with 2400 baud, next try: 9600 baud ttyS1<*1>: ATB40 -- failed with 9600 baud, next try: 115200 baud ttyS1<*1>: ATB40 -- and failed too at 115200, giving up. Port Scan<*1>: S2 S3 S4 S5 S6 S7 S8 S9 Port Scan<*1>: S10 S11 S12 S13 S14 S15 S16 S17 Port Scan<*1>: S18 S19 S20 S21 S22 S23 S24 S25 Port Scan<*1>: S26 S27 S28 S29 S30 S31 S32 S33 Port Scan<*1>: S34 S35 S36 S37 S38 S39 S40 S41 Port Scan<*1>: S42 S43 S44 S45 S46 S47 S48 S49 Port Scan<*1>: S50 S51 S52 S53 Codice:
[Dialer Defaults] Modem = /dev/ttyS0 Baud = 115200 Init1 = AT&F Init2 = ATB40 ISDN = 0 Modem Name = ASUSCOM ISDNLink TA Modem Type = ISDN Terminal Adapter Phone = 7027020000 Username = Miouser Password = miapasswd ho provato prima a levare ATB40 e poi a levare AT&F rimettendo ATB40 e questi sono i risultati: Codice:
root@ubuntu:/home/server # wvdial
--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: AT&F
AT&F
OK
--> Modem initialized.
--> Sending: ATDT7027020000
--> Waiting for carrier.
ATDT7027020000
CONNECT 64000/HDLC
--> Carrier detected. Waiting for prompt.
[7f][03]@![01]Z [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01][ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]\ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]] [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]^ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]_ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]` [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]a [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]b [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]c [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP
--> Connected, but carrier signal lost! Retrying...
--> Sending: ATDT7027020000
--> Waiting for carrier.
NO CARRIER
Q[11]Q]AI]AIAAAA5[7f]
--> No Carrier! Trying again.
--> Sending: ATDT7027020000
--> Waiting for carrier.
ATDT7027020000
Codice:
root@ubuntu:/home/server # wvdial
--> WvDial: Internet dialer version 1.54.0
--> Initializing modem.
--> Sending: AT&F
AT&F
OK
--> Modem initialized.
--> Sending: ATDT7027020000
--> Waiting for carrier.
ATDT7027020000
CONNECT 64000/HDLC
--> Carrier detected. Waiting for prompt.
[7f][03]@![01]Z [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01][ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]\ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]] [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]^ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]_ [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]` [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]a [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]b [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP[7f][03]@![01]c [1d][03][04]@#[05][06]+{{[12][11][04][05]t[13][0b][01]ROMA-MPP
--> Connected, but carrier signal lost! Retrying...
--> Sending: ATDT7027020000
--> Waiting for carrier.
NO CARRIER
Q[11]Q]AI]AIAAAA5[7f]
--> No Carrier! Trying again.
--> Sending: ATDT7027020000
--> Waiting for carrier.
ATDT7027020000
|
|
|
|
|
17-06-2005, 19:52
|
#5 | |
|
Senior Member
Iscritto dal: Jan 2005
Città: Roma
Messaggi: 4870
|
up per me...
ragazzi è molto importante penso di aver raggiunto le 36 ore davanti ad un computer a smadonnare!!!! secondo voi posso entrare nei guinness dei primati??? Quote:
 p.s. non vi accavallate con le risposte... |
|
|
|
|
|
17-06-2005, 20:04
|
#6 |
|
Senior Member
Iscritto dal: Jun 2002
Messaggi: 1393
|
ti rispondo io
 sono un figussiano incallitonn glie la farai mai mi sembri esperto, io son 2 anni ke provo ad usare linux e ho sempre avuto lo stesso blocco, il modem isdn asuscom ta pci, nn riuscendo a connettermi ad internet ho rinunciato. vabè, spero ke tu ce la faccia, ma nn son molto fiducioso su questo. ciao |
|
|
|
|
17-06-2005, 21:06
|
#7 | |
|
Member
Iscritto dal: Oct 2004
Messaggi: 253
|
Quote:
..... io il ta asuscom pci con chipset winbond 6692 ..... con Suse 9.2 va che è una meravigli !!!!! con Kinternet lo vede e lo configura alla perfezione...... ...con le altre distribuzioni ...... 000000000000000000 assoluto !!!!!! Ciao |
|
|
|
|
|
18-06-2005, 11:00
|
#8 |
|
Senior Member
Iscritto dal: Jan 2005
Città: Roma
Messaggi: 4870
|
Forse mi sono spiegato male...l'AsusCom è seriale è il TA 200, comunque a parte questo, confermo che SUSE 9.3 lo legge... ed anche Knoppix... e funziona benissimo.
Non uso queste due distribuzioni perché mi danno problemi con samba.. stranamente e non riesco a capire perché! Al contrario Ubuntu/Kubuntu Samba va che è una scheggia ma non funziona il modem.... O risolvo Samba su uno o Il modem sull'altro...la cosa strana è che samba e su Suse non mi ha mai dato problemi in vita mia E' possibile che sia l'hardware che da problemi?? Oppure che siano i client win Xp SP2?? Non so dove sbattere la testa
|
|
|
|
|
18-06-2005, 11:27
|
#9 | |
|
Senior Member
Iscritto dal: Jun 2002
Messaggi: 1393
|
Quote:
, però ricordo che ho provato suse9.1 mi sembra e nn son riuscito a farlo funzionare, purtroppo io nn ho l'adsl e nn posso stare giorni per scaricarmi una nuova distribuzione al mese o forse ogni settimana e qui9ndi posso fare per ora solo con quello ke ho, cioè suse 9.1.l'isdn mi sembra si chiami ta280 pci, lo vendono a 40€ circa se nn ricordo male, dovrebbe esserci solo quello pci. mi diresti i passaggi da fare per configurarlo? io ricordo che aveva problemi nel caricamento del modulo e me lo segnalava durante l'avvio del SO dicendo caricamento moduli isdn failed ecc. la scheda la vedeva dopo le varie configurazioni ma nn si connetteva. |
|
|
|
|
|
18-06-2005, 15:40
|
#10 | |
|
Member
Iscritto dal: Oct 2004
Messaggi: 253
|
Quote:
... praticamente .. ... usa yast con la suse 9.2 .... sotto modem ..... mi vede il mio modello ...... selezioni configura ... selezioni other nei provider ....ne crei uno con il nome ed il numero da chiamare ..insrisci i dati di login pass ..... salvi ... ed in automatico ti parte kinternet !!! clicchi sull'iconcina di kinternet ...e ... TAAAMMMMMMMMM..... connesso !!! Ciao |
|
|
|
|
|
18-06-2005, 18:33
|
#11 | |
|
Senior Member
Iscritto dal: Jul 2002
Città: Padova
Messaggi: 4245
|
Quote:
Ciao. |
|
|
|
|
|
18-06-2005, 18:35
|
#12 | |
|
Senior Member
Iscritto dal: Jul 2002
Città: Padova
Messaggi: 4245
|
Quote:
Comunque, da quello che ho capito i messaggi che vedi ti vengono restituiti perchè il modulo non riesce a gestire il modem. Cosa ti dice dmesg subito dopo un modprobe hixax..........??? |
|
|
|
|
|
19-06-2005, 10:00
|
#13 | |
|
Senior Member
Iscritto dal: Jun 2002
Messaggi: 1393
|
Quote:
sisi uguale uguale, ma tammmm nn connessocome detto notavo solo all'vvio del sistema che diceva caricamento moduli fallito, questo problema lo dava su tutte le distribuzioni che ho provato, su alcune dava anche altri problemi, solo su suse se accontentava di 1 problema. X stefano dovresti ricordare la tragedia greca per provare a farlo andare a suo tempo, e nn ci sono riuscito, lo slakeware nn riesco manco ad installarlo quindi nn lo provo. ho provato fedora suse mandrake ubuntu lorma e ki più ne ha più ne metta. non potendomi connettere ad internet nn posso nemmeno avere aiuto in linea diretta, ogni volta devo cambiare disco fisso sul pc per caricare suse. forse se qualcuno mi dicesse i comandi da fare per postare il problema sul forum potrei elencarveli. mi servirebbe in particolare tutto lo stilato durante il caricamento così vedete il problema specifico. |
|
|
|
|
|
19-06-2005, 10:05
|
#14 | |
|
Senior Member
Iscritto dal: Jun 2002
Messaggi: 1393
|
Quote:
è facile, pure su windows l'isdn funziona a parte l'iniziale installazione dei driver e configurazione automatica della connessione ad internet tramite uno script.ins preparato dal provider poi modificato da me per i vari provider ke usomi piacerebbe sapere quanto ci hai perso di tempo per configurarlo e quanti libri di linux ti sei pappato....brrrrrrrrr |
|
|
|
|
|
19-06-2005, 13:34
|
#15 | |
|
Senior Member
Iscritto dal: Jul 2002
Città: Padova
Messaggi: 4245
|
Quote:
Quello che ho sempre pensato, è che se perdo una marea di tempo per installare un modem, alla fine non è solo per il modem, perchè è smanettando che impari a conoscere il sistema e impari dove mettere le mani in generale. Posso dire che ora mi so destreggiare abbastanza bene con il sistema e se mi capita di dover installare una nuova periferica che non ho mai installato so dove andare a mettere le mani e questo è merito anche dei precedenti sbattimenti vari. Qualche volta mi vedo costretto a chiedere aiuto lo stesso, però rispetto ad una volta moooolto meno. Vuol dire che qualche passo in avanti è stato fatto. Certo, su windows il modem isdn si installa in un attimo, però ci vuole ben e sottolineo ben altro per convincermi a tornare a windows
|
|
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 13:23.
