After converting our TC network over to rip, things have gone quiet on the dialup front. ISDN multichanel 'just works' and wierd breaks in routing have been pleasently absent from my list of tasks to debug. Unfortunatly, I bragged about this too much and a new issue has popped to the surface. It appears that for quite awhile (as far back as I have logging) we've been handing out 0.0.0.0 as an IP to approx 1% of all connections. We have 3 /24's setup as dynamic public pools on each of 8 TC's. Radius has no knowledge of the ip pools, and as such doesn't specify one to use for connections. At PEAK capacity I show the pools running at about 2/3rds capacity (200 out of 254 in use). Customers auth, and recieve the all 0's ip, hang around for about 30 seconds, and disconnect. No errors are logged by the TC's or our radius server. I'm stumped. This affects just about every type of caller we have, generic analog dyanmic to ISDN with static entries. I'm open to suggestions and appreciate any you can offer. -- Joshua Coombs GWI Networking