I have a RH7.0 server which has been giving me regular unrecoverable disk errors since 6-8 weeks ago. I figured today I had enough time to do something about it. I also figured that as long as I had to rebuild from scratch (after installing a new hard drive) I'd upgrade to RH7.3 -- but I have a few more problems that I figured on. The server is dual homed - eth0 (DEC 2104x 10mbps tulip driver) goes to DSL, eth1 (Realtek 100mbps) goes to internal network. Was running IP Masquerade / IPChains / Apache / sendmail / DNS server fine under RH7.0 I have the following problems: 1) During startup eth0 comes up but eth1 does not. My notes on the previous installation [year ago?] don't show that I did anything special when I installed the Realtek (was previously also DEC 2104x) but that doesn't mean I just didn't write it down. 2) dhcpd won't run, but I assume that's related to #1. Was surprised that dhcpd wasn't loaded during install, as I flagged eth1 as dhcp. 3) how do I know whether IPchains or IPtables is active, and how do I switch. Considering the time involved so far, I think I'd rather delay switching to IPTables and use my existing IPChains firewall for now. Can I still hook it in at the end of rc.local? 4) During install I did answer some firewalling questions (set to medium, custom) -- where is the results of that dialog? 5) If I can use my existing IPChains firewall, that will take care of IP Masquerade -- if not can I have some guidance as to what direction to take. 6) httpd comes up but says "cannot resolve hostname, using 127.0.0.1" - what did I forget to configure? (I haven't touched httpd.conf yet.) 7) issue and issue.net used to be set from rc.local, but no more -- where are they set? I'd like to patch that out and be a bit more anonymous. I'm definitely unconnected until most of these Q's get resolved. Thanks to any who can assist me. Dick
On Mon, Sep 02, 2002 at 06:45:59PM -0500, Richard Goodman wrote: dick> 1) During startup eth0 comes up but eth1 does not. My notes on the dick> previous installation [year ago?] don't show that I did anything dick> special when I installed the Realtek (was previously also DEC 2104x) dick> but that doesn't mean I just didn't write it down. Edit /etc/sysconfig/network-scripts/ifcfg-eth1 and make sure "ONBOOT=yes" is in there. Could you post that file so we can look at it? Run "/sbin/ifconfig eth1". What does that show? If it says "Device not found" then most likely the driver module isn't loading. If not, check /etc/modules.conf. It should have a line for eth1 like so: alias eth1 foobar where "foobar" is the name of the driver module for the Realtek. There are a couple different possibilites for the driver, since they made some different cards with different chipsets. Try ne2k-pci and 8139too. You can also try running /usr/sbin/setup as root and going to "Network configuration". dick> 2) dhcpd won't run, but I assume that's related to #1. Was surprised dick> that dhcpd wasn't loaded during install, as I flagged eth1 as dhcp. What do you mean you flagged eth1 as dhcp? That sounds like you mean "Use DHCP to get the address for eth1". If that is the case, then you want a DHCP *client*, not the dhcpd server. That would be either pump or dhcpcd or dhclient. pump, at the least, should always be installed by Red Hat's installer. If you really wanted a DHCP server, then you would have to install Red Hat's package dhcp-2.0pl5-8.i386.rpm (or my packages for the latest ISC release 3.0.1rc9, available at ftp://angus.ind.wpi.edu/pub/packages/isc/dhcp). You need to be careful that you configure the server correctly to only listen for requests on your internal LAN eth1 (for my packages, edit /etc/sysconfig/dhcpd and put INTERFACES=eth1 in there). dick> 3) how do I know whether IPchains or IPtables is active, and how do I dick> switch. Considering the time involved so far, I think I'd rather dick> delay switching to IPTables and use my existing IPChains firewall for dick> now. Can I still hook it in at the end of rc.local? Red Hat defaults to IPchains, even now. You can put your ipchains statements into /etc/sysconfig/ipchains, and it should be executed automatically at boot. Note that the file format isn't a shell script, but rather the output of "/sbin/ipchains-save". You can run a shell script to set up the rules and then run "/sbin/service ipchains save" to save them for you in the right place. dick> 4) During install I did answer some firewalling questions (set to dick> medium, custom) -- where is the results of that dialog? /etc/sysconfig/ipchains Also, since the ipchains stuff is started as a system service, you need to make sure it is configured to start up automatically: /sbin/chkconfig ipchains on dick> 5) If I can use my existing IPChains firewall, that will take care of dick> IP Masquerade -- if not can I have some guidance as to what direction dick> to take. Well, does your existing IPChains firewall do IP Masquerade? If so, run the existing firewall script and do "/sbin/service ipchains save" to save it in /etc/sysconfig/ipchains. Note that this might not be flexible enough e.g. if you get a dynamic IP address from your ISP, in which case the rules might need to change slightly each time the firewall script is run. If you do use the above method, you'd need to make sure IP forwarding is also turned on in /etc/sysctl.conf. An alternative to using the /etc/sysconfig/ipchains and sysctl.conf stuff is to put your firewall script into /etc/sysconfig/network-scripts/ifup-post. After it runs the /sbin/ipchains commands, it would manually turn on IP forwarding with a "echo 1 > /proc/sys/net/ipv4/ip_forward". dick> 6) httpd comes up but says "cannot resolve hostname, using 127.0.0.1" dick> - what did I forget to configure? (I haven't touched httpd.conf yet.) Set your hostname in /etc/sysconfig/network, and put an entry for your host in /etc/hosts with the right IP address. dick> 7) issue and issue.net used to be set from rc.local, but no more -- dick> where are they set? I'd like to patch that out and be a bit more dick> anonymous. Yes, Red Hat has finally come to their senses and doesn't put anything in rc.local by default anymore. You can just edit /etc/issue and /etc/issue.net with a text editor, and they won't be touched by anything. -- Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886
Charles, Thank you for your detailed response. Your answers to Q 3-7 close those issues. On Q2, yes I really mean to run dhcpd to issue IP#s to selected client machines on the internal network. I'm confident that my dhcpd.conf is correct, and it is called by "dhcpd eth1". This was running under RH7.0. I installed the dhcpd RPM off the 7.3 CD (don't have version info here) Since I first wrote, I went back to the new server and banged my head on it for a couple more hours, remarkably getting answers to some of your questions. 1a) ifcfg-eth1 does have "ONBOOT=yes". I will post it when I get back to the server in the morning. 1b) /sbin/ifconfig shows only "lo" and "eth0" and nothing for "eth1" 1c) There is no /etc/modules.conf file on my machine. 1d) I think the module is 8139too, because when I temporarily pulled the Realtek card (eth1) I got a message during the attempt to startup ETH1 complaining about that module by name (did not get complete message). I did some fiddling with modprobe (which I don't understand) after reading section 2.3 of the Ethernet How-To (Using more than one Ethernet Card per machine). From the startup post screen I can see the Ethernet cards are on IRQs 10 & 9, and from the ifconfig I see that eth0 is 0x8000, but I couldn't get the address for eth1. Do I need it? Thank you for your help; obviously Q1 is the key to getting running now, Dick
On Mon, Sep 02, 2002 at 06:45:59PM -0500, Richard Goodman wrote: dick> 1) During startup eth0 comes up but eth1 does not. My notes on the dick> previous installation [year ago?] don't show that I did anything dick> special when I installed the Realtek (was previously also DEC 2104x) dick> but that doesn't mean I just didn't write it down.
Edit /etc/sysconfig/network-scripts/ifcfg-eth1 and make sure "ONBOOT=yes" is in there. Could you post that file so we can look at it?
Run "/sbin/ifconfig eth1". What does that show? If it says "Device not found" then most likely the driver module isn't loading. If not, check /etc/modules.conf. It should have a line for eth1 like so:
alias eth1 foobar
where "foobar" is the name of the driver module for the Realtek. There are a couple different possibilites for the driver, since they made some different cards with different chipsets. Try ne2k-pci and 8139too.
You can also try running /usr/sbin/setup as root and going to "Network configuration".
dick> 2) dhcpd won't run, but I assume that's related to #1. Was surprised dick> that dhcpd wasn't loaded during install, as I flagged eth1 as dhcp.
What do you mean you flagged eth1 as dhcp? That sounds like you mean "Use DHCP to get the address for eth1". If that is the case, then you want a DHCP *client*, not the dhcpd server. That would be either pump or dhcpcd or dhclient. pump, at the least, should always be installed by Red Hat's installer.
If you really wanted a DHCP server, then you would have to install Red Hat's package dhcp-2.0pl5-8.i386.rpm (or my packages for the latest ISC release 3.0.1rc9, available at ftp://angus.ind.wpi.edu/pub/packages/isc/dhcp). You need to be careful that you configure the server correctly to only listen for requests on your internal LAN eth1 (for my packages, edit /etc/sysconfig/dhcpd and put INTERFACES=eth1 in there).
-- Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- ------------------------------------------------- Richard Goodman dick@goodman1.net ---> Home: (508) 753-DICK
On Mon, Sep 02, 2002 at 10:48:55PM -0500, Richard Goodman wrote: dick> On Q2, yes I really mean to run dhcpd to issue IP#s to selected dick> client machines on the internal network. I'm confident that my dick> dhcpd.conf is correct, and it is called by "dhcpd eth1". This was dick> running under RH7.0. I installed the dhcpd RPM off the 7.3 CD (don't dick> have version info here) Ok, I just looked at the RH 7.3 dhcp package. You can put this in /etc/sysconfig/dhcpd: DHCPDARGS="eth1" Then set the service to start automatically with: /sbin/chkconfig dhcpd on and start it right now with: /sbin/service dhcpd start However, if you have specified eth1, it probably isn't starting due to problem #1. You would see a message from the DHCP server in /var/log/messages to that effect. dick> 1b) /sbin/ifconfig shows only "lo" and "eth0" and nothing for "eth1" Yes, but what does "/sbin/ifconfig eth1" show? By default, ifconfig without any arguments only shows interfaces that are UP. By specifying eth1 explicitly, it will print out that interface whether it is UP or DOWN. Alternatively, you can do "/sbin/ifconfig -a" to show all interfaces, UP or DOWN. dick> 1c) There is no /etc/modules.conf file on my machine. Strange. Is there a /etc/conf.modules? There really should be one of those two. Otherwise, eth0 most likely wouldn't work, either, unless you compiled it into the kernel. dick> 1d) I think the module is 8139too, because when I temporarily pulled dick> the Realtek card (eth1) I got a message during the attempt to startup dick> ETH1 complaining about that module by name (did not get complete dick> message). Ok, so /etc/modules.conf should have at least this in it: alias eth0 tulip alias eth1 8139too dick> I did some fiddling with modprobe (which I don't understand) after dick> reading section 2.3 of the Ethernet How-To (Using more than one dick> Ethernet Card per machine). From the startup post screen I can see dick> the Ethernet cards are on IRQs 10 & 9, and from the ifconfig I see dick> that eth0 is 0x8000, but I couldn't get the address for eth1. Do I dick> need it? These are PCI cards, right? Then you don't need any of that. The PCI BIOS autoconfigures the IRQ's and addresses. What you can do is: /sbin/lspci -v and check to see if your Realtek shows up there. In there it should also have IRQ's and addresses assigned. This command should get things going manually: /sbin/modprobe 8193too After that, check "dmesg" output and see if there are any error messages about loading 8139too. If not, "/sbin/ifup eth1" should start up the network on that interface. -- Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886
participants (2)
-
Charles R. Anderson -
Richard Goodman