Date: Wed, 3 Oct 2001 00:28:13 +0100 (BST) From: Andrew Gordon <arg-bsd@arg1.demon.co.uk> To: Simon Griffiths <simon.g@claycrossbs.co.uk> Cc: <freebsd-isdn@freebsd.org> Subject: Re: Identifying where the problem lies. Message-ID: <20011002234412.F78997-100000@server.arg.sj.co.uk> In-Reply-To: <NEBBJFKEHEOLHKCGOHFOMECJDFAA.simon.g@claycrossbs.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Oct 2001, Simon Griffiths wrote: > Hi There, > > We've been using isdn, i4b and freebsd for around ~6months now with a fair > few problem, i.e. its just not stable and now this morning the things died > yet again. You don't say which version you have been running. The version in -stable (and all releases for the last year or so) until shortly before 4.4-release was not in fact very stable; the version from -current installed over a 4.x system has been much more reliable. However, 4.4 is now OK. > A brief description, we are using i4b with userland ppp coupled with natd Any good reason for using separate natd rather than the nat built-in to PPP? (not that this is at all relevant to your problem) > Whats happening is that the AVM!FRITZ PCI card goes off to dial our isp, > Demon Internet and fails with I have been using the same configuration (and ISP) without significant problem, though on my home system I can't use the AVM PCI due to a bug where it corrupts the other B channel and so interferes with voice calls on the same S-bus. > Oct 2 12:02:14 nas ppp[283]: Phase: PPP Started (auto mode). > Oct 2 12:02:17 nas natd[113]: Aliasing to 172.16.0.1, mtu 1500 bytes > Oct 2 12:02:17 nas ppp[283]: Phase: bundle: Establish > Oct 2 12:02:17 nas ppp[283]: Phase: deflink: closed -> opening > Oct 2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: dial req from rbch, > unit 0 > Oct 2 12:02:17 nas isdnd[260]: DBG find_by_device_for_dialoutnumber: entry > 0, cdid in use > Oct 2 12:02:17 nas ppp[283]: Phase: deflink: Connected! > Oct 2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: config entry reserved > or no match > > It's this line which is catching me out and making me think this is a > configuration error. > Oct 2 12:02:17 nas isdnd[260]: DBG msg_dialoutnumber: config entry reserved > or no match That line is explained by the immediately preceding one - isdnd thinks that the entry for rbch0 is already in use. I assume you don't have two copies of PPP running? It's not immediately clear if you just don't have a useful set of logging turned on, or there really is virtually nothing happening at all at the isdn level. Do you see any activity on the isdnd display? > system > > # accounting > # ---------- > > acctall = on # generate info for everything > acctfile = /var/log/isdnd.acct # name & location of accounting file > useacctfile = yes # generate accouting info to file > isdntime = on > monitor-allowed = no # global switch: monitor on/off > > #================================================================= > # User-ppp example > #================================================================= > entry > name = userppp0 > usrdevicename = rbch > usrdeviceunit = 0 > isdncontroller = 0 > isdnchannel = -1 > local-phone-incoming = * > remote-phone-incoming = * > local-phone-dialout = * I have had trouble on one particulary clueless ISDN provider (Cambridge Cable, now part of NTL) when the 'local-phone-dialout' was unset or set to the wrong value (where 'wrong' varied over time!). Try setting this to the full phone number of your ISDN line (including STD and the leading zero). > -- ppp.conf > > isdn: > set phone 0845212xxxx # Purple > # set phone 0845350xxxx # Black > # set phone 0845212xxxx # Green I'm currently using the 08440416672 surftime number; previously I was using 08452120667 (green). > # Take a wild guess at an IP number and let the other side decide > set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0 For Demon, the far end will always be 158.152.1.222, and the near end will always be whatever yourname.demon.co.uk resolves to. Your configuration should work, but it's tidier (and I believe fractionally faster to sign on) if you use the right values. However, again irrelevant to your current problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011002234412.F78997-100000>