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

prevent windows firewall popup #21

Closed
cottsak opened this issue Aug 19, 2016 · 18 comments
Closed

prevent windows firewall popup #21

cottsak opened this issue Aug 19, 2016 · 18 comments
Labels

Comments

@cottsak
Copy link
Contributor

cottsak commented Aug 19, 2016

Can we prevent the Windows Firewall popup from appearing?

I'm getting it when I reset the test environment or restart VS, etc.

@JohannesHoppe
Copy link
Member

I don't think so. That's a security feature of windows.

@JohannesHoppe
Copy link
Member

As far as I know the only option is to disable the firewall...

@cottsak
Copy link
Contributor Author

cottsak commented Aug 20, 2016

I think it's only presenting because the process opens a tcp listener. Is there a param you can pass to the process to prevent that? I mean, we don't need the tcp listener for in-memory work right?

On 19 Aug 2016, 20:12 +0800, Johannes Hoppe notifications@github.com, wrote:

As far as I know the only option is to disable the firewall...


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#21 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAwr1KXNp5oahAbxyQHRR94AujQjTxkEks5qhZ2SgaJpZM4JoVBW).

@JohannesHoppe
Copy link
Member

Sure. Clients communicate with the database server through a regular TCP/IP socket.
I'm not aware of any other protocoll.

see: https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/

@cottsak
Copy link
Contributor Author

cottsak commented Aug 20, 2016

So what we're saying is there's no avoiding the listener and so no avoiding the firewall warning? ☹️

On 20 Aug 2016, 20:02 +0800, Johannes Hoppe notifications@github.com, wrote:

Sure. Clients communicate with the database server through a regular TCP/IP socket.
I'm not aware of any other protocoll.

see: https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (#21 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAwr1LlMYE_wMniH4HpjbtKugUZRmmC5ks5qhuzRgaJpZM4JoVBW).

@JohannesHoppe
Copy link
Member

As far as I know – yes. My firewall is disabled…

@cottsak cottsak closed this as completed Aug 21, 2016
@kubal5003
Copy link
Contributor

We discovered this issue today too. I think I might have a solution - the window doesn't pop up when you pass the flag --bind_ip 127.0.0.1 to mongod.exe.
Since Mongo2Go is intended for in process use I assume that this would be a safe change? If you agree I can prepare a PR.

@cottsak
Copy link
Contributor Author

cottsak commented Mar 3, 2017

That sounds like a good idea. Safe assumption too I think.

@JohannesHoppe
Copy link
Member

JohannesHoppe commented Mar 3, 2017

Yep. Localhost is fine.

Please keep in mind that #master is right now .NET Core only.
I should make a branch first, if you want to target .NET 4.6.x .

@JohannesHoppe JohannesHoppe reopened this Mar 3, 2017
@JohannesHoppe
Copy link
Member

@kubal5003
Copy link
Contributor

Thank you for creating a branch for the .NET 4.6 since we're using that version :) I'll try to update both of them.

@JohannesHoppe
Copy link
Member

yay, cool! 👍

i think this would be a 1.1 and a 2.0.0-alpha2

@kubal5003
Copy link
Contributor

I saw that you merged my PRs. How do we proceed ? What can I do now?

@JohannesHoppe
Copy link
Member

I will bake two nuget packages today and upload them.
Then you could test! :-)

@kubal5003
Copy link
Contributor

Thank you! We will update as soon as we get those :)

JohannesHoppe added a commit that referenced this issue Mar 10, 2017
@JohannesHoppe
Copy link
Member

Both NuGet packages are on nuget.org now.
Took me a little bit more time, since I had upgraded to VS 2017 (and removed old Visual Studio) ... 😅

For .NET Framework 4.6.1

Install-Package Mongo2Go -Version 1.1.0

For .NET Standard 1.6

Install-Package Mongo2Go -Version 2.1.0

@kubal5003
Copy link
Contributor

I tested this today (1.1.0). It works fine :) The firewall window does not appear. I also made sure to remove the firewall rule prior to testing. Do we want to test 2.1.0 before closing this?

@JohannesHoppe
Copy link
Member

I think it's not necessary in this case! Thanks for testing! 👍

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

No branches or pull requests

3 participants