Hi,
My Airconsole XL 2.03 is set to DHCP Client Mode and is receiving a correct DHCP address when connecting to my local wired LAN. When I connect to the Airconsole WiFi SSID, I receive a correct DHCP IP and am able to access the network. When I try to connect via the Airconsole.app 1.2.1 it fails to connect, defaulting to the 192.168.10.1 address. The Get Console app also fails to connect from iOS 7.0.6 devices connected to the Airconsole WiFi. Any suggestions?
Thanks,
Steve
AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mode
Moderator: sergey
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
The AirconsoleOSX app uses 192.168.10.1 if it cannot discover the updated DHCP assigned address via Bonjour. When Airconsole obtains an address from a DHCP server it will change its mDNS/Bonjour broadcast announcement to the new IP address it has been given by DHCP server. Sometimes however this takes over a minute to update on bonjour clients (i.e. Mac running OSX). if you can connect to the the Airconsole web page on its new DHCP assigned IP via the http://airconsole-xx.local address (where xx is last 2 digits of mac as printed on back) then AirconsoleOSX app should populate it in drop down list of Airconsoles to connect to. Restarting AirconsoleOSX can help refresh its Bonjour listing.
Thanks
Simon Hope
Thanks
Simon Hope
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
I can second that problem. Just updated the device to 2.11 and this is the output from AirConsoleOSX:
Detected Airconsole 'AirConsole-76' on 192.168.10.1:3696
Detected Airconsole 'AirConsole-AVS' on 192.168.2.110:3696
Located Airconsole driver
Initial baud rate is: 9600
Serial device /dev/cu.NullModem-1 opened
Attempting to connect to Airconsole (AirConsole-76) on 192.168.10.1:3696
Connect failed
Failed to connect to Airconsole
Device gets an IP from DHCP server or is set to same static IP. Doesn't matter.
ACOSX wrongly assumes to detect AC with wrong hostname on default IP where it doesn't reside.
Correctly detects it on static IP and tries to connect.
Fails to connect and tries dafault IP again.
No connection, no game...
Any ideas?
Detected Airconsole 'AirConsole-76' on 192.168.10.1:3696
Detected Airconsole 'AirConsole-AVS' on 192.168.2.110:3696
Located Airconsole driver
Initial baud rate is: 9600
Serial device /dev/cu.NullModem-1 opened
Attempting to connect to Airconsole (AirConsole-76) on 192.168.10.1:3696
Connect failed
Failed to connect to Airconsole
Device gets an IP from DHCP server or is set to same static IP. Doesn't matter.
ACOSX wrongly assumes to detect AC with wrong hostname on default IP where it doesn't reside.
Correctly detects it on static IP and tries to connect.
Fails to connect and tries dafault IP again.
No connection, no game...
Any ideas?
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
Can you tell me what address your laptop is on when you generated the above output from ACOSX app, and also do you have 2 air consoles running and is one/both of them have APClient running as well?
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
I seem to be having a similar issue. Computer is on the same vlan as airconsole, both are wired and have an ip of 10.0.10.X/24. With AirconsoleOSX the only thing that it will do is connect to 192.168.10.1:3696
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
Do you have Bonjour enabled on your Mac and/or are you blocking mDNS on the network? Is it possible your VLAN is blocking multicast?
AirconsoleOSX needs mDNS to discover the actual address of the Airconsole, otherwise it uses a fallback address of 192.168.10.1.
AirconsoleOSX needs mDNS to discover the actual address of the Airconsole, otherwise it uses a fallback address of 192.168.10.1.
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
i don't think it is blocking as I can see other bonjour devices on the network. Is there any way to manually specify the address to connect to?
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
There currently isn't a way to manually specify an IP address but this is something we are hoping to add in the future.
In the meantime, you may want to try an application such as Bonjour Browser (http://www.tildesoft.com/) to troubleshoot the mDNS issue. You should be able to see the Airconsole and associated services in the list.
In the meantime, you may want to try an application such as Bonjour Browser (http://www.tildesoft.com/) to troubleshoot the mDNS issue. You should be able to see the Airconsole and associated services in the list.
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
So if I wanted to be able to have it connected to the network via the rj45 port and connect to it from outside the network I would need to use the private server?
Re: AirconsoleOSX defaults to 192.168.10.1 in DHCP Client Mo
mDNS/Bonjour will only work in local networks where multicast packets are passed. If you are on an outside network it won't discover the device.
There are several ways to achieve the connection:
- you can use the private server solution which will automatically connect out with no extra config required on your network (it also has a bunch of other nice features like logging and pushing down scripts, etc)
- if you don't need an entry under /dev/ttyXXX or dynamic baud rate control, you can simply telnet into the Airconsole on port 3696 to access the serial port. You will lose dynamic baud rate control, etc unless your telnet client supports RFC2217 so you should pre-set the baud rate in the Airconsole settings.
We are hoping to update the AirconsoleOSX program in the future to allow manual entry of IP address which will be a third way.
There are several ways to achieve the connection:
- you can use the private server solution which will automatically connect out with no extra config required on your network (it also has a bunch of other nice features like logging and pushing down scripts, etc)
- if you don't need an entry under /dev/ttyXXX or dynamic baud rate control, you can simply telnet into the Airconsole on port 3696 to access the serial port. You will lose dynamic baud rate control, etc unless your telnet client supports RFC2217 so you should pre-set the baud rate in the Airconsole settings.
We are hoping to update the AirconsoleOSX program in the future to allow manual entry of IP address which will be a third way.
Who is online
Users browsing this forum: No registered users and 31 guests