Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Been following the book from Paul Scheer. Trying to connect oldcomp to newcomp.
[dad1@trouble dad1]$ /sbin/route -v -e -n
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
How do I get at newcomp, set up similarly?
Something is missing here. Do I need to declare this computer as server or whatever. Do I need to givemyself access rights to newcomp.
Any tips anyone?
Any tips on setting up dhcp? I just downloaded the newest version.
Can't be that difficult to connect oldcomp to new comp over eth0?
I can connect to the net, and eth0 is active on boot!
It should be quite easy. The easiest way is to give both machines network card static ip addresses, using ifconfig, like this :
ifconfig eth0 192.168.1.1 (on the first machine)
ifconfig eth0 192.168.1.2 (on the other machine)
and connecting the two machines with a crossover cable, from network card to network card. If you have a straight cat5 cable you will have trouble, you need a crossover cable for this. There's the lan all ready to go. Assuming you are using two linux machines. Perhaps you should post more detail as to what you are hoping to achieve and if the other computer is a windows box or not.
Well, thought it must be easy. I'll try it. You don't use dhcp yourself? I have a magazine, Linux User. It explained how to set up dhcp.conf. But I keep getting errors. I don't know what to put for host name, and it asks for dnns-update-style.
If I do it as you say, how do I actually get at newcomp from old comp? Is it sort of mounted under / somewhere, so that kde just sees it? What about access permissions from one comp to another. And more importantly, how do I get at oldcomp and the modem to access the net from newcomp, which is not on connected to the net directly.
I would like to get dhcp going, so that if I connect another comp up at some point, I just plug it in tell the net wizard to use dhcp, et voila.
Can anyone send me an example of a functioning dhcp.conf?
And what is dhcp.lease. dhcpd can't find it, and neither can locate. It's not there. Not on old or new comp.
New comp is the client I suppose, and runs on Mandrake. If I set it to dhcp, it asks for a host name. Is that the ip address of oldcomp, or it's name, trouble.oldcomp??
Thanks for any tips!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.