PPP server doesn`t assign an IP address

Hi

I`ve made a ppp dial-in server as allways on mgetty, but after connect from
a windows workstation I recive the following error "738 server doesn`t
assign an IP address".
In my logs I have something like this:

Jun 30 23:06:49 ghost pppd[2287]: pppd 2.4.2 started by root, uid 0
Jun 30 23:06:49 ghost pppd[2287]: Using interface ppp0
Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14
Jun 30 23:06:57 ghost pppd[2287]: LCP terminated by peer
(^[A-M-<^@<M-Mt^@^@^@^@)
Jun 30 23:06:59 ghost pppd[2287]: Hangup (SIGHUP)
Jun 30 23:06:59 ghost pppd[2287]: Modem hangup
Jun 30 23:06:59 ghost pppd[2287]: Connection terminated.
Jun 30 23:06:59 ghost pppd[2287]: Exit.

Mgetty logs:
06/30 23:06:48 ##### data dev=ttyS14, pid=2287, caller='none',
conn='2400/V42BIS', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

My configuration:

- login.config
/AutoPPP/ - - /usr/sbin/pppd noauth kdebug 4 debug
* - - /bin/login @

- mgetty.config
# Global debug level
debug 4

# Global access speed
speed 115200

# ----- port specific section -----
# ZyXEL Omni 56k
port ttyS14
init-chat "" ATE1Q0V1 OK ATM0 OK

# ZyXEL Omni 56k
port ttyS15
init-chat "" ATE1Q0V1 OK ATM0 OK

- options.ttyS14
115200
crtscts
lock
modem
debug
noauth
proxyarp
netmask 255.255.255.0
ms-dns 194.204.152.34
ms-dns 194.204.159.1
10.0.1.8:10.0.1.100

The address of my network card is 10.0.1.8. There is no iptables rules, and
I have a ppp user with a ppp password and special shell. This problem starts
when I migrate to 2.6.x kernel, but this may not be a problem.

Thx for any suggestions.

--
i NET, www.inet.one.pl www.inet.ll.pl - QoS and security for Linux
"Unix is very simple, but it takes a genius to understand the simplicity".
[Dennis Ritchie]

Baroo <(E-Mail Removed)> wrote:
> Hi

> I`ve made a ppp dial-in server as allways on mgetty, but after
> connect from a windows workstation I recive the following error
> "738 server doesn`t assign an IP address". In my logs I have
> something like this:

> Jun 30 23:06:49 ghost pppd[2287]: pppd 2.4.2 started by root, uid 0
> Jun 30 23:06:49 ghost pppd[2287]: Using interface ppp0
> Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14
> Jun 30 23:06:57 ghost pppd[2287]: LCP terminated by peer
> (^[A-M-<^@<M-Mt^@^@^@^@)
> Jun 30 23:06:59 ghost pppd[2287]: Hangup (SIGHUP)
> Jun 30 23:06:59 ghost pppd[2287]: Modem hangup
> Jun 30 23:06:59 ghost pppd[2287]: Connection terminated.
> Jun 30 23:06:59 ghost pppd[2287]: Exit.

> Mgetty logs:
> 06/30 23:06:48 ##### data dev=ttyS14, pid=2287, caller='none',
> conn='2400/V42BIS', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

> My configuration:

> - login.config
> /AutoPPP/ - - /usr/sbin/pppd noauth kdebug 4 debug
> * - - /bin/login @

> - mgetty.config
> # Global debug level
> debug 4

> # Global access speed
> speed 115200

> # ----- port specific section -----
> # ZyXEL Omni 56k
> port ttyS14
> init-chat "" ATE1Q0V1 OK ATM0 OK

> # ZyXEL Omni 56k
> port ttyS15
> init-chat "" ATE1Q0V1 OK ATM0 OK

> - options.ttyS14
> 115200
> crtscts
> lock
> modem
> debug
> noauth
> proxyarp
> netmask 255.255.255.0
> ms-dns 194.204.152.34
> ms-dns 194.204.159.1
> 10.0.1.8:10.0.1.100

> The address of my network card is 10.0.1.8. There is no iptables
> rules, and I have a ppp user with a ppp password and special shell.
> This problem starts when I migrate to 2.6.x kernel, but this may
> not be a problem.

Here are some observations that may or may not help:

1) The devfs in 2.6.x kernels may not work:

> Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14

It's marked "OBSOLETE" where it's configured in the kernel and is being
replaced by udev. I'd recommend using the traditional ttySx device
files. Also tts/14 is not the same as ttyS14 (options.ttyS14) to pppd.
(I don't know whether sym-linking /dev/tts/14 to /dev/ttyS14 would work.)

2) The mgetty log line

> conn='2400/V42BIS', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

suggests you are using AutoPPP, but the cmd doesn't agree with the
login.conf line:

> /AutoPPP/ - - /usr/sbin/pppd noauth kdebug 4 debug

However, it may be that mgetty just doesn't show the pppd command
line options in cmd='...'.

2) You must have the /etc/ppp/pap-secrets file configured correctly to
do AutoPPP. If AutoPPP isn't compiled into mgetty then that line may
be ignored and /bin/login used by mgetty to present a login prompt,
but that doesn't seem to be the case. The "ppp password and special
shell," the noauth option, and lack of a "user call-in_username" option
all suggest intent to use a login prompt. If so then comment out the
AutoPPP line.

