WIFI 和组播问题

发布于 2024-10-22 02:55:07 字数 424 浏览 2 评论 0原文

大家好 我有两台 PC 的 AB,它们连接到 LAN1 。A 正在侦听 UPNP 多播地址 239.255.255.250 。 我有一个移动设备 D ,它连接到 WIFI ,并且 WIFI 连接到 LAN1 。 PC A 的 IP 地址为 xxx.yyy.209.80,PC B 的 IP 地址为 xxx.yyy.209.81,设备 D 的 IP 地址为 xxx.yyy.209.82。 如果我从 PC B 向 239.255.255.250 发送多播数据包,它会到达 PC A。 但是,如果我从设备 D 发送多播数据包,它永远不会到达 PC A。任何人都可以告诉我为什么吗?如何解决它?

提前致谢 科兹洛夫

Hi All
I ve two PC's A and B which are connected to LAN1 .A is listening on UPNP multicast address 239.255.255.250 .
I have a mobile device D which is connected to a WIFI and the WIFI is connected to LAN1 .
Ip address of PC A is xxx.yyy.209.80 PC B is xxx.yyy.209.81 and device D is xxx.yyy.209.82.
If I send a multicast packet to 239.255.255.250 from PC B it reaches PC A.
But if I send a multicast pakcet from device D it never reaches PC A .Can anyone tell me why ?How to resolve it ?

Thanks in advance
Kozlov

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

短叹 2024-10-29 02:55:07

我意识到这篇文章已有 3 年历史,但以下信息可能对某人有用。我有一个使用 239.xxx 地址的 iPhone 应用程序,但我在使用某些无线接入点时遇到问题。我找到了一份文件,内容如下:

有一些特殊的多播组,例如“众所周知的多播组”
组”,您不应该在您的特定应用程序中使用,因为
他们注定有特殊的目的:

224.0.0.1 是所有主机组。如果您对该组执行 ping 操作,则网络上所有具有多播功能的主机都应该应答,就像每个组一样
具有多播功能的主机必须在启动时加入该组
具有多播功能的接口。
224.0.0.2 是所有路由器组。所有多播路由器必须在所有支持多播的接口上加入该组。
224.0.0.4 是所有 DVMRP 路由器,224.0.0.5 是所有 OSPF 路由器,224.0.013 是所有 PIM 路由器等。所有这些特殊多播组都会定期在“分配的编号”RFC 中发布。

无论如何,范围 224.0.0.0 到 224.0.0.255 保留给本地
目的(作为管理和维护任务)和数据报
发往它们的信息永远不会被多播路由器转发。相似地,
范围 239.0.0.0 到 239.255.255.255 已被保留
“行政范围”(有关信息,请参阅第 2.3.1 节)
行政范围)。

无论如何,我将地址更改为 238.xxx,但这对 Netgear R6100 AP 没有帮助。我在 Wireshark 中发现的问题是 LAN 数据包不会转发到无线设备。我还没有尝试过其他方向。

I realize this post is 3 years old but the following information may be useful to someone. I have an iPhone App that uses a 239.x.x.x address and I have issues with certain wireless access points. I found a document that says the following:

There are some special multicast groups, say "well known multicast
groups", you should not use in your particular applications due the
special purpose they are destined to:

224.0.0.1 is the all-hosts group. If you ping that group, all multicast capable hosts on the network should answer, as every
multicast capable host must join that group at start-up on all it's
multicast capable interfaces.
224.0.0.2 is the all-routers group. All multicast routers must join that group on all it's multicast capable interfaces.
224.0.0.4 is the all DVMRP routers, 224.0.0.5 the all OSPF routers, 224.0.013 the all PIM routers, etc. All this special multicast groups are regularly published in the "Assigned Numbers" RFC.

In any case, range 224.0.0.0 through 224.0.0.255 is reserved for local
purposes (as administrative and maintenance tasks) and datagrams
destined to them are never forwarded by multicast routers. Similarly,
the range 239.0.0.0 to 239.255.255.255 has been reserved for
"administrative scoping" (see section 2.3.1 for information on
administrative scoping).

Anyway I changed my address to 238.x.x.x and that did not help with the Netgear R6100 AP. The issue I have seen with Wireshark is that LAN packets are not forwarded to wireless devices. I have not tried the other direction.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文