forum.censornet.com

[sb]

Have set up CN 3.3r5 on P4 CPU with 512Mb RAM in bridge mode on trial basis. (have ISP firewall upstream)

Now want to roll this out to more users to test scaleability, stress the system etc in case we need different hardware.

More RAM is likely, but we are wanting to replace the 100MB NIC with a Gb NIC as all traffic is going through this (potentially 100-200 users in long run).

Current 100MB NIC is RTL8139 - works OK.
Replaced with Netgear GA311 GB NIC - RTL 8169 - recognised on boot but when CN starts up get kernel error. (did once succesfully boot and scan for driver - then got kernel error - hence now seems to recognise RTP8169 on boot)

Limited knowledge of Linux OS, kernels etc - could not find similar problems in forums, though apols if we missed it.

Is RTL8169 supported? Anyone else using one?
If yes, any suggestions why kernel error and what might be done about it? (laymans terms please, if it involves CLI as root user)

TIA

[stonefish]

Well, there is an r8169.ko file in the modules tree so I suspect its supported.

Try editing the file /etc/modules and removing the lines therein, then reboot.

Now run the setup program and use setup to re-detect your cards. That should fix you.

Regards
Neil
_________________
Neil Briscoe
Adelix Limited
neil.briscoe@adelix.com

Adelix Limited - WiFi, VoIP, CensorNet, Linux solutions and consultancy.
www.adelix.com www.censornet.com

[sb]

Thanks for prompt response.

Have replaced 100MB NIC with Gb NIC and deleted all lines from etc/modules

scan for NIC - found rtl8169 driver and set ip address etc and bridge mode.

NIC has flashing lights and shows FD Gb connection with switch.

modules file only shows rtl8169

try pinging to and from CN - nothing. Eventually falls over - various messages about rtl8169 interrupt and then finally 'kernel panic: fatal exception in interrupt'

Does this suggest anything? (other than it doesn't work! )
TIA

[stonefish]

Sounds like a foob'd driver to me. We didn't write it in the first place - but we might be able to fix it - at a cost. You can send an email to sales@adelix.com and I suggest you include a link to this thread. Then they'll know whats been tried already.

Regards
Neil
_________________
Neil Briscoe
Adelix Limited
neil.briscoe@adelix.com

Adelix Limited - WiFi, VoIP, CensorNet, Linux solutions and consultancy.
www.adelix.com www.censornet.com

[sb]

Might it be simpler to get a GB NIC that is known to work with CN?

Any recommendations?

[Guest]

Hi,

The Intel Pro 1000 NIC is supported by CensorNet. You can buy them from Dabs www.dabs.com quicklinx no. 3N7BWS

Regards,

Tim

[stonefish]

For the benefit of others, we recommend the Intel e1000.

Either you or your colleague phoned the office - please don't do that and ask here - we work in a distributed set of offices and end up sending echoes around the place asking the same questions over and over until everyone is up to date. Rather like a bridged network with no spanning tree suffering from a topology loop.

(See what I mean )

Regards
Neil
_________________
Neil Briscoe
Adelix Limited
neil.briscoe@adelix.com

Adelix Limited - WiFi, VoIP, CensorNet, Linux solutions and consultancy.
www.adelix.com www.censornet.com

[sb]

Sorry about parallel contact - colleague and I in different offices were trying to track solution from different ends in ignorance of each other.

Will endeavour to coordinate in future. (not sure of human equivalent of STP - maybe conversation )

In meantime - trying to source an Intel NIC.

Many thanks for all your help - from both of you.

[stonefish]

Conversation is definitely good, we had lots here - thats what caused the echoes.

Regards
Neil
_________________
Neil Briscoe
Adelix Limited
neil.briscoe@adelix.com

Adelix Limited - WiFi, VoIP, CensorNet, Linux solutions and consultancy.
www.adelix.com www.censornet.com