Reply
Established Member
Posts: 1,408
Registered: ‎10-01-2014
Kudos: 695
Solutions: 66

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

See the first post in this thread...

Please help the community find useful posts and solutions by using the "Kudos" and "Accept as Solution" buttons!
New Member
Posts: 20
Registered: ‎05-06-2016
Kudos: 6

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

Hi All,

 

I'm not sure if this was covered yet, but I recently put a USG into my network. I was able to install bcast relay on the USG, but am unsure if the settings will stick after power cycle or a reprovision from the cloud key.

 

Anywho, just wanted to let folks know that bcast relay works on USG if you directly ssh into the USG.

 

Cheers,

Dave

Emerging Member
Posts: 98
Registered: ‎06-03-2017
Kudos: 2
Solutions: 3

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

Does this broadcast relay service also work on a Edgerouter X(latest firmware) ?
I want to use this service for my sonos. Does sonos also uses the port 1900 or do i have to use another port(s)?

How can i installed the service , by logging in the router with putty?

 

Thanks

Emerging Member
Posts: 69
Registered: ‎05-07-2016
Kudos: 19
Solutions: 5

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

[ Edited ]

Yes, it works for ER-X but it's a different file (different platform): https://community.ubnt.com/ubnt/attachments/ubnt/EdgeMAX/143278/1/ubnt-bcast-relay_ER-X.tgz

 

Then go back to the 1st page and read the first post accepted as solution where britannic cover step by step how to install it.

Emerging Member
Posts: 98
Registered: ‎06-03-2017
Kudos: 2
Solutions: 3

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

thanks!

 

I guess i use your link in the install-procedure?

I want to relay between two vlans switch0.10 and switch0.20. Is this also possible by using

 

set service bcast-relay id 1 interface switch0 vif 40 or

set service bcast-relay id 1 interace switch0.40 ?

Emerging Member
Posts: 69
Registered: ‎05-07-2016
Kudos: 19
Solutions: 5

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

Yes, you must use the ER-X link to download the correct version (or will just not work), everything else is the same (same thing but compiled for the ER-X platform).

 

If you use the "auto complete" option by pressing TAB while writing your set command you will see the available options. It uses the standard "switch0.10" way to reference VLANs.

Emerging Member
Posts: 98
Registered: ‎06-03-2017
Kudos: 2
Solutions: 3

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

[ Edited ]

Ok, thanks. I am going to test it and put my controller and sonos in vlan10 resp. vlan20. THANKS!!!!!

I installed it without errors, with:

 

putty

1) cd /tmp
2) curl -o ubnt-bcast-relay.tgz https://community.ubnt.com/ubnt/attachments/ubnt/EdgeMAX/143278/1/ubnt-bcast-relay_ER-X.tgz
3)  cd /tmp
4)  sudo tar zxvf ubnt-bcast-relay.tgz
5)  cd ubnt-bcast-relay/
6) sudo chmod 0755 ./install.sh
7) sudo ./install.sh

8) configure
set service bcast-relay id 1 description 'Sonos listener'
set service bcast-relay id 1 interface switch0.10
set service bcast-relay id 1 interface switch0.20
set service bcast-relay id 1 port 1900

commit
save
exit

 

 

 

Emerging Member
Posts: 98
Registered: ‎06-03-2017
Kudos: 2
Solutions: 3

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

[ Edited ]

my sonos controller(PC) in VLAN10 does not find the sonos bridge in VLAN20...on a edgerouter X

i installed the script (for the edgerouter x) and  i added port 1900, 1901 and 6969 to the broadcast forwarder...

 

still no sonos found.....

 

 i do see the three services 1900, 1901 en 6969

 3567 ?        S      7:13 /opt/vyatta/sbin/udp-bcast-relay 1 1900 switch0.10 switch0.20
 3570 ?        S      0:00 /opt/vyatta/sbin/udp-bcast-relay 2 1901 switch0.10 switch0.20
 3574 ?        S      7:02 /opt/vyatta/sbin/udp-bcast-relay 3 6969 switch0.10 switch0.20

 

