The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

форумы  помощь  поиск  регистрация  майллист  ВХОД  слежка  RSS
"mgetty проблема с диалаповыми пользователями"
Вариант для распечатки Архивированная нить - только для чтения! 
Пред. тема | След. тема 
Форумы Настройка Squid и других прокси серверов (Public)
Изначальное сообщение [Проследить за развитием треда]

"mgetty проблема с диалаповыми пользователями"
Сообщение от RAW emailИскать по авторуВ закладки on 24-Май-03, 13:42  (MSK)
Есть Сервер на Debian 2.17. Сервер имеет ISDN канал на интернет.
К серверу подключен модем.
Инициализация в mgetty.config:
init-chat "" \d\d+++\d\ATZS=0 OK

При попытке подключения удаленному юзеру выдается сообщение, что от удаленного компьютера не удается получить ответ.
Смотрю syslog, вот что по этому поводу в нем написано:
mgetty[5449]: data dev=ttyS0, pid=5449, caller='none', conn='38400', name='', cmd='usr/sbin/pppd', user='AutoPPP'
mgetty[21678]: init chat failed, exiting...: Invalid argument
mgetty[21678]: failed in mg_init_data, dev=ttyS0, pid=21678

Дело в том, что мгетти был настроен до меня и я не очень шарю в его настройках... Может кто поможет?

  Рекомендовать в FAQ | Cообщить модератору | Наверх

 Оглавление

Индекс форумов | Темы | Пред. тема | След. тема
Сообщения по теме

1. "mgetty проблема с диалаповыми пользователями"
Сообщение от iiws emailИскать по авторуВ закладки on 26-Май-03, 07:42  (MSK)
>Есть Сервер на Debian 2.17. Сервер имеет ISDN канал на интернет.
>К серверу подключен модем.
>Инициализация в mgetty.config:
>init-chat "" \d\d+++\d\ATZS=0 OK
>
>При попытке подключения удаленному юзеру выдается сообщение, что от удаленного компьютера не
>удается получить ответ.
>Смотрю syslog, вот что по этому поводу в нем написано:
>mgetty[5449]: data dev=ttyS0, pid=5449, caller='none', conn='38400', name='', cmd='usr/sbin/pppd', user='AutoPPP'
>mgetty[21678]: init chat failed, exiting...: Invalid argument

ясно же говорит , что чат-скрипт не отработал или в нем обшибка !

  Рекомендовать в FAQ | Cообщить модератору | Наверх

2. "mgetty проблема с диалаповыми пользователями"
Сообщение от RAW emailИскать по авторуВ закладки on 26-Май-03, 10:33  (MSK)
>>Есть Сервер на Debian 2.17. Сервер имеет ISDN канал на интернет.
>>К серверу подключен модем.
>>Инициализация в mgetty.config:
>>init-chat "" \d\d+++\d\ATZS=0 OK
>>
>>При попытке подключения удаленному юзеру выдается сообщение, что от удаленного компьютера не
>>удается получить ответ.
>>Смотрю syslog, вот что по этому поводу в нем написано:
>>mgetty[5449]: data dev=ttyS0, pid=5449, caller='none', conn='38400', name='', cmd='usr/sbin/pppd', user='AutoPPP'
>>mgetty[21678]: init chat failed, exiting...: Invalid argument
>
>ясно же говорит , что чат-скрипт не отработал или в нем обшибка
>!

Так а как его правильно настроить, где оно есть? Может просветите?

  Рекомендовать в FAQ | Cообщить модератору | Наверх

3. "mgetty проблема с диалаповыми пользователями"
Сообщение от iiws emailИскать по авторуВ закладки on 26-Май-03, 10:45  (MSK)
>>>Есть Сервер на Debian 2.17. Сервер имеет ISDN канал на интернет.
>>>К серверу подключен модем.
>>>Инициализация в mgetty.config:
>>>init-chat "" \d\d+++\d\ATZS=0 OK
>>>
>>>При попытке подключения удаленному юзеру выдается сообщение, что от удаленного компьютера не
>>>удается получить ответ.
>>>Смотрю syslog, вот что по этому поводу в нем написано:
>>>mgetty[5449]: data dev=ttyS0, pid=5449, caller='none', conn='38400', name='', cmd='usr/sbin/pppd', user='AutoPPP'
>>>mgetty[21678]: init chat failed, exiting...: Invalid argument
>>
>>ясно же говорит , что чат-скрипт не отработал или в нем обшибка
>>!
>
>Так а как его правильно настроить, где оно есть? Может просветите?


