Virtualbox related issue - multiple networks #60

xingjianpan · 2017-03-14T13:51:27Z

Hi,

I have virtual box installed on my system and there are multiple networks available in additional to my WIFI network (i.e VirtualBox Host-Only Network, VirtualBox Host-Only Network #2， VirtualBox Host-Only Network #3 , etc..).

After running the command yarn start, i got below messsage:

Or enter this address in the Expo app's search bar:

exp://192.168.56.12:19000

Initially i was not able to connect to this address using Expo App. After quite some time investigating this issue, i noticed it's because 192.168.56.12 belongs to one of the network created by VirtualBox.

After disabling all the networks created by Virtual Box, I am able to connect Expo with my project.
and the message become this. Note 192.168.1.12 belongs to my WIFI network which my phone can connect.

Or enter this address in the Expo app's search bar:

exp://192.168.1.12:19000

So, is this a bug? or is there a place where i can set which network to use?

anp · 2017-03-14T17:14:04Z

I think this is probably a bug. What OS are you using? I suspect that our detection for "default network device" is not producing the correct result here. We currently use https://www.npmjs.com/package/ip to detect IP addresses, but it might be worth trying with https://www.npmjs.com/package/address or another package.

cc @jesseruder, relevant xdl line: https://github.com/exponent/xdl/blob/43f29f10ea1641a5ab1808af93bedb8ee683a6b8/src/UrlUtils.js#L148

xingjianpan · 2017-03-15T03:18:25Z

my system is Windows 10 Home Edition.

anp · 2017-03-15T21:36:47Z

This issue has been open for a while indutny/node-ip#21. I'm going to see if I can repro this and will check if the address package works better in this scenario.

anp · 2017-03-16T00:01:37Z

Can you tell me what the output of this command is in a node REPL when running virtualbox on this machine?

Object.keys(require('os').networkInterfaces()).reduce((results, name) => results.concat(interfaces[name]), []).filter((iface) => iface.family === 'IPv4' && !iface.internal).map((iface) => iface.address)

xingjianpan · 2017-03-16T12:41:44Z

I got below error when running your command:

ReferenceError: interfaces is not defined
at Object.keys.reduce (repl:1:89)
at Array.reduce (native)
at repl:1:48
at sigintHandlersWrap (vm.js:22:35)
at sigintHandlersWrap (vm.js:96:12)
at ContextifyScript.Script.runInThisContext (vm.js:21:12)
at REPLServer.defaultEval (repl.js:346:29)
at bound (domain.js:280:14)
at REPLServer.runBound [as eval] (domain.js:293:12)
at REPLServer. (repl.js:545:10)

However, if i just run the first part of your command:

require('os').networkInterfaces()

I got below results:

{ 'VirtualBox Host-Only Network':
[ { address: 'fe80::787d:2d70:287f:b786',
netmask: 'ffff:ffff:ffff:ffff::',
family: 'IPv6',
mac: '0a:00:27:00:00:06',
scopeid: 6,
internal: false },
{ address: '192.168.56.1',
netmask: '255.255.255.0',
family: 'IPv4',
mac: '0a:00:27:00:00:06',
internal: false } ],
'VirtualBox Host-Only Network #2':
[ { address: 'fe80::84af:8a25:b53a:67f9',
netmask: 'ffff:ffff:ffff:ffff::',
family: 'IPv6',
mac: '0a:00:27:00:00:17',
scopeid: 23,
internal: false },
{ address: '192.168.25.2',
netmask: '255.255.255.0',
family: 'IPv4',
mac: '0a:00:27:00:00:17',
internal: false } ],
'VirtualBox Host-Only Network #3':
[ { address: 'fe80::b9e5:1022:96dc:3786',
netmask: 'ffff:ffff:ffff:ffff::',
family: 'IPv6',
mac: '0a:00:27:00:00:15',
scopeid: 21,
internal: false },
{ address: '192.168.99.1',
netmask: '255.255.255.0',
family: 'IPv4',
mac: '0a:00:27:00:00:15',
internal: false } ],
MyWLAN:
[ { address: 'fe80::55f8:45e1:8a5e:a510',
netmask: 'ffff:ffff:ffff:ffff::',
family: 'IPv6',
mac: '34:f3:9a:64:28:5f',
scopeid: 8,
internal: false },
{ address: '192.168.1.11',
netmask: '255.255.255.0',
family: 'IPv4',
mac: '----removed----',
internal: false } ],
'Loopback Pseudo-Interface 1':
[ { address: '::1',
netmask: 'ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff',
family: 'IPv6',
mac: '00:00:00:00:00:00',
scopeid: 0,
internal: true },
{ address: '127.0.0.1',
netmask: '255.0.0.0',
family: 'IPv4',
mac: '00:00:00:00:00:00',
internal: true } ] }

smiled0g · 2017-03-16T14:50:50Z

@xingjianpan I was having the same problem. Assigning interface matric (priority) for your Wifi adapter and any other network adapters solves the problem for me. The order of IP used in https://www.npmjs.com/package/ip seems to be the first one you can see when running ipconfig.

This link shows how: https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/adapter-priority-setting-unavailable-in-windows-10/d2b63caa-e77c-4b46-88b5-eeeaee00c306

Hope this helps

xingjianpan · 2017-03-17T09:42:52Z

@smiled0g , many thanks! I will try it out.

@smiled0g , this method works for me! Thanks!

digital-stoic · 2017-03-19T03:06:25Z

Hi guys,

I think the proper way to address this issue is simply to be able to specify IP and port at launch (options, environment variables).

Here is the problem that I have related to this open issue:

My expo App runs in a Docker container => many options possible for the interfaces (bridges, overlay networks...)
My server running the docker has a virtual public IP (behind load balancer) => Neither the container nor the server is 'aware' of this IP

=> The only way to address this and ALL the other possible networking configurations is to be able to setup the IP+Port at the application level (Expo)

Cheers,

pstanton · 2017-06-22T09:52:46Z

adapter ordering is a work around, a solution would be to be able to configure.

Himujjal · 2017-07-21T20:28:40Z

The following steps will definitely help. I had the same problem and was able to solve it in my Windows 10 OS. I had Virtual Box installed on my computer and I was not able to run CRNA in my android expo client. So,

first I connected my laptop through my mobile hotspot.
Then Control Panel > (search for 'network connections') > network connections
Right-Click on 'Wifi' > select 'Properties' > 'Internet Protocol Version 4 (TCP/IPv4)' [don't uncheck the mark]
Go to "Properties" > "Advanced..." > (Uncheck 'Automatic Metric') > Type in the text-box below that (Interface Metric) : 10.
Click OK and OK and OK :)
Then do the same for the other "Virtual Box-xxxxx" networks. But instead put 20 in the Interface Metric text-box.
Click OK, OK and OK.
Try restarting your app on Expo. It must work now!

rottenoats · 2017-09-25T18:28:36Z

I had a similar issue as @Himujjal . I had VMWare installed. Going to network connections and deactivating all of them solved the problem.

clarkgrg · 2017-10-17T05:11:54Z

I couldn't get the above items to work. Although my problem is running Hyper-V. I just disabled the Ethernet connection for Hyper-V while running react-native.

andriy-f · 2018-01-11T10:13:09Z

If you set env var REACT_NATIVE_PACKAGER_HOSTNAME to desired IP, then it will use that address. More info here https://github.com/react-community/create-react-native-app/blob/master/react-native-scripts/template/README.md#configuring-packager-ip-address

webprofusion-chrisc · 2018-01-19T09:35:28Z

For info, other tools like Ionic let you choose which network interface to serve from.

For windows, running SET REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.5 in the terminal (or permanently in the environment variable settings) is the best option, much more so that messing with your adapter settings.

spyp · 2018-01-20T11:52:49Z

Hey all and thxn @smiled0g i think this comment should be added in docs many of us using windows and we have problem
tnx again my problem is solved too

Bryze · 2018-02-19T13:47:08Z

@webprofusion-chrisc
Even though I have updated both the current CMD session and the registry by using
set REACT_NATIVE_PACKAGER_HOSTNAME=192.168.0.96 and setx REACT_NATIVE_PACKAGER_HOSTNAME 192.168.0.96. Doing a yarn start displays the ip exp://192.168.56.1:19000 which is my VirtualBox Ip.

Additionally, doing a ls env: on PowerShell shows me ->

Also, here is my ipconfig

Are there any additional settings that need to be changed?

EDIT
Was a restart issue. Now, yarn start was picking up the new environment variable value.

webprofusion-chrisc · 2018-02-19T23:48:19Z

@Bryze actually I haven't seen 'setx' before, you learn something new every day. The conventional way is to go to Control Panel\System and Security\System > Advanced system settings, then Environment Variables, you can then set the variable at the user or system level. You then need to close and reopen the command window you're working in (or any other dependant processes which spawned before you changed it).

Bryze · 2018-02-20T10:06:18Z

@webprofusion-chrisc yes indeed that's the conventional way. I had some doubts settings environment variables as all I could see in it were paths. So that confused me a little bit.

However, FYI when we do setx places them in the environment variables section. So, after using setx, if you head over to the same window via the conventional way, you'll see your newly set variable there! :)

kajmagnus · 2018-02-24T14:43:40Z

Don't forget to open the required firewall ports too on your laptop; in my case, seems to be 19000 and 19001.
(Right?)

GBurgardt · 2018-03-26T23:19:57Z

In my case (Ubuntu) the problem was always the ports.

To open them, these are the commands:

sudo ufw enable

sudo ufw allow 19000

sudo ufw allow 19001

SirPhemmiey · 2018-04-07T11:13:59Z

Had the same issue. Re-installing the Expo app on my device, and restarting (clear cache) the packager did it. Relieved!

buryo · 2022-11-07T21:42:06Z

I had the same problem, then I realized my WIFI automatically connected to my neighbours. Your PC and phone should be on the same network.

hafizip00 · 2023-03-27T11:15:39Z

The following steps will definitely help. I had the same problem and was able to solve it in my Windows 10 OS. I had Virtual Box installed on my computer and I was not able to run CRNA in my android expo client. So,

first I connected my laptop through my mobile hotspot.

Then Control Panel > (search for 'network connections') > network connections

Right-Click on 'Wifi' > select 'Properties' > 'Internet Protocol Version 4 (TCP/IPv4)' [don't uncheck the mark]

Go to "Properties" > "Advanced..." > (Uncheck 'Automatic Metric') > Type in the text-box below that (Interface Metric) : 10.

Click OK and OK and OK :)

Then do the same for the other "Virtual Box-xxxxx" networks. But instead put 20 in the Interface Metric text-box.

Click OK, OK and OK.

Try restarting your app on Expo. It must work now!

It's not working for me can you help me out @Himujjal please I'm struggling with this issue since last week.

aalee-haider · 2024-06-05T06:38:07Z

I had the same problem, then I realized my WIFI automatically connected to my neighbours. Your PC and phone should be on the same network.

I tried the same thing and it worked for me

anp added bug underlying tools labels Mar 14, 2017

anp added the awaiting-reply label Mar 16, 2017

anp mentioned this issue Mar 18, 2017

Wrong Server IP #90

Closed

anp removed the awaiting-reply label Mar 18, 2017

anp mentioned this issue Mar 18, 2017

could not load exp://ipaddres+port #81

Closed

anp added the networking label Mar 18, 2017

anp closed this as completed in fd435ea Mar 21, 2017

telmen mentioned this issue Apr 8, 2017

fetch request to localhost server #154

Closed

jurosh mentioned this issue Sep 14, 2017

Service started on different address than Wifi is facebook/react-native#15933

Closed

jimmylee mentioned this issue Sep 19, 2017

Phone <> Computer connection issues for Windows users expo/expo#438

Closed

phillipwei mentioned this issue Oct 26, 2017

exp start --lan selects the wrong Network interface expo/expo#862

Closed

itsAmr mentioned this issue Nov 25, 2017

App is using 172.16.123.1 as the IP address, which isn't on the network I'm connected to. #264

Closed

thebakerdev mentioned this issue Mar 16, 2018

Expo Time out, no manifest in cache #598

Closed

ide mentioned this issue May 7, 2018

Device And Expo Server Not In The Same LAN expo/expo#1726

Closed

okch-codes mentioned this issue Jan 6, 2019

Update ip.js expo/expo-cli#288

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Virtualbox related issue - multiple networks #60

Virtualbox related issue - multiple networks #60

xingjianpan commented Mar 14, 2017 •

edited

Loading

anp commented Mar 14, 2017 •

edited

Loading

xingjianpan commented Mar 15, 2017

anp commented Mar 15, 2017

anp commented Mar 16, 2017

xingjianpan commented Mar 16, 2017 •

edited

Loading

smiled0g commented Mar 16, 2017

xingjianpan commented Mar 17, 2017 •

edited

Loading

digital-stoic commented Mar 19, 2017

pstanton commented Jun 22, 2017

Himujjal commented Jul 21, 2017

rottenoats commented Sep 25, 2017

clarkgrg commented Oct 17, 2017

andriy-f commented Jan 11, 2018

webprofusion-chrisc commented Jan 19, 2018

spyp commented Jan 20, 2018

Bryze commented Feb 19, 2018 •

edited

Loading

webprofusion-chrisc commented Feb 19, 2018

Bryze commented Feb 20, 2018

kajmagnus commented Feb 24, 2018

GBurgardt commented Mar 26, 2018 •

edited

Loading

SirPhemmiey commented Apr 7, 2018

buryo commented Nov 7, 2022

hafizip00 commented Mar 27, 2023

aalee-haider commented Jun 5, 2024

Virtualbox related issue - multiple networks #60

Virtualbox related issue - multiple networks #60

Comments

xingjianpan commented Mar 14, 2017 • edited Loading

anp commented Mar 14, 2017 • edited Loading

xingjianpan commented Mar 15, 2017

anp commented Mar 15, 2017

anp commented Mar 16, 2017

xingjianpan commented Mar 16, 2017 • edited Loading

smiled0g commented Mar 16, 2017

xingjianpan commented Mar 17, 2017 • edited Loading

digital-stoic commented Mar 19, 2017

pstanton commented Jun 22, 2017

Himujjal commented Jul 21, 2017

rottenoats commented Sep 25, 2017

clarkgrg commented Oct 17, 2017

andriy-f commented Jan 11, 2018

webprofusion-chrisc commented Jan 19, 2018

spyp commented Jan 20, 2018

Bryze commented Feb 19, 2018 • edited Loading

webprofusion-chrisc commented Feb 19, 2018

Bryze commented Feb 20, 2018

kajmagnus commented Feb 24, 2018

GBurgardt commented Mar 26, 2018 • edited Loading

SirPhemmiey commented Apr 7, 2018

buryo commented Nov 7, 2022

hafizip00 commented Mar 27, 2023

aalee-haider commented Jun 5, 2024

xingjianpan commented Mar 14, 2017 •

edited

Loading

anp commented Mar 14, 2017 •

edited

Loading

xingjianpan commented Mar 16, 2017 •

edited

Loading

xingjianpan commented Mar 17, 2017 •

edited

Loading

Bryze commented Feb 19, 2018 •

edited

Loading

GBurgardt commented Mar 26, 2018 •

edited

Loading