3) The debug option in the AutoPPP line should produce PPP link
negotiation messages in some log file (depends on what's in
/etc/syslog.conf) from pppd that might be useful, but none are
provided. BTW "kdebug 4" is pretty much useless for pppd 2.4.x.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"

Clifford Kite <(E-Mail Removed)> writes:

>Baroo <(E-Mail Removed)> wrote:
>> Hi

>> I`ve made a ppp dial-in server as allways on mgetty, but after
>> connect from a windows workstation I recive the following error
>> "738 server doesn`t assign an IP address". In my logs I have
>> something like this:

No you forgot to set up debugging in /etc/syslog.conf
daemon.*;local2.* /var/log/daemonlog
and then do
killall -1 syslogd
(do NOT forget that -1)
Then look in /var/log/daemonlog. There is a bunch of stuff that happened in
the 8 sec that has not been logged.



>> Jun 30 23:06:49 ghost pppd[2287]: pppd 2.4.2 started by root, uid 0
>> Jun 30 23:06:49 ghost pppd[2287]: Using interface ppp0
>> Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14

This 8 sec.

>> Jun 30 23:06:57 ghost pppd[2287]: LCP terminated by peer
>> (^[A-M-<^@<M-Mt^@^@^@^@)
>> Jun 30 23:06:59 ghost pppd[2287]: Hangup (SIGHUP)
>> Jun 30 23:06:59 ghost pppd[2287]: Modem hangup
>> Jun 30 23:06:59 ghost pppd[2287]: Connection terminated.
>> Jun 30 23:06:59 ghost pppd[2287]: Exit.

>> Mgetty logs:
>> 06/30 23:06:48 ##### data dev=ttyS14, pid=2287, caller='none',
>> conn='2400/V42BIS', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

>> My configuration:

>> - login.config
>> /AutoPPP/ - - /usr/sbin/pppd noauth kdebug 4 debug

remove the kdebug 4. It is no longer operative.


>> modem
>> debug
>> noauth
>> proxyarp
>> netmask 255.255.255.0

netmask makes no sense. This is point to point, one IP to another specific
IP. Thus the netmask is ALWAYS 255.255.255.255

>> ms-dns 194.204.152.34
>> ms-dns 194.204.159.1
>> 10.0.1.8:10.0.1.100

The other of Kite's comments (eg devfs) may also be causeing trouble, but I
do not see that they are from the logs.

> 1) The devfs in 2.6.x kernels may not work:
>
>> Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14
>
> It's marked "OBSOLETE" where it's configured in the kernel and is being
> replaced by udev. I'd recommend using the traditional ttySx device
> files. Also tts/14 is not the same as ttyS14 (options.ttyS14) to pppd.
> (I don't know whether sym-linking /dev/tts/14 to /dev/ttyS14 would work.)

Yes. This is probably the main problem with my configuration. I use ttyS14
in all configurations files. Mgetty working fine with that (I have ttyS14 in
mgetty logs) but pppd recive /dev/tts/14 and it can`t find correct
options.xxxxx file. I`am newbe at 2.6.x kernels and udev. So, could you tell
me what I should do to totaly disable tts/xx names and use only ttySxx?

--
i NET, www.inet.one.pl www.inet.ll.pl - QoS and security for Linux
"Unix is very simple, but it takes a genius to understand the simplicity".
[Dennis Ritchie]

Baroo <(E-Mail Removed)> wrote:
>> 1) The devfs in 2.6.x kernels may not work:
>>
>>> Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14
>>
>> It's marked "OBSOLETE" where it's configured in the kernel and is being
>> replaced by udev. I'd recommend using the traditional ttySx device
>> files. Also tts/14 is not the same as ttyS14 (options.ttyS14) to pppd.
>> (I don't know whether sym-linking /dev/tts/14 to /dev/ttyS14 would work.)

> Yes. This is probably the main problem with my configuration. I use
> ttyS14 in all configurations files. Mgetty working fine with that
> (I have ttyS14 in mgetty logs) but pppd recive /dev/tts/14 and it
> can`t find correct options.xxxxx file. I`am newbe at 2.6.x kernels
> and udev. So, could you tell me what I should do to totaly disable
> tts/xx names and use only ttySxx?

Reconfigure and recompile the kernel, disabling devfs and adding
serial support.

Cut-and-paste from "make menuconfig" for a 2.6.8.1 kernel:

Linux Kernel Configuration
File systems --->
Pseudo filesystems --->
[ ] /dev file system support (OBSOLETE)

Linux Kernel Configuration
Device Drivers --->
Character devices --->
Serial drivers --->
<*> 8250/16550 and compatible serial support

You don't need udev, see the Help section of /dev filesystem support.
It has limited capabilities.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"

Clifford Kite <(E-Mail Removed)> writes:

>Baroo <(E-Mail Removed)> wrote:
>>> 1) The devfs in 2.6.x kernels may not work:
>>>
>>>> Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14
>>>
>>> It's marked "OBSOLETE" where it's configured in the kernel and is being
>>> replaced by udev. I'd recommend using the traditional ttySx device
>>> files. Also tts/14 is not the same as ttyS14 (options.ttyS14) to pppd.
>>> (I don't know whether sym-linking /dev/tts/14 to /dev/ttyS14 would work.)

>> Yes. This is probably the main problem with my configuration. I use
>> ttyS14 in all configurations files. Mgetty working fine with that
>> (I have ttyS14 in mgetty logs) but pppd recive /dev/tts/14 and it
>> can`t find correct options.xxxxx file. I`am newbe at 2.6.x kernels
>> and udev. So, could you tell me what I should do to totaly disable
>> tts/xx names and use only ttySxx?


>Reconfigure and recompile the kernel, disabling devfs and adding
>serial support.

Please don't. His kernel unless he compiled it himself, already has serial
support. And he does not need options.xxxx especially if he only has one
port. Just put the options into /etc/ppp/options. The options.xxxx are only
there IF you want completely separate options for eachof the various tty
ports.
I would really like to see a debug output from ppp first especially before
he starts to play with the kernel. He is far more liable to break something
recompiling the kernel than fix.




>Cut-and-paste from "make menuconfig" for a 2.6.8.1 kernel:

>Linux Kernel Configuration
>File systems --->
>Pseudo filesystems --->
>[ ] /dev file system support (OBSOLETE)

>Linux Kernel Configuration
>Device Drivers --->
>Character devices --->
>Serial drivers --->
><*> 8250/16550 and compatible serial support

>You don't need udev, see the Help section of /dev filesystem support.
>It has limited capabilities.

>--
>Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"

U¿ytkownik "Unruh" <unruh-(E-Mail Removed)> napisa³ w wiadomo¶ci
news:dake72$qt5$(E-Mail Removed)...
> Clifford Kite <(E-Mail Removed)> writes:
>
>>Baroo <(E-Mail Removed)> wrote:
>>>> 1) The devfs in 2.6.x kernels may not work:
>>>>
>>>>> Jun 30 23:06:49 ghost pppd[2287]: Connect: ppp0 <--> /dev/tts/14
>>>>
>>>> It's marked "OBSOLETE" where it's configured in the kernel and is being
>>>> replaced by udev. I'd recommend using the traditional ttySx device
>>>> files. Also tts/14 is not the same as ttyS14 (options.ttyS14) to pppd.
>>>> (I don't know whether sym-linking /dev/tts/14 to /dev/ttyS14 would
>>>> work.)
>
>>> Yes. This is probably the main problem with my configuration. I use
>>> ttyS14 in all configurations files. Mgetty working fine with that
>>> (I have ttyS14 in mgetty logs) but pppd recive /dev/tts/14 and it
>>> can`t find correct options.xxxxx file. I`am newbe at 2.6.x kernels
>>> and udev. So, could you tell me what I should do to totaly disable
>>> tts/xx names and use only ttySxx?
>
>
>>Reconfigure and recompile the kernel, disabling devfs and adding
>>serial support.
>
> Please don't. His kernel unless he compiled it himself, already has serial
> support. And he does not need options.xxxx especially if he only has one
> port. Just put the options into /etc/ppp/options. The options.xxxx are
> only
> there IF you want completely separate options for eachof the various tty
> ports.

