slackware IP /conecting 2 boxes
 

Hello,
I have to boxes connected to each other via a crossover cable.
They are not connected to the internet. I want them to communicate between each other.
1.How can I assign them static IP (192.168.0.1 and 192.168.0.2)?
It's probably ifconfig, right? What exactly?
2.How do I make them assigned automatically on the startup?

3. how can I connect them to share files and terminals?
thanks

run 'netconfig' as root and select Static IP. Then the ip's and hosts entered at netconfig will be assigned at boot automatically.

I'm running exactly the same setup you are trying to create and also managed to get both of them online via NAT (IP masquerading), just in case you want to try this later on. Here's the thread.

If you're absolutely sure you don't want to connect them to the internet, just edit /etc/rc.d/rc.inet1.conf on both boxes (the addresses are automatically assigned then) and start the SSH daemon by typing /etc/rc.d/rc.sshd start (again, on both). Now you can simply type ssh sycamorex@otherbox to start a SSH session to share files etc ;)

Thanks I did netconfig, however, when I rebooted the computer, eth0 was down. So the first thing I need to do
is to make eth0 up automatically on the startup. How can I do it?
thanks

What says ifconfig -a ?
Ciao

When I reboot the box ifconfig -a
gives only lo interface
then every time I have to issue ifconfig eth0 up
The reason for it is that when I installed slack
I had an integrated network card which wasn't supported,
so I got an pci generic 3m network card which was plugged
in the motherboard after the installation has finished.
I gather I need to edit some file to make it up at the bootup, but which file...?

thanks

I'm not sure why your device is not brought up automaticly. I would open up the /etc/rc.d/rc.inet1.conf to make sure you have your eth0 configured correctly, and also make sure your /etc/rc.d/rc.inet1 is executable. If all else fails, you can always add ‘ifconfig eth0 up’ to your /etc/rc.d/rc.local

regards,
…drkstr

I've had that problem with onboard lans and have had to use nics.

As root do an "lspci" to see if mobo's lan chip and/or your nic is recognised by your system. If it/they are listed under lspci that means that they are recognised by your system but not necessarily that the correct kernel module (if any) is loaded for the network interface.

If you do have the correct module in /lib/modules/kernel_version and it is not being loaded by hotplug, you can load it at boot using /etc/rc.d/rc.modules in which you uncomment the relevant /sbin/modprobe/..... line or add a new line which will load your chip/nic module.

As for assigning ip numbers to your boxes, as root use the command "netconfig" to configure and settings will be good at each boot. For your setup, I would probably just select static ip.

You can use any numbers you like but they should conform to the convention. For lans 192.168.number.number is standard and will never be used on wans.