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

WCF listens 0.0.0.0 (on linux) #373

Closed
Lycreal opened this issue Dec 11, 2016 · 1 comment
Closed

WCF listens 0.0.0.0 (on linux) #373

Lycreal opened this issue Dec 11, 2016 · 1 comment
Labels
🐛 Bug Issues marked with this label indicate unintended program behaviour that needs correction. ✔️ Confirmed Issues marked with this label were acknowledged and confirmed by the developers. 🟢 Low priority Issues marked with this label are actively being worked on if nothing serious is on the list.

Comments

@Lycreal
Copy link

Lycreal commented Dec 11, 2016

After I ran mono ASF.exe --server , I found the mono process listening 0.0.0.0:1242 .

 cloud@2  ~/ASF $ sudo netstat -antp | grep 1242
tcp        0      0 0.0.0.0:1242            0.0.0.0:*               LISTEN      19777/mono
 cloud@2  ~/ASF $ ssh 10.0.0.5
Last login: Sun Dec 11 17:03:24 2016 from 10.0.0.4
 cloud@centos  ~ $ telnet 10.0.0.4 1242
Trying 10.0.0.4...
Connected to 10.0.0.4.
Escape character is '^]'.

I tried changing WCFHostname from localhost to 127.0.0.1 in the ASF.json , nothing changes.

I think this shouldn't happen since the wki says:

ASF by default listens only on localhost address, which means that accessing ASF WCF from any other machine but your own is impossible.

ASF V2.1.6.8 on Ubuntu 16.04 .

@JustArchi JustArchi added 🐛 Bug Issues marked with this label indicate unintended program behaviour that needs correction. ✔️ Confirmed Issues marked with this label were acknowledged and confirmed by the developers. 🟢 Low priority Issues marked with this label are actively being worked on if nothing serious is on the list. labels Dec 11, 2016
@JustArchi
Copy link
Member

Indeed it looks like BasicHttpBinding() is for some reason too stupid to handle even 127.0.0.1 case properly, I'm not entirely sure why but I confirmed it with MS docs, therefore I switched WCF to TCP binding instead, and that one listens correctly on 127.0.0.1 interface if you specify 127.0.0.1. For some reason it doesn't work with specifying localhost, therefore I also renamed property appropriately and enforced 127.0.0.1 instead of localhost from now on.

Thanks for report.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐛 Bug Issues marked with this label indicate unintended program behaviour that needs correction. ✔️ Confirmed Issues marked with this label were acknowledged and confirmed by the developers. 🟢 Low priority Issues marked with this label are actively being worked on if nothing serious is on the list.
Projects
None yet
Development

No branches or pull requests

2 participants