I am out of options.... Somebody?

 

Hera is my config....


firewall {
    all-ping enable
    broadcast-ping disable
    group {
        network-group pvk_vlans {
            description "VLANS die moeten worden beschermd tegen guest access"
            network 192.168.10.0/24
            network 192.168.20.0/24
            network 192.168.30.0/24
        }
    }
    ipv6-receive-redirects disable
    ipv6-src-route disable
    ip-src-route disable
    log-martians enable
    name VLAN40_LOCAL {
        default-action drop
        description Services
        rule 10 {
            action accept
            description "Accept DNS"
            destination {
                port 53
            }
            log disable
            protocol udp
        }
        rule 30 {
            action accept
            description "Accept DHCP"
            destination {
                port 67
            }
            log disable
            protocol udp
        }
    }
    name VLAN40_OUT {
        default-action accept
        rule 10 {
            action accept
            description "Accept Established/Related"
            log disable
            protocol all
            state {
                established enable
                invalid disable
                new disable
                related enable
            }
        }
        rule 20 {
            action accept
            description "Accept controller AP"
            destination {
                address 192.168.10.10
            }
            log disable
            protocol all
            source {
            }
        }
        rule 30 {
            action drop
            description "Drop LAN_NETWORKS"
            destination {
                group {
                    network-group pvk_vlans
                }
            }
            log disable
            protocol all
        }
    }
    name WAN_IN {
        default-action drop
        description "WAN to internal"
        rule 10 {
            action accept
            description "Allow established/related"
            state {
                established enable
                related enable
            }
        }
        rule 20 {
            action drop
            description "Drop invalid state"
            state {
                invalid enable
            }
        }
    }
    name WAN_LOCAL {
        default-action drop
        description "WAN to router"
        rule 10 {
            action accept
            description "Allow established/related"
            state {
                established enable
                related enable
            }
        }
        rule 20 {
            action accept
            description IKE
            destination {
                port 500
            }
            log disable
            protocol udp
        }
        rule 30 {
            action accept
            description L2TP
            destination {
                port 1701
            }
            log disable
            protocol udp
        }
        rule 40 {
            action accept
            description ESP
            log disable
            protocol esp
        }
        rule 50 {
            action accept
            description NAT-T
            destination {
                port 4500
            }
            log disable
            protocol udp
        }
        rule 60 {
            action accept
            description PPTP
            destination {
                port 1723
            }
            log disable
            protocol tcp
        }
        rule 70 {
            action accept
            description PPTPGRE
            log disable
            protocol gre
        }
        rule 80 {
            action drop
            description "Drop invalid state"
            state {
                invalid enable
            }
        }
    }
    receive-redirects disable
    send-redirects enable
    source-validation disable
    syn-cookies enable
}
interfaces {
    ethernet eth0 {
        address 192.168.178.3/24
        description WAN
        duplex auto
        firewall {
            in {
                name WAN_IN
            }
            local {
                name WAN_LOCAL
            }
        }
        speed auto
    }
    ethernet eth1 {
        description "Lan office"
        duplex auto
        speed auto
    }
    ethernet eth2 {
        description "Lan media"
        duplex auto
        speed auto
    }
    ethernet eth3 {
        description "Lan game"
        duplex auto
        speed auto
    }
    ethernet eth4 {
        description "Lan wifi"
        duplex auto
        poe {
            output off
        }
        speed auto
    }
    loopback lo {
    }
    switch switch0 {
        description Local
        mtu 1500
        switch-port {
            interface eth1 {
                vlan {
                    pvid 10
                }
            }
            interface eth2 {
                vlan {
                    pvid 20
                }
            }
            interface eth3 {
                vlan {
                    pvid 30
                }
            }
            interface eth4 {
                vlan {
                    pvid 40
                    vid 20
                }
            }
            vlan-aware enable
        }
        vif 10 {
            address 192.168.10.1/24
            description "VLan 10 office"
            mtu 1500
        }
        vif 20 {
            address 192.168.20.1/24
            description "VLan 20 media"
            mtu 1500
        }
        vif 30 {
            address 192.168.30.1/24
            description "VLan 30 game"
            mtu 1500
        }
        vif 40 {
            address 192.168.40.1/24
            description "VLan 40 wifi"
            firewall {
                in {
                    name VLAN40_OUT
                }
                local {
                    name VLAN40_LOCAL
                }
            }
            mtu 1500
        }
    }
}
port-forward {
    auto-firewall enable
    hairpin-nat enable
    lan-interface eth1
    rule 1 {
        description nas
        forward-to {
            address 192.168.10.80
            port 8080
        }
        original-port 8083
        protocol tcp_udp
    }
    rule 2 {
        description nas
        forward-to {
            address 192.168.10.80
            port 443
        }
        original-port 8082
        protocol tcp_udp
    }
    rule 3 {
        description camera
        forward-to {
            address 192.168.20.50
            port 37777
        }
        original-port 37777
        protocol tcp_udp
    }
    rule 4 {
        description camera
        forward-to {
            address 192.168.20.50
            port 37778
        }
        original-port 37778
        protocol tcp_udp
    }
    rule 5 {
        description camera
        forward-to {
            address 192.168.20.50
            port 80
        }
        original-port 85
        protocol tcp_udp
    }
    rule 6 {
        description camera
        forward-to {
            address 192.168.20.50
            port 554
        }
        original-port 554
        protocol tcp_udp
    }
    rule 7 {
        description domoticz
        forward-to {
            address 192.168.10.30
            port 444
        }
        original-port 445
        protocol tcp_udp
    }
    rule 8 {
        description domoticz
        forward-to {
            address 192.168.10.30
            port 82
        }
        original-port 82
        protocol tcp_udp
    }
    rule 9 {
        description domoticz
        forward-to {
            address 192.168.10.30
            port 80
        }
        original-port 80
        protocol tcp_udp
    }
    wan-interface eth0
}
service {
    bcast-relay {
        id 1 {
            description "Sonos listener"
            interface switch0.10
            interface switch0.20
            port 1900
        }
        id 2 {
            description "Sonos listener 1901"
            interface switch0.10
            interface switch0.20
            port 1901
        }
        id 3 {
            description "Sonos listener 6969"
            interface switch0.10
            interface switch0.20
            port 6969
        }
    }
    dhcp-server {
        disabled false
        hostfile-update disable
        shared-network-name LAN1 {
            authoritative disable
            subnet 192.168.10.0/24 {
                default-router 192.168.10.1
                dns-server 192.168.10.1
                lease 86400
                start 192.168.10.100 {
                    stop 192.168.10.200
                }
                static-mapping Nas {
                    ip-address 192.168.10.80
                    mac-address 00:08:9b:8d:83:36
                }
                static-mapping RPI3-domoticz {
                    ip-address 192.168.10.30
                    mac-address b8:27:eb:ad:e2:fa
                }
                static-mapping SqueezeboxBoom {
                    ip-address 192.168.10.45
                    mac-address 00:04:20:1e:f3:c9
                }
                static-mapping huiskamerpc {
                    ip-address 192.168.10.10
                    mac-address 00:24:1d:dc:d5:69
                }
                static-mapping printer {
                    ip-address 192.168.10.20
                    mac-address 00:15:99:81:4b:5f
                }
            }
        }
        shared-network-name LAN2 {
            authoritative disable
            subnet 192.168.20.0/24 {
                default-router 192.168.20.1
                dns-server 192.168.20.1
                lease 86400
                start 192.168.20.100 {
                    stop 192.168.20.200
                }
                static-mapping Chromecast-Ultra-lan {
                    ip-address 192.168.20.23
                    mac-address 44:09:b8:01:be:5d
                }
                static-mapping Denon {
                    ip-address 192.168.20.26
                    mac-address 00:05:cd:2f:16:3b
                }
                static-mapping Mobiel-monique {
                    ip-address 192.168.20.41
                    mac-address a0:8d:16:f5:d3:1f
                }
                static-mapping Mobiel-niels {
                    ip-address 192.168.20.42
                    mac-address 74:a5:28:a5:88:9a
                }
                static-mapping Mobiel-peter {
                    ip-address 192.168.20.40
                    mac-address 20:02:af:a1:91:a3
                }
                static-mapping Mobiel-sonia {
                    ip-address 192.168.20.43
                    mac-address 20:a6:80:c3:7b:09
                }
                static-mapping Mobiel-peter-p8lite {
                    ip-address 192.168.20.46
                    mac-address 20:a6:80:52:ae:8b
                }
                static-mapping PC-kodi {
                    ip-address 192.168.20.22
                    mac-address 00:01:2e:3a:e7:30
                }
                static-mapping Sonia-pc {
                    ip-address 192.168.20.35
                    mac-address e0:94:67:73:ef:f6
                }
                static-mapping Sonos-connect {
                    ip-address 192.168.20.25
                    mac-address 00:0e:58:28:97:50
                }
                static-mapping Sonoszp {
                    ip-address 192.168.20.29
                    mac-address 00:0e:58:53:b9:fe
                }
                static-mapping TV-huiskamer {
                    ip-address 192.168.20.24
                    mac-address 1c:5a:3e:a5:25:93
                }
                static-mapping Tablet-monique {
                    ip-address 192.168.20.44
                    mac-address d8:5b:2a:76:83:15
                }
                static-mapping camera {
                    ip-address 192.168.20.50
                    mac-address 3c:ef:8c:ed:8e:48
                }
            }
        }
        shared-network-name WIFI {
            authoritative disable
            subnet 192.168.40.0/24 {
                default-router 192.168.40.1
                dns-server 192.168.40.1
                lease 86400
                start 192.168.40.100 {
                    stop 192.168.40.200
                }
                static-mapping Accespointpvk {
                    ip-address 192.168.40.2
                    mac-address f0:9f:c2:3c:e6:57
                }
                unifi-controller 192.168.10.10
            }
        }
        shared-network-name game {
            authoritative disable
            subnet 192.168.30.0/24 {
                default-router 192.168.30.1
                dns-server 192.168.30.1
                lease 86400
                start 192.168.30.100 {
                    stop 192.168.30.200
                }
                static-mapping Wii-lan {
                    ip-address 192.168.30.31
                    mac-address 00:0e:c6:87:72:70
                }
                static-mapping pc-niels {
                    ip-address 192.168.30.32
                    mac-address 28:d2:44:2c:6f:83
                }
                unifi-controller 192.168.10.10
            }
        }
        use-dnsmasq disable
    }
    dns {
        forwarding {
            cache-size 150
            listen-on eth1
            listen-on switch0
            listen-on switch0.10
            listen-on switch0.20
            listen-on switch0.30
            listen-on switch0.40
        }
    }
    gui {
        http-port 80
        https-port 443
        older-ciphers enable
    }
    nat {
        rule 5010 {
            description "masquerade for WAN"
            outbound-interface eth0
            type masquerade
        }
    }
    ssh {
        port 22
        protocol-version v2
    }
}
system {
    gateway-address 192.168.178.1
    host-name ubnt
    login {
        user admin {
            authentication {
                encrypted-password ****************
                plaintext-password ****************
            }
            full-name peter
            level admin
        }
        user pvklink {
            authentication {
                encrypted-password ****************
                plaintext-password ****************
            }
            full-name peter
            level admin
        }
    }
    name-server 8.8.8.8
    name-server 208.67.222.222
    ntp {
        server 0.ubnt.pool.ntp.org {
        }
        server 1.ubnt.pool.ntp.org {
        }
        server 2.ubnt.pool.ntp.org {
        }
        server 3.ubnt.pool.ntp.org {
        }
    }
    static-host-mapping {
        host-name router {
            inet 192.168.10.1
        }
    }
    syslog {
        global {
            facility all {
                level notice
            }
            facility protocols {
                level debug
            }
        }
    }
    time-zone UTC
    traffic-analysis {
        dpi disable
        export disable
    }
}
vpn {
    ipsec {
        auto-firewall-nat-exclude disable
        ipsec-interfaces {
        }
    }
    l2tp {
        remote-access {
            authentication {
                local-users {
                    username pvklink {
                        password ****************
                    }
                }
                mode local
            }
            client-ip-pool {
                start 192.168.10.100
                stop 192.168.10.120
            }
            dns-servers {
                server-1 8.8.8.8
                server-2 8.8.4.4
            }
            ipsec-settings {
                authentication {
                    mode pre-shared-secret
                    pre-shared-secret ****************
                }
                ike-lifetime 3600
            }
            outside-address 192.168.178.3
        }
    }
    pptp {
        remote-access {
            authentication {
                local-users {
                    username pvklink {
                        password ****************
                    }
                }
                mode local
            }
            client-ip-pool {
                start 192.168.10.200
                stop 192.168.10.220
            }
            dns-servers {
                server-1 8.8.8.8
                server-2 8.8.4.4
            }
            mtu 1492
            outside-address 192.168.178.3
        }
    }
}

