On 2004-01-08, Geoff <geoff_r@canada.com> wrote:
>
> "Cameron Kerr" <cameron.kerr@paradise.net.nz> wrote in message
> news:slrnbvpbko.dsv.cameron.kerr@orloc.localdomain ...
>> On 2004-01-07, Geoff <geoff_r@canada.com> wrote:
>>
>> > Setup:
>> > WAN
>> > |
>> > 3Com <--> Router <--> Other PC

> Sorry the picture didn't work... the WAN is connected to the router (it's
> WAN port) while the PC and 3COM (in the redhat machine) are on the LAN side
> of the router.

Use a monospace font when doing ASCII art.

> I'm wondering if the NIC's (3Com) interrupt is not be noticed/processed..
> (I'm sure there are interrupts as there is traffic in the form of pings
> to/from the PC)

It is possible that the 3Com is dropping interrupts, possibly because of
a driver issue. Might I suggest you try a different card?

Or, get hold of the testing disk (usually a DOS program) which will
perform hardware checking on it for you. I'm told that there are Linux
programs for doing this also.

>> You should also make sure that the Router is set to forward IP.
>> 'cat /proc/sys/net/ipv4/ip_forward' should output 1.
>
> When I run look at /proc/sys/net/ipv4/ip_forward it is 0 - what does this
> mean ?

On the router? Are you sure? It should be set to 1 so that it will
forward IP packets. Usually, that's done by putting the following in
your startup commands, although I imagine Redhat does it differently.

echo 1 > /proc/sys/net/ipv4/ip_forward

--
Cameron Kerr
cameron.kerr@paradise.net.nz : http://nzgeeks.org/cameron/
Empowered by Perl!