inetd.sec

[Bush_2]

Hi all,
#cat /var/adm/inetd.sec
ftp deny 192.168.55.21
still I am able to do ftp from the given ip.

Rgrds,
Raj

[Ivan Krastev]

There are 2 possible reasons:
1. ftp is not started fron inetd
2. inetd is not reloaded after changing this file with 'inetd -c'

regards,
ivan

[Yogeeraj_1]

hi,

did you try to run: inetd -c ?

revert!
kind regards
yogeeraj

[Yogeeraj_1]

hi again,

you can also consider installation of the latest inetd cumulative patch -> PHNE_28312


kind regards
yogeeraj

[Bush_2]

hi,
"ftp allow 192.168.55.2" is working.

[Sajjad Sahir]

u have run inted -c

[Safarali]

hi Bush

if your server is listed in ftp.allow file then it will work remove from there and put only ftp.deny

and restart inetd -c as sajjad mentioned

Regards

Safar

[Bush_2]

Hi all,
I have installed the patch PHNE_34823 ( inetd cumulative patch for 11.23) and restarted the inetd also. But still can ftp to the server...
Any more suggestion ?????

[Bush_2]

Could you please help me on this issue ?

[Aneesh Mohan · Accepted solution]

Mr Bush,

Are you checked by applying the server ip in /var/adm/inetd.sec for allow and deny functionality ?

means
#vi inetd.sec ---- on 192.168.1.2
ftp deny 192.168.1.2 #for checking deny fuctionatilty

Note : The ip address should be the server address itself ,just for checking .


#inetd -c

then try ftp to itself ,you may not able to connect to server then we can conclude that "ftp deny"is working .


About your issue ,the ip address reflecting from the client to the server could be a different one .

means :-

Your client ip address could be 192.168.55.2 on client side but while connecting to the server it may reflecting with different ip address ( confirm through syslog after opening a telnet session ,or try ping 192.168.55.2 from server ) due to security implementation on network side.


If this is right then you have to confirm your client mapping ip address on server side and apply inetd.sec accordingly .



Thanks,
Aneesh

[Bush_2]

Thanks