Emerging Member
Posts: 98
Registered: ‎06-03-2017
Kudos: 2
Solutions: 3

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

Solved!

 

Problem was the firewall of my windows pc. the vlans were considered public instead of private. So i adjust the application in the firewall....

New Member
Posts: 17
Registered: ‎08-07-2014
Kudos: 7
Solutions: 1

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

While a bit verbose, I appreciate the time taken to explain and provide step-by-step exection.  Just wanted to say that I had this entire thread bookmarked and it seems there were minor updates to the post and solution, but suffice it to say that I have now used this on my ERPOE5 running 1.8.5 (for more than 9 months, if not longer) and have recently finally upgraded to 1.9.1.1 and had to re-do this part of the configuration since it still is NOT PACKAGED by UBNT (hint hint Man Happy UBNT).

 

My Sonos devices (all 7), and actually more so my WinX installation Sonos Controller, require this for full system operation on both WiFi and hardwire because I have a) separate subnets for WiFi and hardwire and b) I do not utilize the SonosNET feature due to my WiFi currently being only 2.4Ghz and WiFi saturation levels in my subdivision (along with dorks jumping in and using nearly all channels) being attrocious.

 

I just wanted to put a verbal vote in to maybe have this as an optional UBNT provided feature in future releases that could be enabled / configured by the UI or CLI (or both).

