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

castnow picks up wrong IP address #56

Open
kim0 opened this issue Jan 13, 2015 · 6 comments
Open

castnow picks up wrong IP address #56

kim0 opened this issue Jan 13, 2015 · 6 comments
Milestone

Comments

@kim0
Copy link

kim0 commented Jan 13, 2015

My machine has multiple IP addresses (I've got virtualization software installed). I noticed castnow picks up the wrong IP address, thus initially it was never working for me .. I noticed that if I pass the --myip parameter, it does work (and it's awesome)

castnow should automatically pick the IP address that falls within the network of the chromecast device.

@xat
Copy link
Owner

xat commented Jan 13, 2015

Very nice idea :)
If someone has multiple network adapters in the same network as chromecast we would just choose randomly one of them I guess.

@kim0
Copy link
Author

kim0 commented Jan 13, 2015

Another (possibly simpler) solution, is to bind the webserver to ip 0.0.0.0 which corresponds to all known IP addresses .. Usually bad for security, but in this case, I guess the convenience beats being too pedantic on security .. Guess that would work no?

@xat
Copy link
Owner

xat commented Jan 13, 2015

Chromecast also needs to know your IP since it's fetching the video data from your computer.

@kim0
Copy link
Author

kim0 commented Jan 15, 2015

Agreed 👍

@xat xat added this to the v0.5 milestone Jan 16, 2015
xat added a commit that referenced this issue Jan 20, 2015
@kennyluk
Copy link

kennyluk commented Feb 2, 2016

I use vmware on OSX and castnow is still picking up the VM's interfaces, even though their ip's begin with 172.16 and my real machine's ip is 192.168

@bugdanov
Copy link

bugdanov commented Mar 9, 2017

Hi there !

It's because internal-ip returns the last ip address instead ot the primary network interface address.

I fixed it with this:
bugdanov/internal-ip@0b9a350

Could not test it on Windows or MacOS

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

No branches or pull requests

4 participants