topic Re: route table and rlogin in Operating System - Linux

route table and rlogin

emily_3 — Sun, 11 Jan 2004 21:36:17 GMT

hello,

My system's platform is linux redhat, and I have two questions:

1. How to permently change the route table, which file? I know i could use # route ....
command to change it temporally, but after I reboot the system, all the changes are gone.

2. I could be able to # rlogin A from this system, but in A system I couldn't rlogin to this system. it always prompt for password, and even I key in the correct password, but still failed. Any file is controlling this?

Thanks.

Re: route table and rlogin

Roshan Sequeira — Sun, 11 Jan 2004 23:51:43 GMT

Add the route commands to rc.local. Take a look at http://linux.ittoolbox.com/documents/document.asp?i=2433 for details.

BTW, on Redhat, static routes added through the redhat-config-network tool persist across reboots. Not sure where these route entries are stored though.

Re: route table and rlogin

Roshan Sequeira — Mon, 12 Jan 2004 00:05:20 GMT

On Redhat, routes added through redhat-config-network are saved in files eth0.route, eth1.route etc. in the /etc/sysconfig/networking/devices directory.

Re: route table and rlogin

Stuart Browne — Mon, 12 Jan 2004 01:05:04 GMT

Depending on what type of route it is depends on where you want to change it.

The simple answer is the rc.local, but that takes control away from any of the GUI type of interfaces that are written.

To do it the 'RH Way', you modify either /etc/sysconfig/network (for a default route), or /etc/sysconfig/static-routes for other partial routes, or interface based routes.

As for the 'rlogin' thing, there are a number of possible reasons.

With the description you've given, it sounds like you're the 'root' user. BY default, a RH system will not allow the root user to log in directly to a pseudo TTY (telnet, rlogin etc.).

There are two ways around this:

modify /etc/securetty, add 'rlogin'.

modify /etc/pam.d/rlogin, remove the line 'auth required /lib/security/pam_securetty.so'

Both of these options have the same end goal: allow root to 'rlogin' via a pseudo-tty.

If it isn't the root user, and you're still getting the error, then I'm picking it's the permissions on your .rhosts file. It should be 600 (-rw-------).

Have fun.

Re: route table and rlogin

emily_3 — Mon, 12 Jan 2004 06:27:03 GMT

hello Stuart Browne,

Thanks. it did work.

i would like to know what's the purpose to add "rlogin" entry in /etc/securetty?
Where can I find the detailed information about the different "auth entry" inside /etc/pam.d/rlogin?

Regards.

Re: route table and rlogin

Stuart Browne — Mon, 12 Jan 2004 19:28:58 GMT

On a RH system, /usr/share/doc/pam-*/txts/ has all the documentation in text format (there's HTML and Poscript there too!).

The pam_securetty.so has hardwared 2 (or 3?) overrides. rlogin, rsh are two of them, to allow those services to go in as root (which kidna defeats the purpose, but hey!).