| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Recsync: RecCeiver Server announcement contains Broadcast address instead of server ip address |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Heinz Junkes <junkes at fhi-berlin.mpg.de> |
| Cc: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
| Date: | Fri, 22 Apr 2022 12:41:17 -0700 |
On 4/22/22 11:51, Heinz Junkes via Tech-talk wrote:
Hi, we need to route the announcements from our central Channelfinder server to a subnet so that the recasters on the IOCs in the subnet can send their PV information to the server. Unfortunately, the announcement package does not contain the IP of the server but FF:FF:FF:FF.
How are you planning to "route"? Playing games with routing rules, or mangling via. something like iptables/netfilter won't change the IP source address, which is what SERV ADDR == 0xffffffff means (as with CA or PVA). If you are thinking to create an active repeater (application level proxy), then this app. will need to copy the original IP source address into SERV ADDR field. https://github.com/ChannelFinder/recsync#udp-protocol
root@priscilla:~# socat -ls -u -v -x UDP4-RECVFROM:5049,broadcast,fork,bind=141.14.143.255 UDP4-SENDTO:10.0.1.255:5049,broadcast2022/04/22 17:22:18.879313 length=16 from=0 to=1552 43 00 00 ff ff ff ff 84 81 00 00 61 bf c1 23 RC..........a..# Gruss Heinz