Forum Home
Press F1
Thread ID: 70014	2006-06-19 10:12:00	Linux Mepis, setting machine up as a NAT	personthingy (1670)	Press F1

Post ID	Timestamp	Content	User
464527	2006-06-21 22:59:00	Shouldn't have to remove dhcpd3 - it shouldn't do any harm. The screen shot is just of the interrupts used so can't tell too mcuh from that. I have struck NICs before that all appears right but will not transmit - could be the case here??No, both work, or at least both can work if the system chooses to use them as eth0. I turned Debs on this morning, and had to swap the network cable over again. Eth0 is now the PCI card, as opposed to the onboard NIC... Deep breath. positive thoughts *sigh*	personthingy (1670)
464528	2006-06-22 06:02:00	It is a bit hard trying to figure out what is happening here! How about trying to set the IP numbers from the command shell (root): ifconfig eth0 203.97.119.70 ifconfig eth1 192.168.0.1 Then restart the network services - not sure how to in your version but in RedHat based ones: service network restart or /etc/rc.d/init.d/network restart	johnd (85)
464529	2006-06-22 06:20:00	One thing you need to do is have eth0 and eth1 assigned permanently to one NIC each. The modules.conf situation seems to be a bit confused between distributions, but have a look at /etc/modules.conf . It might tell you to put any additions of yours in another file. Ideally your NICs will be from different manufacturers, so will use different modules. Then alias eth0 drivermodule1name and alias eth1 drivermodule2name will do it. I'm not sure how to make it happen for two identical cards. ;)	Graham L (2)
464530	2006-06-22 08:07:00	It is a bit hard trying to figure out what is happening here! How about trying to set the IP numbers from the command shell (root): ifconfig eth0 203.97.119.70 ifconfig eth1 192.168.0.1 Then restart the network services - not sure how to in your version but in RedHat based ones: service network restart or /etc/rc.d/init.d/network restart personthingy@1[~]$ su - Password: root@1[~]# ifconfig eth0 203.97.119.70 root@1[~]# ifconfig eth1 192.168.0.1 root@1[~]# /etc/init.d/networking restart Reconfiguring network interfaces...ifup: interface lo already configured ...: Unknown server error Failed to bring up eth1. done. root@1[~]# OK, so something about eth1 isn't happy today... One thing you need to do is have eth0 and eth1 assigned permanently to one NIC each. The modules.conf situation seems to be a bit confused between distributions, but have a look at /etc/modules.conf . I dont seem to have a modules.conf file as such, but i do have a "modules" file # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a `#', and everything on the line after them are ignored. and thats it.... Theres a modules.conf.old that offers this gem ### This file is automatically generated by update-modules # # Please do not edit this file directly. If you want to change or add # anything please take a look at the files in /etc/modutils and read # the manpage for update-modules. UPDATE-MODULES(8) Debian UPDATE-MODULES(8) NAME update-modules - obsolete command SYNOPSIS update-modules DESCRIPTION update-modules is an obsolete command. In its current form it will exe- cute /sbin/update-modules.modutils (the old update-modules program pro- vided by the modutils package) if it exists and do nothing else. Note that the file /etc/modprobe.conf is not the exact equivalent of /etc/modules.conf. It is not required for module-init-tools and is not generated any more. In fact, most people should not create that file since /etc/modprobe.d/* would be ignored in this case but Debian pack- ages store their additional configuration files in /etc/modprobe.d/. SEE ALSO depmod(1) modprobe(8) modprobe.conf(5) BUGS Not the most helpful, but looking in /etc/modutils led me to these: # Change the name of the interface to a standard one options rt2400 ifname=eth%d # Change the name of the interface to a standard one options rt2500 ifname=eth%d so i assume i change "eth%d" to "eth0" and "eth1"?	personthingy (1670)
464531	2006-06-22 08:12:00	.	personthingy (1670)
464532	2006-06-22 09:30:00	Not sure - distributions seem to be different in this area . As a general rule changing things cannot do too much harm as long as you can get back to where you started . A good technque before you start is: cp /etc/modutils /etc/modutils . orig or similar so that the original file is always recoverable .	johnd (85)
464533	2006-06-22 10:16:00	Well... At least that didn't break anything :D /etc/modutils/rt2400-base # Change the name of the interface to a standard one options rt2400 ifname=eth0 /etc/modutils/rt2500-base # Change the name of the interface to a standard one options rt2500 ifname=eth1 Same error though root@3[~]# /etc/init.d/networking restart Reconfiguring network interfaces...ifup: interface lo already configured ...: Unknown server error Failed to bring up eth1. done. I'll see what happens when i boot up next time, if the cards swap roles or not, hopefully that fixes them.	personthingy (1670)
464534	2006-06-23 03:12:00	I did say that the handling of modules varies. ;) But you did find the information. You will need to restart the network services after making any changes. Booting is one way to do that. :)	Graham L (2)
464535	2006-06-28 00:04:00	I concede, i'm defeated. In the end we got a machine running puppy Linux to do the job as an expererment. It took less time to squiz round puppys menu and tick the right boxes than it did to run the network cable round the desk and boot up the 2 machines. Unfortunately the puppy machine is in the sleepout which is some distance from the house, and it's not practical to run another 50 metre cable. Also Ziggy has the habit of changing OS every couple of days. I've come to the conclusion that Mepis, is very client/end user orientated and utterly hopeless for anything serverish. I suppose that is some sort of progress. :groan: I've taken the extra NIC out of the Mepis machine, and will continue this project when i get the next machine up, one made for the purpose, and probably running puppy, because it's a great wee system! :D Thanks to all who helped. Such a pity the project turned out to be pushing stuff up hill with a one tooth rake.	personthingy (1670)
1 2 3