Myst <[EMAIL PROTECTED]> writes:
> But regardless, RedHat's not giving customers who are using their
> operating system technical support just because they didn't buy it
> specifically from them is pretty shabby - pretty much the equivalent
> of HersheysSquirt Inc telling a handicapped customer they won't help
> them open their child-proof squirtbottle because the product was
> purchased at K-Mart and not directly from them.
No, it isn't the same. Redhat makes money nearly only by helping that
handicapped customer! The whole idea behind selling free software is
to act like a nursery and make money by helping people that can't help
themseves. That's what support is.
> (Original setup still in place - I want to keep this config):
> ZELDA:
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window Use Iface
> 192.163.2.0 * 255.255.255.0 U 1436 0 103 eth0
> 127.0.0.0 * 255.0.0.0 U 1936 0 12 lo
> default 192.163.2.254 * UG 1436 0 0 eth0
> (192.163.2.254 is Pandora, the hub)
Is the 192.163.2.0 net really yours? It's not a network reserved for
private use! (That's 192.168.0.0!)
> PANDORA:
> Kernel IP routing table (before route deletion)
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 198.109.192.42 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
> 192.163.2.0 0.0.0.0 255.255.255.0 U 0 0 7 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 3 lo
> 0.0.0.0 192.163.2.0 0.0.0.0 UG 0 0 29 eth0
> 0.0.0.0 192.163.2.1 0.0.0.0 UG 1 0 0 eth0
Very strange. Take a look at some scripts and subdirectories in /etc,
probably /etc/init.d...
> PANDORA:
> Kernel IP routing table (after route deletion)
> 192.163.2.0 0.0.0.0 255.255.255.0 U 0 0 7 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 3 lo
> (NOW I can telnet out)
Even more strange. ;-) I think you need a default route to the outside
world (hopefully the ppp connection is already up, otherwise these two
routes should be set by the pppd):
route add 198.109.192.42 ppp0
route add default gw 198.109.192.42
Probably you have to activate IP-Forwarding and IP-Masquerading also,
but I don't know how this is done on Redhat (I'm Debian user
;-)). Probably using something along this lines:
modprobe /lib/modules/2.0.34/net/ip_forward.o
modprobe /lib/modules/2.0.34/net/ip_masq.o
(That's the basic way and probably should be done by the pppd anyway,
I don't know if Redhat has some special command to make sure this is
done at the next boot again...)
> > Either shut down the news server vi "chkconfig innd off", or uninstall the
> > entire news package via "rpm -e inn". Either way, reboot after the change.
> Okie, one problem solved (I hope).. thanks. =) I got this though:
> cannot remove /var/spool/news/innfeed - directory not empty
> cannot remove /var/spool/news - directory not empty
> cannot remove /var/run/news - directory not empty
> cannot remove /var/log/news/OLD - directory not empty
> cannot remove /var/log/news - directory not empty
> cannot remove /var/lock/news - directory not empty
> cannot remove /var/lib/news/innd - directory not empty
> cannot remove /var/lib/news - directory not empty
> cannot remove /usr/lib/news/bin/control - directory not empty
> cannot remove /usr/lib/news/bin - directory not empty
> cannot remove /usr/lib/news - directory not empty
> cannot remove /etc/news - directory not empty
> Is it OK to just delete those directories now? Or does anything else
> look for them? <Just don't wanna have to go through all this again!> :P
Should be ok to delete them. (Probably some script called from cron
looks for them, but if that stops working it doesn't hurt, news is off
anyway ;-))
> Thanks for your time and help! =)
No prob, but: YMMV! ;-))
Regards, Ulli
