RE: ISP dialing with callback - def. route problems
You do not need the line compress stuff it's over kill and outdated, it just slows down the connection. On callback you are not logging into his box, he is logging into your box You also need gateway="YES" in rc.conf if dialin user want to access public internet through your gateway box. IF you have firewall you now have to use NAT function because dialin user looks like private LAN. change incoming section to this incoming: # section header name enable pap # uses ppp.secret file # SECURITY WARNING - It is VITAL that pap is enabled. If it is not, # you are allowing any body to establish an dial in ppp session with # your FBSD box using any ID/password. There is no authentication being # done on incoming ppp connections if pap is not enabled. - SECURITY WARNING allow users *# allow all users who pass authentication access accept dns # give dial in connection access to dns lookup set ifaddr 10.0.0.1 10.0.0.2 255.255.255.255 disable pred1 deflate lqr # compression features & line quality reporting denypred1 deflate lqr # compression features & line quality reporting disable ipv6 # turn off ipv6 challenge -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kyryll A Mirnenko Sent: Monday, February 23, 2004 3:21 PM To: [EMAIL PROTECTED]; JJB Subject: RE: ISP dialing with callback - def. route problems Thanks to JJB, callback is set up, e.g. ISP calls back & modems answers the call. The most stupid bug was in /etc/ttys: ttyl0 "/usr/libexec/getty callback1" dialup on (instead of ttyd0 - for Lucent winmodem driver). Now I've got more sophisticated callback problem. Saying again, when calling directly no such problem exists, as for callback - Windows client ppp seems not to produce any problems, so that's not ISP bugs: [!!!] PPP fails to add default route, e.g. I can see his DNS (gethostbyname(),...) & the whole local network (for ex., his HTTP server), but can't reach further. # route get says can't open roure socket, and here's the part of ppp.log (bugs're marked with "[HERE!!!] -->"): tun0: Command: incoming: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 tun0: Command: incoming: add default HISADDR tun0: Command: incoming: set authname MYLOGIN tun0: Command: incoming: set authkey tun0: Command: incoming: set logout ATS0=0 OK AT&W OK tun0: Phase: PPP Started (direct mode). tun0: Phase: bundle: Establish tun0: Phase: deflink: closed -> opening tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening -> carrier tun0: Phase: deflink: /dev/ttyl0: CD detected tun0: Phase: deflink: carrier -> lcp tun0: Phase: bundle: Authenticate tun0: Phase: deflink: his = PAP, mine = none tun0: Phase: Pap Output: MYLOGIN tun0: Phase: Pap Input: SUCCESS () tun0: Phase: deflink: lcp -> open tun0: Phase: bundle: Network [HERE!!!] --> tun0: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! [HERE!!!] --> tun0: Warning: ff02:4::/32: Change route failed: errno: Network is unreachable Can anybody deal with this? Here's incoming ppp.conf setup: default: set log phase tun chat cbcp command pap ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cual0 set speed 38400 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATS0=1 OK AT&W OK ATE1Q0 OK \\dATDP\\T TIMEOUT 80 CONNECT" set timeout 180# 3 minute idle timer (the default) enable dns # request DNS info (for resolv.conf) enable vjcomp deflate deflate24 protocomp pred1 accept vjcomp deflate deflate24 protocomp pred1 set urgent udp +53 incoming: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 add default HISADDR set authname MYLOGIN set authkey MYPASSWORD ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ISP dialing with callback - def. route problems
Thanks to JJB, callback is set up, e.g. ISP calls back & modems answers the call. The most stupid bug was in /etc/ttys: ttyl0 "/usr/libexec/getty callback1" dialup on (instead of ttyd0 - for Lucent winmodem driver). Now I've got more sophisticated callback problem. Saying again, when calling directly no such problem exists, as for callback - Windows client ppp seems not to produce any problems, so that's not ISP bugs: [!!!] PPP fails to add default route, e.g. I can see his DNS (gethostbyname(),...) & the whole local network (for ex., his HTTP server), but can't reach further. # route get says can't open roure socket, and here's the part of ppp.log (bugs're marked with "[HERE!!!] -->"): tun0: Command: incoming: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 tun0: Command: incoming: add default HISADDR tun0: Command: incoming: set authname MYLOGIN tun0: Command: incoming: set authkey tun0: Command: incoming: set logout ATS0=0 OK AT&W OK tun0: Phase: PPP Started (direct mode). tun0: Phase: bundle: Establish tun0: Phase: deflink: closed -> opening tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening -> carrier tun0: Phase: deflink: /dev/ttyl0: CD detected tun0: Phase: deflink: carrier -> lcp tun0: Phase: bundle: Authenticate tun0: Phase: deflink: his = PAP, mine = none tun0: Phase: Pap Output: MYLOGIN tun0: Phase: Pap Input: SUCCESS () tun0: Phase: deflink: lcp -> open tun0: Phase: bundle: Network [HERE!!!] --> tun0: Phase: deflink: IPV6CP protocol reject closes IPV6CP ! [HERE!!!] --> tun0: Warning: ff02:4::/32: Change route failed: errno: Network is unreachable Can anybody deal with this? Here's incoming ppp.conf setup: default: set log phase tun chat cbcp command pap ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cual0 set speed 38400 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATS0=1 OK AT&W OK ATE1Q0 OK \\dATDP\\T TIMEOUT 80 CONNECT" set timeout 180# 3 minute idle timer (the default) enable dns # request DNS info (for resolv.conf) enable vjcomp deflate deflate24 protocomp pred1 accept vjcomp deflate deflate24 protocomp pred1 set urgent udp +53 incoming: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 add default HISADDR set authname MYLOGIN set authkey MYPASSWORD ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ISP dialing with callback
Try changing the following which you have sitel: set phone 2053203 set authname CALLER set authkey MYPASSWORD set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 add default HISADDR set callback auth cbcp E.164 6661313 set cbcp 6661313 To this sitel: set phone 2053203 set authname CALLER set authkey MYPASSWORD set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 add default HISADDR set callback cbcp set cbcp 6661313 with 6661313 being the phone number and area code of the phone line connected to the modem which is to answer the callback call. You failed to say if you can hear your modem answer the incoming call, you have to Configure Modem to answer call using HAYES Commands ALL external and internal PCI voice phone modems since they were first developed, have been manufactured to comply to the Hayes standard. When you turn on your modem or reset it, your modem loads the 'active configuration profile' into non-volatile memory (NVRAM). The active configuration profile is a group of configuration settings, derived from the values of the modem's internal S registers, that define how the modem will operate. The active configuration profile can be either the factory-default, or one of two user defined profiles. The first time your modem is turned on, the factory-default profile is loaded into the 'active profile in non-volatile memory (NVRAM). The factory-default profile is stored in the modem's read-only-memory (ROM) and can not be changed. The factory-default profile contains standard settings which allow the majority of users to use their modem without every knowing about the Hayes standard. Modems are not factory configured to answer incoming calls by default, so you will have to manually create your own user profile, enable auto answer on first ring, save it to one of the user profiles in NVRAM, and tell the modem to use it on power up and reset as the default profile. Use 'tip' command to send Hayes commands to permanently configure the modem to answer incoming calls. Note: The Hayes modem commands are capital letters and the '0' is a zero. On the command line enter tip comX where X is the com port your modem is on. AT&F0load the factory default profile0 into current profile. ATS0=1 tell current profile to answer on first ring. AT Enter AT command 10 times to train modem to 115200 speed AT&W0write current profile to saved user profile0. AT&Y0tell modem to load user profile0 as default profile on power up. Use keyboard ~ key followed by . key to exit tip command. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kyryll A Mirnenko Sent: Sunday, February 22, 2004 11:42 AM To: [EMAIL PROTECTED] Subject: ISP dialing with callback This topic seems to be an elder one, but nobody around couldn't help me. I need to setup ppp (user) to dial to my callback-ISP. Here're useful info: 1). IPS uses PAP authentification. 2). Phone number negotiation is unsupported, I need to send it. When using Windows ppp-dialer (really buggy), everything is OK, so that's not ISP problem. Direct connection & authentification goes right, but no incoming call after that. I browsed my logs & only strange thing I found is there was no phone number I should send (at least in the readable part, not in the packages sent). Here're my configs (truncated with dummy logins & passwords :) - the provider entry is "sitel": [ /etc/ppp/ppp.conf ] default: set log phase tun chat cbcp command pap ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cual0 set speed 38400 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATDP\\T TIMEOUT 80 CONNECT" set timeout 180# 3 minute idle timer (the default) enable dns # request DNS info (for resolv.conf) enable vjcomp deflate deflate24 protocomp pred1 accept vjcomp deflate deflate24 protocomp pred1 set urgent udp +53 sitel: set phone 2053203 set authname CALLER set authkey MYPASSWORD set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 add default HISADDR set callback auth cbcp E.164 6661313 set cbcp 6661313 incoming: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 set authname CALLER set authkey MYPASSWORD [ /etc/ppp/ppp.secret ] CALLER MYPASSWORD * * 6661313 [ /etc/ttys ] console noneunknown off secure # ttyv0 "/usr/libexec/getty Pc" cons25u on secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" cons25u on secure ttyv2 "/usr/libexec/getty Pc" cons25u on secure ttyv3 "/usr/libexec/getty Pc" cons25u on secure ttyv4 "/usr/libexec/getty Pc" cons25u off secure
ISP dialing with callback
This topic seems to be an elder one, but nobody around couldn't help me. I need to setup ppp (user) to dial to my callback-ISP. Here're useful info: 1). IPS uses PAP authentification. 2). Phone number negotiation is unsupported, I need to send it. When using Windows ppp-dialer (really buggy), everything is OK, so that's not ISP problem. Direct connection & authentification goes right, but no incoming call after that. I browsed my logs & only strange thing I found is there was no phone number I should send (at least in the readable part, not in the packages sent). Here're my configs (truncated with dummy logins & passwords :) - the provider entry is "sitel": [ /etc/ppp/ppp.conf ] default: set log phase tun chat cbcp command pap ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cual0 set speed 38400 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATDP\\T TIMEOUT 80 CONNECT" set timeout 180# 3 minute idle timer (the default) enable dns # request DNS info (for resolv.conf) enable vjcomp deflate deflate24 protocomp pred1 accept vjcomp deflate deflate24 protocomp pred1 set urgent udp +53 sitel: set phone 2053203 set authname CALLER set authkey MYPASSWORD set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 add default HISADDR set callback auth cbcp E.164 6661313 set cbcp 6661313 incoming: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 set authname CALLER set authkey MYPASSWORD [ /etc/ppp/ppp.secret ] CALLER MYPASSWORD * * 6661313 [ /etc/ttys ] console noneunknown off secure # ttyv0 "/usr/libexec/getty Pc" cons25u on secure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" cons25u on secure ttyv2 "/usr/libexec/getty Pc" cons25u on secure ttyv3 "/usr/libexec/getty Pc" cons25u on secure ttyv4 "/usr/libexec/getty Pc" cons25u off secure ttyv5 "/usr/libexec/getty Pc" cons25u off secure ttyv6 "/usr/libexec/getty Pc" cons25u off secure ttyv7 "/usr/libexec/getty Pc" cons25u off secure ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xtermu off secure # ttyd0 "/usr/libexec/getty callback1" dialup on # AND SO ON... [ /etc/gettytab ] default:\ :cb:ce:ck:lc:fd#1000:im=\r\n%s/%m (%h) (%t)\r\n\r\n:sp#1200:\ :if=/etc/issue: # my callback account callback1|38400-baud:\ :np:sp#38400:pp=/etc/ppp/callback.ppp: # AND OTHERS... [ /etc/ppp/callback.ppp ] #!/bin/sh echo "!!! Incoming call. Use kill -TERM $$ to kill it..." | wall -g wheel exec /usr/sbin/ppp -direct incoming That's all. If have a solution or any experience in setting-up user-ppp callback, reply (workable configs won't be out of place). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"