Awesome job all!!

UniFi Controller: 5.9.29(Linux Mint 18.3 Sylvia)
Wireless: 2x UAP (gen1) 3.9.54.9373
Router: ERPOE-5 1.10.6
Switches: DGS-1024D
New Member
Posts: 3
Registered: ‎03-30-2017
Kudos: 3

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

I too have managed to install and configure broadcast relay on my USG to have my Yamaha IOS App in VLAN20 discover and control the Yamaha Receiver in VLAN30.  I did have to manually add the IP Address of the receiver into the App as it could not automatically find and add it (unlike when everything is in the same VLAN).

Enabled mDNS and UPnP in system.properties also and confirmed Airplay also works from iPhone to Yamaha.

 

But now I need to go the other way and have the Yamaha Receiver discover and play music from my Synology NAS media server which uses port 1900 UDP and TCP 5000.  I added another broadcast service on ID2 using port 1900 between the 2 VLANs on eth1.30 and eth1.20 but the Yamaha can't find/see the NAS.  There is no option in the Yamaha to manually add the IP address of the NAS either.  I'm stuck.... any ideas?

New Member
Posts: 24
Registered: ‎12-30-2016
Kudos: 2
Solutions: 1

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

I tried running your condensed instructions for Chromecasting, but I can't run the "set service mdns repeater interface <my eth here>" commands. Did I miss a step?

 

