Custom override of host IP addressed used in NFS shares #62
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please excuse my code, as I'm not a ruby miner (I'm a PHP guy), so I apologize deeply in advance.
I'm in a situation where I cannot access my NFS shares when I'm connected to VPN, since all communications with the host machine (that aren't directly tied to loop-back at
127.0.0.1
) are completely locked out. Thankfully, my VM sees the host machine (in my case) always as10.0.2.2
. The problem is, due to Vagrant core NFS functionality, they automatically use the host-only IP address (which in my case was10.9.8.1
since my private network address was10.9.8.7
). Unfortunately, that gets locked out so the VM cannot connect to that IP (while communications are just fine on my forwarded ports and when directly connecting back to10.0.2.2
).This PR provides a workaround that I've implemented in my copy of your plugin which just allows me to set the IP address in my configuration. Is there a better way of doing this? I'm completely open to the possibility that I'm doing this all wrong (and I struggled with this for several hours!).