inetd.sec problem

[Katherine Gardos_1]

We have been using inetd.sec to allow telnet access. Our file is of the format

telnet allow 65.246.22.3 \
65.246.22.4 \
128.183.213.17 \ etc. with many entries. Everything was working fine until I added ten more entries in the same format, and now only the top entry works. Any suggestions?

Thanks

[Jeff Schussele]

Hi Katherine,

I suspect that an unprintable character has made it's way into the end of line #1 or the start of line #2.
Why dont you try removing *all* characters between those 2 entries and re-add the \ & LF to the end of line #1?

Rgds,
Jeff

[Katherine Gardos_1]

Jeff,

I will try that and see what happens. Thanks!!!

Kathy

[Nguyen Anh Tien]

I recommend you type like
telnet allow 65.246.22.3 65.246.22.4 128.183.213.17
The cause of your problem is CR (carri return) Character.
HTH
tienna

[SureshKumar_2]

hi kathe,

add the new entries followed by another line, you cant keep on add a line more than 120 char ( exact number of charcter i am not remember !)

I too faced same problem earlier, i added the additional ip allowed as another line, got worked.....

telnet allow <.....> ,..,...
telnet allow <......> ,..,..

Hope this meets your requirement.

suresh

[Katherine Gardos_1]

Thanks for your suggestions. Do you mean that the entries can wrap around to the next line without the "\"? What is the 120 limit mentioned? The number of entries I can put on a line (wrapped or not)?

Can you explain how an inetd.sec would be formatted with something like 50 entries? I'm still confused as to whether I need the "\" and how many entries I can put on a line.

Thanks so much!

[John Payne_2]

Kathy,

The lines can wrap without the \'s.

telnet allow 10.0.2-11.* 10.0.254.* 10.2.162.* 10.2.165.* 10.2.182-183.* 10.4
.167.* 10.4.182.* 10.4.184.* 10.5.124.59 10.5.194.59 10.7.218.252 10.7.227.252 1
0.7.228.252 10.7.229.252 10.7.230.252 10.7.231.252 10.7.232.252 10.7.233.252 10.
7.235.252 10.7.237.252 10.7.239.252 10.7.241.252 10.7.243.252 10.7.244.252 10.7.
247.252 10.7.249.252 10.7.249.251 10.7.250.251-252 10.7.251.251-252 10.7.252.251
-252 10.7.253.252 10.7.254.252 10.11.22.* 10.11.88.* 10.11.167.* 10.25.4.253 12
8.187.6.* 128.187.21.* 128.187.22.* 128.187.30.* 128.187.36-39.* 128.187.43.* 12
8.187.45.* 128.187.48.* 128.187.53.* 128.187.57.* 128.187.66.* 128.187.69-71.* 1
28.187.76.* 128.187.78.251-252 128.187.80-81.* 128.187.88.* 128.187.99.* 128.187
.102.* 128.187.130.* 128.187.136-140.* 128.187.142-147.* 128.187.150-151.* 128.1
87.160-163.* 128.187.165.* 128.187.166.* 128.187.167.3 128.187.167.4 128.187.178
-185.* 128.187.192-194.* 128.187.197 128.187.198.* 128.187.200.* 128.187.208-213
.* 128.187.215.* 128.187.216.* 128.187.219.* 128.187.231.188 10.5.217.*

I am not sure about the limit, but here is one of ours, as you can see, it is quite extensive. (More than it needs to be, really.) The format is funny here, but ip's can wrap lines...

I am not sure about the limit, but you can add multiple lines as stated before.

Hope it helps
John

[Katherine Gardos_1]

Thanks so much!!! I have reformatted the entries like your example and everything seems to be working fine.