On Sat, 14 Oct 2000, Dave Kempe wrote:
> also for ipchains i've found it helpful to use ipchains -L -n
> prints out the current chains and their rules etc.
> useful if somehting is stuck in there then you can flush them with
> ipchains --flush
Many thanks to all who replied to this - the problem is now solved,
but in a bloody wierd manner.
As you know, everything internally could communicate, and the
gateway machine could communicate with the 'net. All routes and
IPCHAINS rules were correct....
Much scratching of various bodily orifices ensued...Aided, I might
add, by suggestions from David, George and Graham...
In frustration, thinking I had broken something (not impossible in
this house at the moment - it's amazing what damage a 7 month old
with a passion for keyboards can do !!), I was about to blow the
gateway machine away and re-install, when I checked the rc.config
file.
In the line INITRD_MODULES, it was loading "ncr53C8xx", the SCSI
module for my drive / cd-rom, but no-where was the network driver
"pcnet32" mentioned (the machine is a Compaq Prosignia 300).
Keep in mind that I could still contact EVERYTHING internally, even
without pcnet32 loaded.
Edited rc.config, rebooted (to be sure), and it's now working.
I guess it's possible thaqt some sort of support for this interface
is built into the kernel, but not "full" support for forwarding,
etc. reasonable or not ?
Anyway, thanks all for your help.
Jon
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