показывай все свои конфиги для pppd и для mgetty, как авторизация используется ? как стартуешь pppd ?  

  Рекомендовать в FAQ | Cообщить модератору | Наверх

4. "mgetty проблема с диалаповыми пользователями"
Сообщение от Pavel Искать по авторуВ закладки on 26-Май-03, 11:37  (MSK)
Была такая фигня ... пока новый mgetty не собрал то нифига не получалось
  Рекомендовать в FAQ | Cообщить модератору | Наверх

5. "mgetty проблема с диалаповыми пользователями"
Сообщение от RAW emailИскать по авторуВ закладки on 26-Май-03, 11:40  (MSK)
>>>>Есть Сервер на Debian 2.17. Сервер имеет ISDN канал на интернет.
>>>>К серверу подключен модем.
>>>>Инициализация в mgetty.config:
>>>>init-chat "" \d\d+++\d\ATZS=0 OK
>>>>
>>>>При попытке подключения удаленному юзеру выдается сообщение, что от удаленного компьютера не
>>>>удается получить ответ.
>>>>Смотрю syslog, вот что по этому поводу в нем написано:
>>>>mgetty[5449]: data dev=ttyS0, pid=5449, caller='none', conn='38400', name='', cmd='usr/sbin/pppd', user='AutoPPP'
>>>>mgetty[21678]: init chat failed, exiting...: Invalid argument
>>>
>>>ясно же говорит , что чат-скрипт не отработал или в нем обшибка
>>>!
>>
>>Так а как его правильно настроить, где оно есть? Может просветите?
>
>
>показывай все свои конфиги для pppd и для mgetty, как авторизация используется
>? как стартуешь pppd ?

Стартую демона через init.d просто. без настроек.
Мгетти рестартует кащеем в inittab-е.
Конфиги:
mgetty.config
#
# mgetty configuration file
#
# this is a sample configuration file, see mgetty.info for details
#
# comment lines start with a "#", empty lines are ignored


# ----- global section -----
#
# In this section, you put the global defaults, per-port stuff is below


# set the global debug level to "4" (default from policy.h)
debug 4

# set the local fax station id
fax-id  

# access the modem(s) with 38400 bps
speed 38400

# use an alternate issue file, to avoid being bitten by linuxlogo
issue-file /etc/issue.mgetty

#  use these options to make the /dev/tty-device owned by "uucp.uucp"
#  and mode "rw-rw-r--" (0664). *LEADING ZERO NEEDED!*
#port-owner uucp
#port-group uucp
#port-mode 0664

#  use these options to make incoming faxes owned by "root.uucp"
#  and mode "rw-r-----" (0640). *LEADING ZERO NEEDED!*
#fax-owner root
#fax-group uucp
#fax-mode 0640


# ----- port specific section -----
#
# Here you can put things that are valid only for one line, not the others
#

# Old configuration
# Zoom V.FX 28.8, connected to ttyS0: don't do fax, less logging
#
port ttyS0
  init-chat "" \d\d+++\d\dATZS0=0 OK
#  init-chat "" ATZ OK
#  init-chat "" \d\d\d+++\d\d\dAT&FS2=255 OK ATN3S0=0S13.2=1 OK
#  debug 3
#  data-only y

login.config
# login.config
#
# This is a sample "login dispatcher" configuration file for mgetty
#
# Format:
# username userid utmp_entry login_program [arguments]
#
# Meaning:
#       for a "username" entered at mgettys login: prompt, call
# "login_program" with [arguments], with the uid set to "userid",
# and a USER_PROCESS utmp entry with ut_user = "utmp_entry"
#
# username may be prefixed / suffixed by "*" (wildcard)
#
# userid is a valid user name from /etc/passwd, or "-" to not set
#  a login user id and keep the uid/euid root (needed for /bin/login)
#
# utmp_entry is what will appear in the "who" listing. Use "-" to not
#  set an utmp entry (a must for /bin/login), use "@" to set it to the
#  username entered. Maximum length is 8 characters.
#
# login_program is the program that will be exec()ed, with the arguments
#  passed in [arguments]. A "@" in the arguments will be replaced with the
#  username entered. Warning: if no "@" is given, the login_program has
#  no way to know what user name the user entered.
#
#
# SAMPLES:
# Use this one with my Taylor-UUCP and Taylor-UUCP passwd files.
#  (Big advantage: tuucp can use the same passwd file for serial dial-in
#   and tcp dial-in [uucico running as in.uucpd]). Works from 1.05 up.
#
#U* uucp @ /usr/sbin/uucico -l -u @