Yes, I need 5 separate sections for each modem

--
i NET, www.inet.one.pl www.inet.ll.pl - QoS and security for Linux
"Unix is very simple, but it takes a genius to understand the simplicity".
[Dennis Ritchie]

> I would really like to see a debug output from ppp first especially before
> he starts to play with the kernel. He is far more liable to break
> something
> recompiling the kernel than fix.

Here you are:
Jul 8 09:25:25 ghost pppd[2291]: pppd 2.4.2 started by root, uid 0
Jul 8 09:25:25 ghost pppd[2291]: using channel 1
Jul 8 09:25:25 ghost pppd[2291]: Using interface ppp0
Jul 8 09:25:25 ghost pppd[2291]: Connect: ppp0 <--> /dev/tts/15
Jul 8 09:25:25 ghost pppd[2291]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0x12c49979> <pcomp> <accomp>]
Jul 8 09:25:26 ghost pppd[2291]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>
<magic 0x12c49979> <pcomp> <accomp>]
Jul 8 09:25:28 ghost pppd[2291]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0x12c49979> <pcomp> <accomp>]
Jul 8 09:25:28 ghost pppd[2291]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>
<magic 0x12c49979> <pcomp> <accomp>]
Jul 8 09:25:30 ghost pppd[2291]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0x3ae767b3> <pcomp> <accomp> <callback CBCP>]
Jul 8 09:25:30 ghost pppd[2291]: sent [LCP ConfRej id=0x1 <callback CBCP>]
Jul 8 09:25:31 ghost pppd[2291]: rcvd [LCP ConfReq id=0x2 <asyncmap 0x0>
<magic 0x3ae767b3> <pcomp> <accomp>]
Jul 8 09:25:31 ghost pppd[2291]: sent [LCP ConfAck id=0x2 <asyncmap 0x0>
<magic 0x3ae767b3> <pcomp> <accomp>]
Jul 8 09:25:31 ghost pppd[2291]: sent [CCP ConfReq id=0x1 <deflate 15>
<deflate(old#) 15> <bsd v1 15>]
Jul 8 09:25:31 ghost pppd[2291]: sent [IPCP ConfReq id=0x1 <compress VJ 0f
01> <addr 10.0.1.8>]
Jul 8 09:25:31 ghost pppd[2291]: rcvd [LCP code=0xc id=0x3 3a e7 67 b3 4d
53 52 41 53 56 35 2e 31 30]
Jul 8 09:25:31 ghost pppd[2291]: sent [LCP CodeRej id=0x2 0c 03 00 12 3a e7
67 b3 4d 53 52 41 53 56 35 2e 31 30]
Jul 8 09:25:32 ghost pppd[2291]: rcvd [LCP code=0xc id=0x4 3a e7 67 b3 4d
53 52 41 53 2d 31 2d 4e 4f 54 45 42 4f 4f 4b]
Jul 8 09:25:32 ghost pppd[2291]: sent [LCP CodeRej id=0x3 0c 04 00 18 3a e7
67 b3 4d 53 52 41 53 2d 31 2d 4e 4f 54 45 42 4f 4f 4b]
Jul 8 09:25:32 ghost pppd[2291]: rcvd [CCP ConfReq id=0x5
<mppe -H -M -S -L -D +C>]
Jul 8 09:25:32 ghost pppd[2291]: sent [CCP ConfRej id=0x5
<mppe -H -M -S -L -D +C>]
Jul 8 09:25:32 ghost pppd[2291]: rcvd [IPCP ConfReq id=0x6 <compress VJ 0f
01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-wins 0.0.0.0> <ms-dns3 0.0.0.0>
<ms-wins 0.0.0.0>]
Jul 8 09:25:32 ghost pppd[2291]: sent [IPCP ConfRej id=0x6 <addr 0.0.0.0>
<ms-dns1 0.0.0.0> <ms-wins 0.0.0.0> <ms-dns3 0.0.0.0> <ms-wins 0.0.0.0>]
Jul 8 09:25:32 ghost pppd[2291]: rcvd [CCP ConfRej id=0x1 <deflate 15>
<deflate(old#) 15> <bsd v1 15>]
Jul 8 09:25:32 ghost pppd[2291]: sent [CCP ConfReq id=0x2]
Jul 8 09:25:32 ghost pppd[2291]: rcvd [IPCP ConfAck id=0x1 <compress VJ 0f
01> <addr 10.0.1.8>]
Jul 8 09:25:32 ghost pppd[2291]: rcvd [CCP TermReq
id=0x7":\37777777747g\37777777663\000<\37777777715 t\000\000\002\37777777734"]
Jul 8 09:25:32 ghost pppd[2291]: sent [CCP TermAck id=0x7]
Jul 8 09:25:32 ghost pppd[2291]: rcvd [IPCP ConfReq id=0x8 <compress VJ 0f
01> <addr 0.0.0.0>]
Jul 8 09:25:32 ghost pppd[2291]: sent [IPCP ConfRej id=0x8 <addr 0.0.0.0>]
Jul 8 09:25:33 ghost pppd[2291]: rcvd [IPCP TermReq id=0x9
":\37777777747g\37777777663\000<\37777777715t\000\ 000\002\37777777742"]
Jul 8 09:25:33 ghost pppd[2291]: sent [IPCP TermAck id=0x9]
Jul 8 09:25:33 ghost pppd[2291]: rcvd [LCP TermReq id=0xa
":\37777777747g\37777777663\000<\37777777715t\000\ 000\000\000"]
Jul 8 09:25:33 ghost pppd[2291]: LCP terminated by peer
(:M-ggM-3^@<M-Mt^@^@^@^@)
Jul 8 09:25:33 ghost pppd[2291]: sent [LCP TermAck id=0xa]
Jul 8 09:25:35 ghost pppd[2291]: Hangup (SIGHUP)
Jul 8 09:25:35 ghost pppd[2291]: Modem hangup
Jul 8 09:25:35 ghost pppd[2291]: Connection terminated.
Jul 8 09:25:35 ghost pppd[2291]: Exit.

This line:
Jul 8 09:25:32 ghost pppd[2291]: sent [IPCP ConfRej id=0x6 <addr 0.0.0.0>
<ms-dns1 0.0.0.0> <ms-wins 0.0.0.0> <ms-dns3 0.0.0.0> <ms-wins 0.0.0.0>]
was sent because pppd couldn`t find the options.xxx file

--
i NET, www.inet.one.pl www.inet.ll.pl - QoS and security for Linux
"Unix is very simple, but it takes a genius to understand the simplicity".
[Dennis Ritchie]

> Linux Kernel Configuration
> File systems --->
> Pseudo filesystems --->
> [ ] /dev file system support (OBSOLETE)
>
> Linux Kernel Configuration
> Device Drivers --->
> Character devices --->
> Serial drivers --->
> <*> 8250/16550 and compatible serial support

This is what I have now.

> You don't need udev, see the Help section of /dev filesystem support.
> It has limited capabilities.

Are you sure this isn`t a udev problem? I have found something like this in
udev.rules file:
# tty devices
KERNEL="tty[0-9]*", NAME="vc/%n", SYMLINK="%k"
KERNEL="ttyS[0-9]*", NAME="tts/%n", SYMLINK="%k"
KERNEL="ttyUSB[0-9]*", NAME="tts/USB%n"

--
i NET, www.inet.one.pl www.inet.ll.pl - QoS and security for Linux
"Unix is very simple, but it takes a genius to understand the simplicity".
[Dennis Ritchie]

U¿ytkownik "Baroo" <(E-Mail Removed)> napisa³ w wiadomo¶ci
news:dalakp$lea$(E-Mail Removed)...
>> Linux Kernel Configuration
>> File systems --->
>> Pseudo filesystems --->
>> [ ] /dev file system support (OBSOLETE)
>>
>> Linux Kernel Configuration
>> Device Drivers --->
>> Character devices --->
>> Serial drivers --->
>> <*> 8250/16550 and compatible serial support
>
> This is what I have now.
>
>> You don't need udev, see the Help section of /dev filesystem support.
>> It has limited capabilities.
>
> Are you sure this isn`t a udev problem? I have found something like this
> in udev.rules file:
> # tty devices
> KERNEL="tty[0-9]*", NAME="vc/%n", SYMLINK="%k"
> KERNEL="ttyS[0-9]*", NAME="tts/%n", SYMLINK="%k"
> KERNEL="ttyUSB[0-9]*", NAME="tts/USB%n"

Sory for so many posts. This is not a udev problem. I have disabled udev and
in logs I have:
Jul 8 09:42:14 ghost pppd[1368]: Connect: ppp0 <--> /dev/ttyS15
but it still doesn`t work.

--
i NET, www.inet.one.pl www.inet.ll.pl - QoS and security for Linux
"Unix is very simple, but it takes a genius to understand the simplicity".
[Dennis Ritchie]