Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unique MAC address workaround #125

Open
jmbinette opened this issue Aug 2, 2019 · 3 comments
Open

Unique MAC address workaround #125

jmbinette opened this issue Aug 2, 2019 · 3 comments

Comments

@jmbinette
Copy link

Hi,

I understand the "unique mac address" issue with the networkid.

To permit running multiple instances of APIs on the same raspberry PI, would it be possible to add a configurable prefix before the MAC ?

Thanks,

@vervallsweg
Copy link
Owner

APIs on the same raspberry PI, would it be possible to add a configurable prefix before the MAC ?

This won't work since this a ST limitation. If we want to send something to ST we need to use the mac to identify ourself. It needs to be a valid mac and obviously match the hardware mac the ST hub received the package from.

Your only option is to add a second network card/device to your raspberry, with a different ip. Then you have two different ip/mac pairs for two different apis.

@jmbinette
Copy link
Author

Sorry I "snoozed" on this for a long time!

Any way to choose which network interface is used by cast-web-api ?

@jmbinette
Copy link
Author

That could be a great feature yes ! Did not find a solution yet as even using WLAN and ETH on the Raspberry Pi, the mac address used seems to always be the same

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

No branches or pull requests

2 participants