> Many thanks to Gary, Josh, and Todd at Livingston for helping to get
> everything working. Now that users are able to CONNECT, a couple of
> questions....
>
> I have "set debug isdn" configured so that I can see the ports as they login.
>
> Watching the console, I have many requests:
>
> IPCP_CONFIGURE_REQUEST on port S4 of 24 bytes:
> <hex data omitted>
> IPCP_CONFIGURE_ACK to port S4 of 28 bytes:
> <hex data omitted>
>
> What is this?
You have debugging turned on...this is normal PPP configuration
information. See Chapter 22 in the Configuration Guide for Portmaster
Products (or the web version at www.livingston.com 8-) Also, check the
archives of the portmaster-users list (links available from the above web
site)...you'll get a good idea of what you should/shouldn't see.
> (I am worried because earlier, Gary at Lucent had confirmed
> all of my port setups when telnetted in, and hours later, ALL Sx ports had
> been reconfigured from LOGIN/NETWORK/SECURITY to merely LOGIN, thus locking
Sounds like somebody didn't do a SAVE ALL before rebooting.
> out my users.... Is the above reconfiguring the ports so that RADIUS users
> can't get in? (It seems to happen during the RADIUS handshaking).
>
Or possibly something's goofed in your radius config...that's a question
for portmaster-radius@livingston.com
> Secondly, if a user is on say, S1, and I do a SHOW S1, I get this:
>
> Remote Host: 198.85.229.42 (a part of my pool)
> Netmask: 255.255.255.255 (this doesn't seem valid to me!)
>
That's exactly what you should see...a single host netmask is all 255's.
> I'm supernetting here.... I've been assigned 198.85.228.0/22 by my
> upstream, four consecutive class C's... I've kept the first TWO for our
> LAN, and am using the second two for dedicated connection customers....
> Thus, the local lan is 198.85.228.0/23 with a netmask of 255.255.254.0.
> Why is the netmask above the "broadcast all" address of quad 255's?
>
Because the netmask only applies to the specific user, not the PM/LAN/WAN.
Depending upon your routing protocol(s) in use and the manner in which you
divided your network, the PM and any other routers in your network should
properly aggregate the class C's to your upstream. In fact, your upstream
should never receive specific routes from you...only an "announcement"
that you are routing for your /24's ("old class C").
-- John-David Childs (JC612) Enterprise Internet Solutions System Administrator @denver.net/Internet-Coach/@ronan.net & Network Engineer 1039 S. Parker Rd. #I-8 Denver, CO 80231 As of this^H^H^H^H next week, passwords will be entered in Morse code. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.