Thanks.

Established Member
Posts: 1,408
Registered: ‎10-01-2014
Kudos: 695
Solutions: 66

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

[ Edited ]

Post the exact sequence of instructions you followed. Also, be sure to use the tab key to complete the commands in the CLI, to avoid typos and unavailable interfaces. Note that "<my interface here>" isn't a legal instruction and actually represents a place holder for the real interface, i.e. "eth0" (using the tab key will help here). 

Please help the community find useful posts and solutions by using the "Kudos" and "Accept as Solution" buttons!
New Member
Posts: 24
Registered: ‎12-30-2016
Kudos: 2
Solutions: 1

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

I used this link: http://www.cron.dk/edgerouter-and-chromecast/ along with your "ubnt-bcast-relay" file.

The Unifi USG we are using will accept a "set service" command just not

set service mdns repeater interface eth0   <-Will not accept says "invalid command"

set service mdns repeater interface eth0.1   <-Will not accept says "invalid command"

 

Nor will it accept the commands the way you did it:

 

set service bcast-relay id 1 description 'Chromecast'  <- Will not accept says "invalid command"
set service bcast-relay id 1 interface eth0   <- Will not accept says "invalid command"
set service bcast-relay id 1 interface eth0.1   <- Will not accept says "invalid command"
set service bcast-relay id 1 port <chromecast port>   <- Will not accept says "invalid command"

 

