- WLUG - wlug.mailman3.com

laser printer?

by Bill Mills-Curran

I'm considering getting a laser printer (I'm tired of buying all those ink jet cartidges that my kids burn through), and I'm interested in recommendataions for low-cost models. (I'm running RedHat 7.2.) HP has a model (LaserJet 1000) for $250 retail. It has a USB connection that the HP web page says is for "window only". ("Non-Windows based operating systems will not be supported.") Any suggestions? TIA, Bill

Sept. 3, 2002

Re: [Wlug] RH7.3 Questions -round 3 (success)

by Richard Goodman

The modprobe did the trick - firewall (with a couple minor messages) and masquerading came right up. Then it took over an hour playing with the firewall which no longer allowed DHCP handshaking to occur (probably behaving right now, was acting wrong under RH7.0) so that I could access mail on this laptop (all the desktops have static IPs) I do plan to switch to IPtables, but I wanted the luxury of learning it first. Thanks to all, especially Charles-- I'm 99% up and definitely functioning again. Dick At 10:43 AM 9/3/2002 -0400, you wrote: >On Tue, Sep 03, 2002 at 10:32:08AM -0400, Richard Goodman wrote: >dick> One unresolved issue - when I issue an IPChains command, the first >time I >dick> get "IPchains incompatible with this kernel" and thereafter "IPChains >dick> protocol not available". The IPChains command is there, as for example >dick> "ipchains -h" works. But I haven't got masquerading or firewalling yet >dick> because of this. > >I've seen this before. The /etc/rc.d/init.d/ipchains script manually >modprobe's the ipchains module. If you aren't using that script, then >you need to do it yourself: > >/sbin/modprobe ipchains > >-- >Charles R. Anderson <cra(a)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(a)mail.wlug.org >http://mail.wlug.org/mailman/listinfo/wlug Richard Goodman dick(a)goodman1.net

Sept. 3, 2002

Re: [Wlug] RH7.3 Questions -round 2

by Charles R. Anderson

On Tue, Sep 03, 2002 at 01:06:58PM -0400, Peter Gutowski wrote: peterg> Many installs of RHL 7.3 will add both ipchains and iptables. It could be peterg> that iptables is running instead of ipchains. I believe that both are peterg> actually compiled as modules so you might need to rmmod the one in order peterg> to use the other. (I've ususally had the reverse problem: I prefer peterg> iptables and usually have to unload ipchains in order to use it. In the peterg> init scripts both are 'by default' set to S08ipchains and S08iptables, so peterg> ipchains loads first. ) Good point. A "/sbin/chkconfig iptables off" will fix that, but in my experience, I've never seen it conflict, as long as there is no /etc/sysconfig/iptables file. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Sept. 3, 2002

Re: [Wlug] RH7.3 Questions -round 2

by Peter Gutowski

Many installs of RHL 7.3 will add both ipchains and iptables. It could be that iptables is running instead of ipchains. I believe that both are actually compiled as modules so you might need to rmmod the one in order to use the other. (I've ususally had the reverse problem: I prefer iptables and usually have to unload ipchains in order to use it. In the init scripts both are 'by default' set to S08ipchains and S08iptables, so ipchains loads first. ) On Tue, 3 Sep 2002, Charles R. Anderson wrote: > On Tue, Sep 03, 2002 at 10:32:08AM -0400, Richard Goodman wrote: > dick> One unresolved issue - when I issue an IPChains command, the first time I > dick> get "IPchains incompatible with this kernel" and thereafter "IPChains > dick> protocol not available". The IPChains command is there, as for example > dick> "ipchains -h" works. But I haven't got masquerading or firewalling yet > dick> because of this. > > I've seen this before. The /etc/rc.d/init.d/ipchains script manually > modprobe's the ipchains module. If you aren't using that script, then > you need to do it yourself: > > /sbin/modprobe ipchains > >

Sept. 3, 2002

Re: [Wlug] RH7.3 Questions -round 2

by Charles R. Anderson

On Tue, Sep 03, 2002 at 10:32:08AM -0400, Richard Goodman wrote: dick> One unresolved issue - when I issue an IPChains command, the first time I dick> get "IPchains incompatible with this kernel" and thereafter "IPChains dick> protocol not available". The IPChains command is there, as for example dick> "ipchains -h" works. But I haven't got masquerading or firewalling yet dick> because of this. I've seen this before. The /etc/rc.d/init.d/ipchains script manually modprobe's the ipchains module. If you aren't using that script, then you need to do it yourself: /sbin/modprobe ipchains -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Sept. 3, 2002

RE: [Wlug] RH7.3 Questions -round 2

by Richard Goodman

Well, I've got the ETH1 and DHCP issues resolved (Thanks, Charles). Did not need to do anything with modules - had misinterpreted the install dialog and ifcfg-eth1 had BOOTPROTO=dhcp. eth1 should have been static with DHCP running from there. One unresolved issue - when I issue an IPChains command, the first time I get "IPchains incompatible with this kernel" and thereafter "IPChains protocol not available". The IPChains command is there, as for example "ipchains -h" works. But I haven't got masquerading or firewalling yet because of this. [Past history of this problem dialog unavailable as I'm on a dial-up laptop] Dick Richard Goodman dick(a)goodman1.net ---> Home: (508) 753-DICK trader(a)goodman1.net ---> Work: (508) 757-3452 voice/fax

Sept. 3, 2002

Re: [Wlug] RH7.3 Questions

by Charles R. Anderson

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(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Sept. 3, 2002

Server For Sale

by JV

Sometime around April I bought a server from Dell. The plan, at the time, was to make it into a webserver and host Wormtown.org and whoever else I could split the bandwidth/hard drive with at a hosting facility in Marlboro. However, it was also in April that I lost my job and then determined that the donations that Wormtown.org collects are not nearly enough to cover the cost of hosting. So, now that I've been unemployed since April. I'm feeling the money start to tighten up and I think it's about time to sell this server. It is a Dell PowerEdge 1650 http://www.dell.com/us/en/esg/topics/esg_pedge_rackmain_servers_1_pedge_165… It is a 1U rackmountable server. It has one PIII 1.13 chip in it It has 512M of RAM (2x256) It has one 36G drive (U160, 10K RPM) The rest of the specs are standard. I've got all the CDs including the Dell Drivers CD and the Red Hat 7.2 Discs that came with it. I've even got Rack Rails. And it does have the cool blue Dell logo that lights up on it. It's been run for about 15 hours total. I believe I paid a bit over $2100 for it. I just priced the same exact machine for $2071 (plus tax and shipping) at Dell.com. I will, of course, take the best offer I can get. I don't want to go any lower than $1500 if I can help it, though. If you're interested, or someone you know might be, contact me. Thanks John V +--------------------------------------------+ |-- "I taught you how to cyclops rock |-- (and then you go and) |-- turn around and break my heart |-- and waste my cyclops time |-- mess up my cyclops mind" |-- |-- - They Might Be Giants |-- |-- John: http://voegtlin.org/~john +--------------------------------------------+

Sept. 3, 2002

Re: [Wlug] RH7.3 Questions

by Richard Goodman

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(a)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(a)mail.wlug.org >http://mail.wlug.org/mailman/listinfo/wlug -- ------------------------------------------------- Richard Goodman dick(a)goodman1.net ---> Home: (508) 753-DICK

Sept. 3, 2002

Re: [Wlug] RH7.3 Questions

by Charles R. Anderson

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(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Sept. 3, 2002