Hi,
I need to use RFX9400 with Marantz RC9001 :( due to Marantz extenders are not available for me.
It is possible to connect to RFX9400 from RC9001 via additional WiFi AP (router), and this extender is unvisible for Maratz Extender Discovery Tool, though.
But I'll be happy to connect from RC9001 directly to RFX9400, masquerading it as Marantz RX8001 in Networking mode on WiFi network with SSID Pronto_Network_1, None encryption and Fixed IP of this Extender 0. So, the question is: what IP is assigned to WiFi interface of RFX9400 when it is in standalone mode?

Eugene

Not sure if what you are requesting is possible. Philips Remote to Marantz Extender.

With regard to IP address, no idea. In standalone mode the RFX9400 generates one of 3 SSIDs to which a remote connects.

ProntoNetwork1
ProntoNetwork2
ProntoNetwork3

Thank you, Lundel!

Yes, Pronto_Network_1 on channel 1, Pronto_Network_2 on channel 6 or Pronto_Network_3 on channel 11, all in Ad Hoc mode, without encryption.
In standalone mode after connection to WiFi, remote discovers extender via broadcast as extender discovery tool does, but Marantz can't discover Philips.

Both remote and extender in standalone are in space of 169.254.0.0/16 (automatical private pool), so I think my problem is unsolvable without proxy WiFi AP (aka router), because of extender in standalone has no static IP.

Eigeny, I suspect that the discovery is based on MAC address. as you probably know, in a MAC address the first (leftmost) three HEX characters denote the manufacturer and/or device (e.g Philips Prontos are 00:16:41 or 00:1A:6B, why there are two I have no idea). I would not be surprised if Philips looks only for its MAC tags and Marantz does the same to promote sales of their equipments. That is, make it difficult to use with other brands

How are you doing? long time no see on forums.

Eugene,

FYI, there's an open source project ProntoNIC that you might want to have a look at. Search this forum for last 4 years and google search as well.

Barry,
Both 00:16:41 and 00:1A:6B are reserved is USI (USinternetworking?) - [Link: coffer.com]
As I seen, when Pronto works with extender(s) in standalone mode, it connects to Ad Hoc WiFi network (Pronto_Network_1 etc or Marantz_Network_1(?)), assigns an automatic private ip 169.254.xxx.xxx, and sends the broadcast packets with http(!) data like "Hey, I'm TSU9600 with MAC=XX:XX:XX:XX:XX:XX and IP=xxx.xxx.xxx.xxx, is there an extender with ID=x?". The rest of this fascinated dialogue was left from my Microsoft Network Monitor, due to it was not broadcasted. But it is enough for me: this packet means that Pronto has no extender's IP at this moment, and I can't assume standalone extender by IP at Marantz Wizz.It Ex.
I think, the MACs of Marantz are the same, and only "Philips" and "Pronto" are changed everywhere for incompatibility purposes.
I'm so sorry for invisibility: both my bad practice in English and time devouring crisis moves me off the posts, but I'm trying to track the themes.
Currently I'm working with Crestron, and there are a lot of projects when I use Pronto as remote for Crestron's control processors, and I can only dream for conciliatory research of new control solutions somewhere in warm and sunny paradise, say FL or HI...

Lyndel,
I was surprised with ProntoNIC, thank you! For a year ago I was asked ProntoTeam for protocol Pronto<->extender, due to I was an idea to use RFX9600 as an endpoint control solution at the amount of remote offices in a huge video conference system with Crestron control logic. ProntoNIC looks really helpful for this purpose due to Philips themselves is yet not ready for these integration ambitions.

Seems you need a router in the project anyway, just use the pronto extender in network mode and give it a fixed ip.
The Marantz remote will then be able to talk to it.

dz-,
Yes, you are right - now all is OK, in network mode via additional WiFI AP.
It'll be the pretty spiffy way to convert "Marantz" to "Pronto" via firmware patching, but additional AP is faster and cheaper:)

I would not be surprised if Philips was using SSDP (Simle Service Discovery Protocol) to find the extenders. SSDP is am expired IETF draft originally proposed by MS and HP and is UDP based.