I am thinking is might an issue with my model number, or it could be my syntax. @britannic thank you for your help.

Established Member
Posts: 1,408
Registered: ‎10-01-2014
Kudos: 695
Solutions: 66

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

Unfortunately, the USG isn't supported by broadcast relay, but it may still be possible to still make it work. I don't have a USG to test to figure it out, so maybe someone else can help. 

Please help the community find useful posts and solutions by using the "Kudos" and "Accept as Solution" buttons!
New Member
Posts: 24
Registered: ‎12-30-2016
Kudos: 2
Solutions: 1

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

Got it all it took was the following commands:

1) ssh into the USG and
2) configure
3) set service mdns reflector
4) commit
5) save.

 

Got the commands from this post: https://community.ubnt.com/t5/UniFi-Routing-Switching/Airplay-and-Airprint-Firewall-Rules/td-p/17903...

New Member
Posts: 10
Registered: ‎10-11-2014
Kudos: 4

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

I've since moved from an edgerouter to pfsense, but this thread has helped me a ton in the past.

 

I've done a lot of work on udp-broadcast-relay to add better support for multicast groups and chromecast. Unfortunately, as pfSense is FreeBSD based, I don't really have a way to compile it for an edgerouter anymore, but if anyone else is interested, here is the repo:

 

https://github.com/sonicsnes/udp-broadcast-relay-redux

 

I've been able to ditch mdns-repeater and icmp-proxy and use this exclusively for discovery between vlans of all my lifx bulbs, chromecasts, rokus, and other personal projects which use mdns / udp broadcasts.

 

Good luck!

Emerging Member
Posts: 108
Registered: ‎07-09-2016
Kudos: 35
Solutions: 4

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

Does anybody have the knowledge to hack udp-broadcast such that it adds a "related" entry to conntrack when a datagram is forwarded? Then the answer packets could be matched by a "state related" rule in the firewall.
IIRC, the currently installed conntrack tools on EdgeRouter have a bug in the --create parameter, but this has been fixed in the original conntrack tools source by now.
Cheers
Alex
New Member
Posts: 10
Registered: ‎10-11-2014
Kudos: 4

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

I believe conntrack requires a source and destination address/port to create a relationship. Since you don't know what address (or even port) the responses will be coming from, I don't think it will work.
Emerging Member
Posts: 108
Registered: ‎07-09-2016
Kudos: 35
Solutions: 4

Re: Multicast, Sonos, Phorus & Play-Fi Broadcast 255.255.255.255:<port> Discovery Solution

The source and destination ports will be destination and source ports of the forwarded packet (just swapped). Destination address of answer will be source of original datagram. And the source address of the reply will be within the respective network - conntrack expectation table allows for an address mask to be included for the expect entry.
Reply