Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This question is somewhere between networking and applications.
I have a lab environment in which I'd like to create several virtual "dumb terminals".
I would like to install several ethernet cards and then configure shells that are statically associated with network cards. Shell instance A would be always and only associated with (for instance) Eth1, while shell B would be with Eth2.
It would be ideal if, other than these 2 special shells, anything else running on the machine would use Eth0. I could then have Eth0 hooked to the LAN outside the lab.
It is necessary to have separate NICs. Multiple IP addresses through a single NIC won't do. The NICs will be cabled to different connections.
It is necessary to have this work within a single account (which could be root). Need to be able to switch between "terminals" at a mouseclick, not by logout/login.
The special terminal shells must be able to run at least ping, traceroute, and telnet.
I think the crux of the matter is associating a particular network device with a particular shell instance.
I am using SUSE 8.1/KDE. If changing distros helps solve the problem, I'll do it.
I wonder if you could just clarify a couple of things. When you say you want a virtual terminal associated with a network card do you mean that when you use for example tty3 it would only be able to see eth1 or something like this?
If I understand your question, I don't think you can acheive the results that you want.
My only idea for what you can do is to start looking through the man page for bash and some of the networking utilities.
Yes, that's it exactly. If for instance, I attempted to ping through tty3, that attempt should fail if it can't do so via eth1. It should not, failing on eth1, attempt to use some global-to-my-machine default gateway.
You're probably right about burrowing into the bash or similar info. Thanks.
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
why? linux supports multiple terminals.. and multiple network cards, but I don't think you can do that you COULD however use serial hardware for 'dumb terminals' but i'm not sure that's what you want.
What you are talking about is probably possible, but you're most likely going to have to write it yourself. good luck
I just thought of something that may work. You could try writing wrapper shell scripts for the commands you want to run to explicitly use certain interfaces. and then alias these scripts to the commands. or something like this.... maybe use a trick with the path.