Subject says it all; I'm trying to set up a Red Hat 7 machine to do dialup on demand. I started out with pppd just to be sure everything worked, and pppd does work; the connection comes up, I authenticate, and I can pass packets. But for some reason diald is failing. Here's the relevant part of /var/log/messages, taken when diald was running and we try to ping "pluto.saecos.com": Nov 13 14:14:10 guinea diald[22415]: Trigger: udp 192.168.0.1/1097 207.229.143.3/53 Nov 13 14:14:10 guinea diald[22415]: Calling site 192.168.0.2 Nov 13 14:14:11 guinea connect: Initializing Modem Nov 13 14:14:12 guinea connect: Dialing system Nov 13 14:14:34 guinea connect: Connected Nov 13 14:14:34 guinea connect: Loggin in >> Nov 13 14:14:35 guinea diald[22415]: connector: /usr/lib/diald/connect: [: to: >binary operator expected Nov 13 14:14:35 guinea connect: Protocol started Nov 13 14:14:35 guinea diald[22415]: Connected to site 192.168.0.2 Nov 13 14:14:35 guinea diald[22415]: Running pppd (pid = 22446). Nov 13 14:14:35 guinea kernel: PPP: version 2.3.7 (demand dialling) Nov 13 14:14:35 guinea kernel: PPP line discipline registered. Nov 13 14:14:35 guinea kernel: registered device ppp0 Nov 13 14:14:35 guinea pppd[22446]: pppd 2.3.11 started by root, uid 0 Nov 13 14:14:35 guinea pppd[22446]: Using interface ppp0 Nov 13 14:14:35 guinea pppd[22446]: Connect: ppp0 <--> /dev/ttyS0 Nov 13 14:14:35 guinea kernel: PPP BSD Compression module registered Nov 13 14:14:35 guinea kernel: PPP Deflate Compression module registered >>> Nov 13 14:14:36 guinea pppd[22446]: Peer is not authorized to use remote address >216.80.19.11 Nov 13 14:14:37 guinea pppd[22446]: Hangup (SIGHUP) Nov 13 14:14:37 guinea pppd[22446]: Modem hangup Nov 13 14:14:37 guinea pppd[22446]: Connection terminated. Nov 13 14:14:37 guinea pppd[22446]: Connect time 0.1 minutes. Nov 13 14:14:37 guinea pppd[22446]: Sent 310 bytes, received 308 bytes. Nov 13 14:14:37 guinea pppd[22446]: Exit. [angle brackets added by me] I'm not sure what the "[: to: binary operator expected" message is talking about but diald appears to soldier on in spite of it. The one that has me puzzled is the next one I marked, "Peer is not authorized to use remote address." I got that error when I was testing with pppd alone, but fixed it by adding "dynamic" and "defaultroute" in the /etc/ppp/options file. But that tactic doesn't appear to be working with diald. For comparison's sake, here's the options file that's working for plain old ppp: lock defaultroute noipdefault modem /dev/ttyS0 115200 crtscts debug passive asyncmap 0 name "saecos" ...here's /etc/diald.conf: mode ppp connect /usr/lib/diald/connect device /dev/ttyS0 speed 115200 modem lock crtscts local 192.168.0.1 remote 192.168.0.2 dynamic defaultroute proxyarp demasq ip-up /etc/sysconfig/network-scripts/ifup-ppp pppd-options file /etc/ppp/options.diald debug 0x0008 include /usr/lib/diald/standard.filter ...and here's /etc/ppp/options.diald: noipdefault debug passive asyncmap 0 name "saecos" I've found several archives on line in which people mention this or a similar problem, but so far no solutions, or suggestions that I've already tried. Any thoughts? Or places to look for more info? Thanks, -m _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
