Skip to content
This repository has been archived by the owner on Aug 5, 2022. It is now read-only.

[ocf] Fix OCF resources not discoverable on FRDM-K64F #1886

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jimmy-huang
Copy link
Contributor

This patch fixes the issue that multicast discovery messages cannot be
routed to the server after Zephyr update 1.11 with IPV6, but turning on
promiscuous mode resolves this issue.

Fixes #1885

Signed-off-by: Jimmy Huang jimmy.huang@intel.com

This patch fixes the issue that multicast discovery messages cannot be
routed to the server after Zephyr update 1.11 with IPV6, but turning on
promiscuous mode resolves this issue.

Fixes intel#1885

Signed-off-by: Jimmy Huang <jimmy.huang@intel.com>
@grgustaf
Copy link
Contributor

grgustaf commented Jun 1, 2018

See if the solution from #1881 would work for this too... (see discussion in #1842 where @pfalcon showed the right way to solve it).

@jimmy-huang
Copy link
Contributor Author

@grgustaf Yeah, that solution didn't work, in fact, ocf already sets CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=4, and I tried increasing it with no success either, until I turned on promiscuous mode, then it worked, that's why I am hoping @pfalcon might know the real answer here.

@pfalcon
Copy link
Contributor

pfalcon commented Jun 4, 2018

@pfalcon might know the real answer here.

I don't know the exact answer.

CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=4, and I tried increasing it with no success either

To what value did you increase it? How many multicast addresses does OCF require?

@jimmy-huang
Copy link
Contributor Author

@pfalcon I've tried ranges from 4 up to 8, I believe ocf only requires 1 multicast addr for the discovery.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ocf] Ocf Client cannot connect to OcfServer on K64F
3 participants