>>Now, I want to get nala routing through ariel to do such things
>>as telnet, ftp, and netscape. But, it doesn't work yet. For whatever
>>reason, nala can't connect to anyone in the outside world, jusy
>>ariel.
>You can't do this by yourself at your end. To do what you want,
>you need to get an "official" network number from the NIC. Hint:
>it'll be a class C network, not one starting with "111." Also,
>you'll need a domain name, again registered with the NIC.
No, all he needs is another IP address from his university. He
definately *does not* need a domain name for connectivity. Domain
names have nothing at all to do with routing packets.
Quote:>After this, you'll have to get your University's network admins
>to route to your network. They may or may not agree to do this.
This is true. The extra IP address he gets from the university
will *have* to have a route set up in the terminal server. This is
probably a very impractical thing for the university admins to set
up, especially since a dynamic IP address is being assigned when he
dials in. If you could setup your own dialup facility on campus,
you could handle this yourself. This is what I have done, regard
http://www.ee.msstate.edu/~simmons/apartment.html for information,
technical notes, and an academic paper I have written.
The more practical solution in your case may be to keep your
network situation like it is, using a "private" IP network at home
that the outside world cannot see, and make the internetted
machine into a proxy server for the non-internetted machine.
This involves running proxy daemon software on the internetted host.
This will allow the non-internetted host to access WWW, etc., through
the internetted host without actually having to be "on the net".
There might also be some similar alternatives, like the 'slurp'
software.
Hope this helps.
David
--
Mississippi State University Electrical and Computer Engineering
Visit my home page! http://www.ee.msstate.edu/~simmons