Setting up an Alias. 1

[butchrecon]

I have my LINUX server with an IP of 192.168.100.1 and I am on a 192.168.2.x IP scheme. I need to be able to telnet or ftp to the LINUX server, how do I set up an alias to my inhouse network? James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[Guest_imported]

You can enable ftp and telnet by editing /etc/inetd.conf and unhashing ftp and telnet

 

[butchrecon]

They are enabled. I just cant reach them from my network.
James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[ifincham]

Hi,

There must be a gateway on the 192.168.2.x subnet that knows the route for it to work. You would just add a route command like this

/sbin/route add -net 192.168.100.0 netmask 255.255.255.0 gw 192.168.2.5

(where 192.168.2.5 was a gateway machine / router which a path to the 192.168.100.x subnet)

That command would be from linux again but you can do the same thing from windows with slightly different syntax. If you have only one gateway / router just set the default route to the IP address of that.

Regards

 

[butchrecon]

No gateway or router. Its a local network. I am setting up a custome server with a specific IP. I just want to be able to telnet or ftp in from my machine. does the above still apply? James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[marsd]

You are on different networks-your windows/linux situation is a little strange:try to subinterface(alias)your linux machine:
ifconfig eth0:1 192.168.100.? up
#routing
echo 1 > /proc/sys/net/ipv4/ip_forward

route add -net 192.168.100.0 netmask 255.255.255.0 gw aliased interface ip..
and add a reverse route the other way.

Or just run routed -t for a minute and look at the routing output for hints.

 

[butchrecon]

Whoah. You are way above my head. I know little of LINUX. I am the one in my office designated to get this going and i have little LINUX knowledge. Thats why I am asking. I know Windows and networking, just not LINUX. I need more "common man" explanations. Thanks for the help. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[marsd]

sorry bout that..
You need to somehow have a listening interface on the same subnet as the windows machines. Since you need to listen on two networks at the same time you must have routes:
broadcasts do not cross broadcast domains and networks are the delimiters of broadcast domains.
Make sense?

In linux to set up routing you must (at least):
echo 1 > /proc/sys/net/ipv4/ip_forward; to enable
forwarding packets if you will route from network to network.

your linux ethernet interface can be aliased, or
subinterfaced with a command similar to this:

ifconfig eth0:1 ip address netmask state

where ifconfig is the command ; eth0:1 is the subinterface,
address is the ip address, netmask is the subnet mask; and
state is up or down. Very flexible.

So if i were in your shoes i would create a subinterface to listen on the target network, route packets, and
run the routed daemon with the -t option if i had trouble
seeing where my routes needed to be, or jut run routed anyway as a dynamic routing solution.
I have had so-so luck with routed, but it has often shown me oversights in my routing that i was able to fix manually.
Try this url:

http://www.bestlinux.net/en/2000/manual/node367.html

on the windows side:
I would (as explained above)use linux as my router.
It is the only way to do it in this situation unless
you are using win2k/nt for proxy/routing..in which case
you only need to connect to the local linux subinterface for your ftp and telnet needs.

I am assuming throughout this that there is some
really important reason for your linux machine not to be on the same subnet as the windows machines....if there
isn't just configure linux on the same subnet,
or if you are using dhcp run the dhcp client for linux.

 

[butchrecon]

I will be asking some questions in the morning when I get back to the office. The machine is for a customer with specific IP needs. I will be running samba and some proprietary software that makes switching IP schemes difficult. So I just need to be able to telnet into from time to time from my desk to do what I need to do instead of going to the server and back constantly. I will look into your suggestions in the morning. Thanks James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.