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

HostOnly adapter not booting #2

Closed
AliBawazeEer opened this issue Jun 15, 2016 · 5 comments
Closed

HostOnly adapter not booting #2

AliBawazeEer opened this issue Jun 15, 2016 · 5 comments
Assignees

Comments

@AliBawazeEer
Copy link

@jbarone ... when i logged in to the box
ifconfig ,,, only NAT adapter is working fine but not Hostonly

have you blog post about this lab somewhere ?

@jbarone
Copy link
Owner

jbarone commented Jun 15, 2016

I'm actually seeing this as well on my setup. I'm looking into it now. I think something might have changed with the Trusty64 box that this is based on. I may need to change some more setup, but I'll get you working.

This lab was actually created for a talk that I gave at a local security meetup (NolaSec). So I don't have a blog post about the lab specifically, but I do have post about the content of the talk http://caveconfessions.com/xxe-ugly-side-of-xml/

@jbarone jbarone self-assigned this Jun 15, 2016
@jbarone
Copy link
Owner

jbarone commented Jun 16, 2016

@AliBawazeEer I've looked into this some more. I found that it worked right away on Mac and Linux, so that narrowed it down to a Windows issue. I found that using Edge seems to be the issue. For some reason it doesn't bother making any requests for local ips. If you use Internet Explorer, Firefox, Chrome, etc.. it works. Also if you use a proxy (ZAP, Burp) then Edge will make the connection.

I'm going to close this issue based on this research. If you are still having problems, please leave a comment, and let me know what you are seeing. Thanks.

@jbarone jbarone closed this as completed Jun 16, 2016
@AliBawazeEer
Copy link
Author

AliBawazeEer commented Jun 17, 2016

@jbarone thanks a zillion for taking the time to investigate this with me ,
i was able to tackle the issue , which is related to windows encoding within vagrant environment . as i believe nothing wrong in your vagrant , the issue in my windows encoding
how i resolve it , good to post it might be helpful for other too
in a nutshell , all you need to do is to run the following command

C:> chcp 1252


i also , have reinstalled latest versions of both virtual box and vagrant and now works perfect . .

p:s can we discuss more on the lab offline , i would really appreciate it
thanx

@jbarone
Copy link
Owner

jbarone commented Jun 17, 2016

@AliBawazeEer Glad to hear it's working for you.

I will try to put together a video walk through of the lab. That should at least get you up and running with it. You can also feel free to find me on twitter (@tygarsai) and I will be happy to answer any question you have about the lab.

@AliBawazeEer
Copy link
Author

@jbarone i have send you a follow request ,,, awaiting your request and follow back to send you a message

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

2 participants