DRS4NXT Ethernet

2Fishy4u

New member
We are planning to integrate a DRS4NXT into an existing Ethernet via a switch for 2 PCs with TZ (no MFDs).
What is the technical background why a separate LAN is required for Furuno products?

In my opinion, this is not necessary with the appropriate network knowledge. If necessary, it would be quite sufficient to define a VLAN.
 
If you use sort of smart switch, make sure igmp-snooping is on for the network with the Furuno equipment. I use a managed switch so I can see & log interface status changes but skip the vlans, even though I have 20 years of experience with vlans.

I'm happy to either use a PC with multiple ethernet interfaces, or a $15 USB gig-ethernet adaptor to do the TZ PC without vlan tagging. Keeping it basic is worth something if it means someone less skilled in the various layers of the OSI model for networking is able to fix or troubleshoot it without advanced help.
 
Thank you for explaining!

Is there any reason why the radar shouldn't be connected to an existing ethernet? Does it require a own physical cabling & switch? Why?
 
A radar would connect to an existing ethernet network for Furuno/timezero PC equipment. We'd normally have a separate ethernet network for Internet purposes. They have different IP addressing / DHCP need that need separation.
A casual approach would be to have wifi for Internet and hardwired ethernet for Furuno instruments. I have PCs with two ethernet ports (connected to different switches), and use one port for Furuno/timezero uses, and the other for Internet/IP cameras/serial port servers for NMEA0183 over IP/remote management.
 
Yes, PC with two different network cards if someone wants the boat network to be accessible by the same PC that is also running TZ PC software. Unobstructed bandwidth and ip structure means it is never a good idea to go against advice. When issues come up the a custom network will always be questionable and harder to get anyone to service a mixed network of "stuff".
 
I just gave the PC a second IP address in the TCP-IPV4 properties (so that timezero could see the Radar which has a static IP address on an odd subnet) then plugged the whole lot in to a switch. Works fine :)
 
I just gave the PC a second IP address in the TCP-IPV4 properties (so that timezero could see the Radar which has a static IP address on an odd subnet) then plugged the whole lot in to a switch. Works fine :)
- one PC or two?
- one Lan-port or two?
- active/managed or passiv switch?
 
I just gave the PC a second IP address in the TCP-IPV4 properties (so that timezero could see the Radar which has a static IP address on an odd subnet) then plugged the whole lot in to a switch. Works fine :)
A reason not to document this as a good configuration is that if you add a Furuno MFD, it may act as a DHCP server and mess up your network (specifically your computer's first IP address which is probably Internet)
 
Back
Top