Re: (PM) IP pool... on a PM3 (5 pools in one network)

Tom Fellenz (tlf@livingston.com)
Thu, 08 Jan 1998 14:55:41 -0800

Two things explained here:
1) x.x.x.255 conflicts.
2) c0 port for ppp dialin as hiccup in 48 address pool size.

--

1) x.x.x.255 conflicts: At 03:29 PM 1/8/98 -0600, Jeff Carneal <jeff@apex.apex.net> wrote: [...] >question I have, is with the .255 address argument below. How is it >exactly that having a user assigned the .255 address doesn't break >everything? I'm not arguing with you, truly. I just would like to >know cuz I'd love to cut my route summaries by 1/4! >

I should have expounded on this more specifically....

I (Tom Fellenz) wrote: > Furthermore, if you decide to use the range of addresses [hosts = .1 - .14] > with masks of 255.255.255.0, including the PMs, there may be an exposure to > the user assigned the x.x.x.255 address. > *** this I have not had the opportunity to check/test.

In other words, if you were to configure the gateway router, the portmasters, and hosts to have IP addresses in the x.x.x.1 through x.x.x.14 range with a netmask of 255.255.255.0, THIS WOULD CAUSE the client workstation that is assigned x.x.x.255 to receive all broadcast traffic. (unverified)

Thus, if you do use the x.x.x.0 subnet, after chopping a network up like I recommended with the original mail, MAKE SURE you use a 255.255.255.240 netmask, or just don't use it.

--

2) c0 port for ppp dialin as hiccup in 48 address pool size:

There was another person who pointed out that the use of the C0 port as a dialin PPP interface will throw a wrench into the pool size allocation for Channelized T1.

I say that only for CT1 because two CT1s = 48 ports, thus 48 addresses. Add one more and you have 49 addresses needed. Arg. Best way to attend to this is by not have anyone dial into that port with a user profile that takes a dynamic address - ONLY Statically assigned address users. IE - an ADMIN user profile using an address out of the unused subnet.

With PRI, its not a problem - two PRIs = 46 ports, plus a c0 = 47. When you set the pool size to 48 to generate the two routes per PM.

Again: PM3-1 assigned address = x.x.x.16 pool = 48 routes = x.x.x.16/28, x.x.x.32/27 PM3-2 assigned address = x.x.x.64 pool = 48 routes = x.x.x.64/27, x.x.x.96/28 PM3-3 assigned address = x.x.x.112 pool = 48 routes = x.x.x.112/28, x.x.x.128/27 PM3-4 assigned address = x.x.x.160 pool = 48 routes = x.x.x.160/27, x.x.x.192/28 PM3-5 assigned address = x.x.x.208 pool = 48 routes = x.x.x.208/28, x.x.x.224/27

'set assigned x.x.x._' 'set pool 48'

To make the issue of 49 addresses moot, you can just leave dip switch 1 up and dialin as '!root' at 9600 and be done with it. :)

--

All the best,

--
Tom Fellenz                                 Technical Support Staff Engineer
Lucent Technologies, Inc                       Data Networking Systems Group
Remote Access Business Unit           4464 Willow Road, Pleasanton, CA 94588
tlf@livingston.com               (800)458-9966 (1) http://www.livingston.com

- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.