#
# Use this one for fido calls (login name /FIDO/ is handled specially)
#
# You need Eugene Crosser's "ifmail" package for this to work.
#  mgetty has to be compiled with "-DFIDO", otherwise a fido call won't
#  be detected.
#
#/FIDO/ uucp fido /usr/lib/fnet/ifcico @

#/FIDO/ uucp fido /usr/local/bin/bforce @
#
# Automatic PPP startup on receipt of LCP configure request (AutoPPP).
#  mgetty has to be compiled with "-DAUTO_PPP" for this to work.
#  Warning: Case is significant, AUTOPPP or autoppp won't work!
#  Consult the "pppd" man page to find pppd options that work for you.
#
#  NOTE: for *some* users, the "-detach" option has been necessary, for
#        others, not at all. If your pppd doesn't die after hangup, try it.
#
#  NOTE2: "debug" creates lots of debugging info.  LOOK AT IT if things
#         do not work out of the box, most likely it's a ppp problem!
#
#  NOTE3: "man pppd" is your friend!
#
#  NOTE4: max. 9 arguments allowed.
#
#/AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug
/AutoPPP/ -     a_ppp   /usr/sbin/pppd auth -chap +pap login lock idle 600

#
#
# An example where no login name in the argument list is desired:
#  automatically telnetting to machine "smarty" for a given login name
#
#telnet-smarty gast telnet /usr/bin/telnet -8 smarty
#
# This is the "standard" behaviour - *dont* set a userid or utmp
#  entry here, otherwise /bin/login will fail!
#  This entry isn't really necessary: if it's missing, the built-in
#  default will do exactly this.
#
#* - - /bin/login @
#* - - /bin/false @

options
# /etc/ppp/options
#
# $Id: options,v 1.4 1996/05/01 18:57:04 alvar Exp $
#
# Originally created by Jim Knoble <jmknoble@mercury.interpath.net>
# Modified for Debian by alvar Bray <alvar@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org>
#
# Use the command  egrep -v '#|^ *$' /etc/ppp/options to quickly see what
# options are active in this file.

#debug

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use
# Two Servers can be remotely configured
#dns-addr 193.124.240.200
ms-dns 10.4.253.2
ms-dns 127.0.0.1

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
ms-wins 10.4.253.10


# 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

# 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 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).
#require-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).
#5^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>

# 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. Under Linux, the echo-request is sent when
# no packets have been received from the peer for 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 10

# 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 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

options.ttyS0
# this file to
# options.<ttyname> for each tty with a modem on it.
#
# The options.tty file will assign an IP address to each PPP connection
# as it comes up. They must all be distinct!
#
# Example:
# options.ttyS1 for com2 under DOS.
#
# Edit the following line so that the first IP address
# mentioned is the ip address of the serial port while the second
# is the IP address of your host
#
# I usually use the convention ns1.isb.gomel.by + dash + last 2 character of
# the ttyname to refer to serial ports.
# For example servername_s1 for ttyS1 on server "servername"

#10.4.253.2:ppp_S0
ppp-server_s0.risb:ppp_s0.risb

Ну кажется все настройки... Может еще чего нужно?

  Рекомендовать в FAQ | Cообщить модератору | Наверх

6. "mgetty проблема с диалаповыми пользователями"
Сообщение от iiws emailИскать по авторуВ закладки on 26-Май-03, 12:19  (MSK)
кинул тебе ответ на твой email - читай
  Рекомендовать в FAQ | Cообщить модератору | Наверх


Удалить

Индекс форумов | Темы | Пред. тема | След. тема
Пожалуйста, прежде чем написать сообщение, ознакомьтесь с данными рекомендациями.




Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру