PPP-Protokoll
# 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
OLD: (john@netrom.com) pointed out that if you are running shadow passwords, you have to re-compile pppd with 'make HAS_SHADOW=1' for the 'login'" option to work.
/AutoPPP/ - ppp /usr/sbin/pppd file /etc/ppp/autoppp.confDatei /etc/ppp/autoppp.conf
auth -chap +pap # papcrypt # require-pap # refuse-chap login modem crtscts lock proxyarp nodefaultroute noreplacedefaultroute debug asyncmap 20A0000 escape FF ms-dns 172.16.1.61 ms-dns 172.16.1.62 ms-wins 172.16.1.3 ms-wins 192.120.163.200 # 172.16.1.65:162.16.1.66 # remote-ip fuer Analog-PPP :162.16.1.66 logfile /var/log/di.log
S1:2345:respawn:/sbin/mgetty ttyS1oder
mo:23:respawn:/usr/sbin/mgetty -x 6 -s 38400 ttyS0Parameterbeschreibung mgetty (Auszug Datei /etc/inittab) :
dialinuser1 * b1ab1a!? 111.222.33.44 dialinuser2 * p8sSw0rd 111.222.33.44In der 'mgetty'-Konfigurationsdatei /etc/mgetty+sendfax/mgetty.config wird unter anderem festgelegt, bei einer ankommenden Verbindung nur den Modem-Modus zu verwenden:
# ----- port specific section ----- # Here you can put things that are valid only for one line, not the others # USR Sportster Vi 28.8, connected to ttyS0: don't do fax port ttyS0 data-only y rings 2Parameterbeschreibung Auszug Datei /etc/mgetty+sendfax/mgetty.config :
Die 'login'-Sperre wird realisiert durch ein simples touch /etc/nologin.ttyS0; chmod 666 /etc/nologin.ttyS0
Die 'login'-Sperre kann wieder aufgehoben werden durch
rm -f /etc/nologin.ttyS0
alias ppp-compress-21 bsd_comp alias ppp-compress-24 ppp_deflate alias ppp-compress-26 ppp_deflate
'arp -s <IP> <HW ADDR> pub'. "echo "1" > /proc/sys/net/ipv4/conf/eth0/proxy_arp"es wird hier serverseitig mit local-ip-address und remote-ip-adress gearbeitet.
The 'proxyarp' option sets up (surprise) a proxy ARP entry in the PPP server's ARP table that basically says 'send all packets destined for the PPP client to me'.
This is the easiest way to set up routing to a single PPP client - but you cannot use this if you are routing between two LANs - you must add proper network routes which can't use proxy ARP.
The use of proxy ARP is useful when you have a server. It will allow the dynamic connection of remote systems without the need for the update of the routing tables on other system but the one associated as the 'server'.
Linux's networking software directly supports proxy ARP. There is no need for a special daemon process such as proxyarpd used in some systems.
# $ tcpdump -n arp # 12:33:06.979376 arp who-has xx.xx.xx.149 tell xx.xx.xx.3 # 12:33:07.969471 arp who-has xx.xx.xx.149 tell xx.xx.xx.3 # 12:33:08.969470 arp who-has xx.xx.xx.149 tell xx.xx.xx.3 # # 3 packets received by filter # 0 packets dropped by kernel.
ATS0=3
daemon.*;local2.* /var/log/ppp
(Wegen einem Rechner bastelt man nicht in den Routingtabellen herum !)
dettlx05 dettnbxy
Lösung: IP-Adressvergabe bei Dial-In mittels Datei /etc/ppp/options.tty
Alternativ: Radius- oder Tacacs-Server verwenden.
domain tt.de.ifm
search tt.de.ifm es.de.ifm
nameserver 172.16.1.61
nameserver 172.16.1.62
# nameserver 192.120.252.1
Also check the following in your client DUN session:
#!/bin/sh
# Establishing a PPP connection
# to a Windows NT Server under CALLBACK mode use
phone="cb 555111"
/usr/sbin/pppd 38400 connect '/usr/sbin/chat -v -f $HOME/win_nt.chat' \
lock $phone
_______________________________________________________________________________
file: dial_win_nt.callback
To take the arrived callback correctly, a corresponding 'mgetty'
process for the interface must be defined for this purpose through an
entry to the file /etc/inittab. This 'mgetty' process is activated in the
next system start and takes the 'pppd' programmes' call in an arrived PPP
connection.
_______________________________________________________________________________
mo:23:respawn:/usr/sbin/mgetty -x 6 -s 38400 ttyS0
_______________________________________________________________________________
Exit file /etc/inittab
_______________________________________________________________________________
Parameter description exit file /etc/inittab :
-s : sets the port speed to be used
e.g.: 38400 Baud
ttyS0 : defines the interface to be addressed
( ttyS0 = COM1 )
-x 6 : sets the debug mode. The debug informations
are filed in the file /tmp/log.mg.
(/tmp/log.mg.ttyS0)
_______________________________________________________________________________
In the 'mgetty' configuration file /usr/etc/mgetty+sendfax/mgetty.config
is fixed to use only the modem mode in an arrived connection.
_______________________________________________________________________________
# ----- port specific section -----
# Here you can put things that are valid only for one line, not the others
# USR Sportster Vi 28.8, connected to ttyS0: don't do fax
port ttyS0
data-only y
rings 2
_______________________________________________________________________________
Exit file /usr/etc/mgetty+sendfax/mgetty.config
_______________________________________________________________________________
Parameter description exit file /usr/etc/mgetty+sendfax/mgetty.config :
port ttyS0 : Specific interface definitions for
port ttyS0 ( = COM1 )
data-only y : specifies the class of the modem connected to the
declared port:
no use from FAX mode, only data mode
rings : defines the RING messages' number that are
waited for until 'mgetty' lifts the modem up
_______________________________________________________________________________
Informatik- und Netzwerkverein Ravensburg e.V
Walter Jäger