Internal Network problem

[pauld]

I have a problem with the network scanning of LMCE for some reason when scanning my internal network LMCE manages to kill the network connection on my Technomate 9100 satellite box. As soon as LMCE is running the network connection goes down.

Is there a way to stop LMCE from scanning a set network address?

Thanks

Paul

[jimmah6786]

Whats the network card make/model piz?

if onboard, what mobo you got?

[pauld]

I am using the onboard lan of a MSI K8N Neo board. The board uses a nVIDIA nFORCE3 chipset.

Thanks

[dopey]

It sounds like LinuxMCE is trying to take an IP address that's already in use. Have you verified the IP addresses in your network?

Also, it seems like you aren't setting this up to be your dhcp server (only one NIC). By default LinuxMCE is going to try to bring on the DHCP server and take over your network... that would fail if miserably if 192.168.*.1 (192.168.80.1 by default) is used and half work if there is another DHCP server on the network subnet (very bad). At that point it can assign an IP address to one device that another device is already using... effectively killing your network.

[pauld]

My network is set up like this.

Internal network uses the onboard lan with ip address as 192.168.0.1. I also have a Netgear lan card in the machine which is used for the outside network this uses the ip address 192.168.1.1 and connects directly to my router 192.168.1.254.

LMCE is my only DHCP device on my network & is set to give addresses for LMCE devices of 192.168.0.50 to 192.168.0.75 and for non LMCE devices 192.168.0.100 to 192.168.0.150. My Technomate satellite box has the ip address of 192.168.0.215.

Even if I turn off the both the DHCP servers for both LMCE devices and non LMCE devices I still get the same problem.

Paul

[dopey]

Hmm, that looks like it would work.

Try manually bringing down each interface:

Code Select Expand

ifdown eth0
ifdown eth1

Then bring them back up one at a time and ping a known address on that interface with:

Code Select Expand

ifup eth0 //or eth1
ping %known address%

If that succeded then next manually launch the filewall script:

Code Select Expand

/usr/pluto/bin/Network_Firewall.sh


That will let us know if the problem is with one particular interface/network driver or a problem with the firewall script.