Ok next time someone asks me to install and setup a network that you got because your brother in-law said it worked at his house .... NOPE not doing it unless I get to design and use the parts I want to use.
/rant
Here is the plan. Getting internet from a Belkin router (1), connection goes to an EnGenius antenna (2) acting as an Access Point, to it's brother antenna (2) acting as a Client Bridge to an EnGenius router (3) acting only as a switch and Access Point for internet connectivity in the barn (no wire connected in WAN port), to the actual cow mixer panel [CMP] (4).
So I learned today that the CMP has a fixed IP of 192.168.200.240 apparently, and requires 3 ports to be opened for it to be accessible by the company providing service to it.
So I setup the whole network using the .200 subnet. Main Belkin router is the only one running a DHCP server ... everyone should be happy. Right ... now during my networking classes we only work with business grade equipment which is a lot more easy to configure. But it seems to make sense.
Now the problems. If I connect to the EnGenius router (3) directly or through wireless, I get an IP from DHCP, internet connectivity and I can ping everyone ...most of the time. I will sometimes lose connectivity with the main Belkin router (unpingable (sp?)). If I connect to the main Belkin router, I can't ping anything after the first EnGenius antenna (AP).
Now this guy did all his cabling and crimping ... and he's a farmer, so I'm buying a cable tester next time so I will test all cables. Are these symptoms related to bad wire? I have a feeling both routers are not playing nice together as I was reading that the specific EnGenius router model was terrible as acting as an AP only.
Any other suggestions/ideas?
Edit : Forgot to add, when I am connected to (3) in the barn, I cannot ping the CMP using the address given to me by the panel maker's tech of 192.168.200.240. Sometimes when I refresh the DHCP table on (1) I will see the panel, next refresh it's gone and I cannot ping. I'll do an IP scan next time to find that sucker.