Discovery across vlans
-
Do you need something in the port there? Or that's probably for the proxy. nevermind.
-
Does IGMPproxy appear to start and run without errors when using VLAN interfaces?
If you shutdown Avahi do the Mac and iOS Spotify clients also fail to find it?
I would guess they are using mDNS and the Marantz app is using UPnP.
Steve
-
@derelict said in Discovery across vlans:
Do you need something in the port there? Or that's probably for the proxy. nevermind.
@stephenw10 said in Discovery across vlans:
Does IGMPproxy appear to start and run without errors when using VLAN interfaces?
It depends on how it should be set up - I played with the settings too much so at the moment, no it doesn't.
If you shutdown Avahi do the Mac and iOS Spotify clients also fail to find it?
Done & Macbook seem to still find it - Android still doesn't.
I would guess they are using mDNS and the Marantz app is using UPnP.
Steve
-
@mtk said in Discovery across vlans:
The Marantz App, does allow manual IP, but still cannot access the device
As Johnpoz mentioned, if there's no gateway, it can't get past a router. Accessing devices on the local network is different from going through a router, as you're trying to do. If there's no gateway setting, that configurable IP address is used instead of automatic discovery.
When working only on the local LAN, the IP addresses is used to determine the MAC address, by using ARP. The MAC address is then used for the actual communications beteen devices. If the device is on a different network, that's recognized by comparing the remote and local addresses, through the subnet mask, to see if they're on the same network. If not, the packets are sent via the gateway address. However, for this to work, both a subnet mask and gateway are needed. With the method Johnpoz is describing, pfSense is acting as a proxy to pass the packets to another subnet.
-
@jknott said in Discovery across vlans:
@mtk said in Discovery across vlans:
The Marantz App, does allow manual IP, but still cannot access the device
As Johnpoz mentioned, if there's no gateway, it can't get past a router. Accessing devices on the local network is different from going through a router, as you're trying to do. If there's no gateway setting, that configurable IP address is used instead of automatic discovery.
When working only on the local LAN, the IP addresses is used to determine the MAC address, by using ARP. The MAC address is then used for the actual communications beteen devices. If the device is on a different network, that's recognized by comparing the remote and local addresses, through the subnet mask, to see if they're on the same network. If not, the packets are sent via the gateway address. However, for this to work, both a subnet mask and gateway are needed. With the method Johnpoz is describing, pfSense is acting as a proxy to pass the packets to another subnet.
Did you see the image I provided, with the IP & gateway & mask?
-
@mtk said in Discovery across vlans:
Did you see the image I provided, with the IP & gateway & mask?
Are those on the receiver or Android/iPhone apps? If the receiver then that's for Internet access for updates, etc., not remote control. That's how my Yamaha is set up. Those apps will require a gateway and subnet mask, if they are on a different subnet. That's in addition to multicast being used. Unless specifically configured or managed with IGMP, multicast packets are not passed by a router.
-
@jknott said in Discovery across vlans:
Are those on the receiver or Android/iPhone apps? If the receiver then that's for Internet access for updates, etc., not remote control. That's how my Yamaha is set up. Those apps will require a gateway and subnet mask, if they are on a different subnet. That's in addition to multicast being used. Unless specifically configured or managed with IGMP, multicast packets are not passed by a router.
Those settings are on the Receiver (web management page) itself, and they set the internet access as well as the local device IP.
The Marantz (Android or iPhone) app, doesn't have the option to set a gateway, just the IP of the device you wish to connect to.
-
@mtk said in Discovery across vlans:
@jknott said in Discovery across vlans:
Are those on the receiver or Android/iPhone apps? If the receiver then that's for Internet access for updates, etc., not remote control. That's how my Yamaha is set up. Those apps will require a gateway and subnet mask, if they are on a different subnet. That's in addition to multicast being used. Unless specifically configured or managed with IGMP, multicast packets are not passed by a router.
Those settings are on the Receiver (web management page) itself, and they set the internet access as well as the local device IP.
The Marantz (Android or iPhone) app, doesn't have the option to set a gateway, just the IP of the device you wish to connect to.
That's what I thought. The receiver needs a gateway & subnet mask to reach the Internet for updates and content, but not for the phone/tablet apps. Since the phone/tablet apps don't have a subnet mask and gateway, they cannot communicate beyond the router. As Johnpoz mentioned, pfSense would have to be configured to act as a proxy for the receiver. In that instance you'd need to manually configure the IP address on those devices.
-
@jknott said in Discovery across vlans:
@mtk said in Discovery across vlans:
@jknott said in Discovery across vlans:
Are those on the receiver or Android/iPhone apps? If the receiver then that's for Internet access for updates, etc., not remote control. That's how my Yamaha is set up. Those apps will require a gateway and subnet mask, if they are on a different subnet. That's in addition to multicast being used. Unless specifically configured or managed with IGMP, multicast packets are not passed by a router.
Those settings are on the Receiver (web management page) itself, and they set the internet access as well as the local device IP.
The Marantz (Android or iPhone) app, doesn't have the option to set a gateway, just the IP of the device you wish to connect to.
That's what I thought. The receiver needs a gateway & subnet mask to reach the Internet for updates and content, but not for the phone/tablet apps. Since the phone/tablet apps don't have a subnet mask and gateway, they cannot communicate beyond the router. As Johnpoz mentioned, pfSense would have to be configured to act as a proxy for the receiver. In that instance you'd need to manually configure the IP address on those devices.
Any hint how to do that?
-
I assume you'd have to set up port forwarding for the protocols used by those apps.
-
@jknott said in Discovery across vlans:
I assume you'd have to set up port forwarding for the protocols used by those apps.
Port forward from where to where?
Traffic between VLAN is wide open (see screenshot above). -
@mtk said in Discovery across vlans:
@jknott said in Discovery across vlans:
I assume you'd have to set up port forwarding for the protocols used by those apps.
Port forward from where to where?
Traffic between VLAN is wide open (see screenshot above).Find out what protocols/port numbers are used, then configure pfSense to forward them to the receiver. It's exactly the same thing as when you have to get past NAT to reach computers on your home network. You determine what has to be forwarded and where.
-
@jknott said in Discovery across vlans:
@mtk said in Discovery across vlans:
@jknott said in Discovery across vlans:
I assume you'd have to set up port forwarding for the protocols used by those apps.
Port forward from where to where?
Traffic between VLAN is wide open (see screenshot above).Find out what protocols/port numbers are used, then configure pfSense to forward them to the receiver. It's exactly the same thing as when you have to get past NAT to reach computers on your home network. You determine what has to be forwarded and where.
well, yes, but we still have the "thing" where it works for iPhone/Macbook (so it's probably open), but not for Android and there are no real blocked entries in the log...
-
@mtk said in Discovery across vlans:
well, yes, but we still have the “thing” where it works for iPhone/Macbook (so it’s probably open), but not for Android and there are no real blocked entries in the log…
Does the app on those devices have settings for gateway and subnet mask? If not, I have no idea how they manage to work through a router.
-
@jknott said in Discovery across vlans:
@mtk said in Discovery across vlans:
well, yes, but we still have the “thing” where it works for iPhone/Macbook (so it’s probably open), but not for Android and there are no real blocked entries in the log…
Does the app on those devices have settings for gateway and subnet mask? If not, I have no idea how they manage to work through a router.
The app is the Spotify (official) app and no, it doesn't even have IP settings - it just "finds" the Marantz.
-
@mtk
May I suggest you ask spotify what differences there are between their working iOS app and their not working Android app in your scenario. -
@jahonix said in Discovery across vlans:
@mtk
May I suggest you ask spotify what differences there are between their working iOS app and their not working Android app in your scenario.I'll do that, but in the meantime, is there any way to see what the iOS/MacOS are doing network-wise vs the Android?
I mean, they are probably initiating some sort of request to see "how is out there", right? -
@mtk said in Discovery across vlans:
is there any way to see what the iOS/MacOS are doing network-wise vs the Android?
You can use Packet Capture record the traffic and then download for viewing with Wireshark. If you have a managed switch, you can use Wireshark directly by configuring the switch for port mirroring.
-
You don't need to configure a subnet or gateway in the phone app for the same reason you need need one in your web browser. It just uses the hosts IP stack with whatever the default route is.
Steve
-
@stephenw10 said in Discovery across vlans:
ou don’t need to configure a subnet or gateway in the phone app for the same reason you need need one in your web browser. It just uses the hosts IP stack with whatever the default route is.
Quite so. Not thinking straight. Not enough beer. ;)
