Nomad in client mode over AP

Hi,

Ok, I know, I read the disclaimer about connecting Nomad via wireless in client mode.  I am running Nomad v2.2.1.9.0.13 on my Macbook (10.9.5).  Connected to an Ion via Netgear GS105 switch.  Any recommendations for experimenting with Nomad in Client Mode for a simple Wireless, static setup with a Win7 Ion v2.2.1.9.0.13. Ethernet Port 1?

Network Setup: Static IP's, Ion 10.101.90.101, Subnet 255.255.0.0.  DHCP Off. Multiconsole ON. sACN On. Default Gateway is greyed out.

If I connect via ethernet cable, Nomand works perfectly in client mode with the Ion.

  • iRFR on my iPad works perfectly with all wireless connections.
  • Belkin N600DB in AP mode: 10.101.90.102 (Nomad doesn't see a master console)
  • Belkin N600DB in router mode: 10.101.90.102 (dhcp on) but still using static IP's. (Nomad see's master console but sync fails.)
  • Netgear w54G router (Nomad client mode works over wireless, but is super laggy)

Same behavior whether a switch is inline or not.  Just looking for ideas with anyone that has experimented with this..

Thanks,

Jason

  • Hi Jason!

    If you must run this with a wireless router, then I would suggest the following:

    Add a default gateway of 10.101.1.1

    Enable the DHCP server on your Ion.

    Set the router into router mode and connect to the Internet port if one is available.  Allow the router to take a DHCP address from the Ion.  

    Set the ETCnomad to take a DHCP address as well.

    I have seen the best luck connecting wirelessly when using this configuration.  Please remember to disable firewall and any antivirus on the ETCnomad computer that may block communication.

    Thank you,

  • Adding to what Sasha said... while this can work in some scenarios, ETCnomad as a client generates a lot more traffic than iRFR (level data, multiconsole connection, etc...). This added level of traffic is one of the reasons why we recommend wired.

Related