Kali IP Issue

[worthingt...@gmail.com]

I'm trying to connect to my IP through an internet browser so I can harvest some data and send it back to myself as a test as well as learning purposes. Every IP I try (192.168.1.12, 10.0.2.15, as well as my outward facing IP) my browser keeps returning that it cannot connect to this address. It's driving me crazy. Can someone school me on why this might be happening and possible solutions? It would be greatly appreciated.

[Jorgen Grahn]

We don't know your networking setup, so helping is difficult.
Do you mean you're working on a specific Linux machine, and
trying to access it using addresses you know it has?

Some things to try (assuming A is such an address, and that you want
to talk to a web server on the machine):

% ping A
% nc A 80
# netstat -tapn | grep -w 80
# iptables -vL

/Jorgen

--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .

[Joe Beanfish]

Is there a webserver running? On port 80 (or the port you're trying)?

Try "localhost" or "127.0.0.1" no quotes for the IP.

Make sure there's no iptables rule blocking it.

Does it return immediately or after a fairly long delay?
If immediate it's probably a lack of server running or route issues.
If delayed it may be routing issues or iptables blocking it.

What if you try to ping the host?

[William Unruh]

On 2014-02-19, Jorgen Grahn <grahn...@snipabacken.se> wrote:
> On Wed, 2014-02-19, worthingt...@gmail.com wrote:
>> I'm trying to connect to my IP through an internet browser so I can
>> harvest some data and send it back to myself as a test as well as
>> learning purposes. Every IP I try (192.168.1.12, 10.0.2.15, as well as
>> my outward facing IP) my browser keeps returning that it cannot

What are those IP addresses? Also if they are supposed to be the
addresses of your own machine, you would have to be running an http
server (apache) in order for your machine to respond to http requests.
(ps auxww |grep http
should show you whether or not an httpd server is running)

But this probably is not what you wnat anyway. For transferring data,
use programs such as scp, rsync.

[worthingt...@gmail.com]

Yes Jorge, I am trying to access an address I know it has from a web browser. (ex. http://192.168.1.12) Kali Linux is installed and running on Oracle's VM VirtualBox. I'm running Windows 8 the same computer. On Kali, I'm using a program that takes your IP as an input, then a web address. Kali then clones the website, and when I access the website and click on the link I created in the messages section of the website (my computers IP) it will phish for certain info and return it within the program. Kali's shell tells me my IP is 10.0.2.15. Windows cmd returns 192.168.1.12 for my IP. Those along with my outward facing when used as a url in http format all, after a delay, display a cannot connect error. Thanks guys, I'm going to try all of your suggestions and will let you know what happens.

[David W. Hodgins]

On Wed, 19 Feb 2014 15:57:06 -0500, <worthingt...@gmail.com> wrote:

> Yes Jorge, I am trying to access an address I know it has from a web browser. (ex. http://192.168.1.12) Kali Linux is installed and running on Oracle's VM VirtualBox. I'm running Windows 8 the same computer. On Kali, phish for certain info and return it within the program. Kali's shell tells me my IP is 10.0.2.15. Windows cmd returns 192.168.1.12 for my IP. Those

The default settings for a vb guest is to use nat routing, where vb
itself acts as a router. Since it's using a different subnet, the host
and guest cannot access each other.

Given the host has an ip address starting with 192.168, the host is
connecting to a router, which is most likely using dhcp to assign
the address.

Change the settings for the vb guest to use a bridged connection,
which will allow the guest to get it's address, via dhcp, from the
same router, so it will be in the 192.168.1 subnet.

If you're using static ip addresses, the network config in the guest
will have to be changed to also start with 192.168.1.

The host and guest should then be able to access each other, provided,
they are not being blocked by firewalls.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

[worthingt...@gmail.com]

Dave, it worked!! You are the man. Thanks a bunch.

[worthingt...@gmail.com]

Setting up a bridged network worked perfectly
for my local network!

Next I would like to be able to receive data
from someone outside my network.

I sent my friend my outward facing IP as a link
and when he tried accessing it, we encountered
the dreaded 'cannot connect' from the internet
browser.

What can I do as far as creating a link that
sends data from an outside computer to my
apache server?

[worthingt...@gmail.com]

Possibly port forwarding within my routers admin panel?

[moe...@gmail.com]

On Wednesday, February 19, 2014 11:23:44 PM UTC+4, worthingt...@gmail.com wrote:
> I'm trying to connect to my IP through an internet browser so I can harvest some data and send it back to myself as a test as well as learning purposes. Every IP I try (192.168.1.12, 10.0.2.15, as well as my outward facing IP) my browser keeps returning that it cannot connect to this address. It's driving me crazy. Can someone school me on why this might be happening and possible solutions? It would be greatly appreciated.

to get the data on on your friends computer you'll have to port forward the 80, and for you info, the server has a very short range so nobody from outside your country, heck your city would be able to see the page

[William Unruh]

> On Wednesday, February 19, 2014 11:23:44 PM UTC+4, worthingt...@gmail.com wrote:
>> I'm trying to connect to my IP through an internet browser so I can harvest some data and send it back to myself as a test as well as learning purposes. Every IP I try (192.168.1.12, 10.0.2.15, as well as my outward facing IP) my browser keeps returning that it cannot connect to this address. It's driving me crazy. Can someone school me on why this might be happening and possible solutions? It would be greatly appreciated.

It depends on where you are. Addresses like 192.168. or 10. are
non-routable on the outside net. There are about 100000 of each of these
addresses assigned around the world, and which of those should the
system connect to? routers will simply throw them away, unless you are
on exactly the same network they are on. Thus if you are not, you cannot
get there from here.
Your outward facing IP is just that an IP. Unless it is on your
computer, rather that on the modem/switch/router, the computer inside
that has no idea what to do
with a packet it gets for port 80. You have to tell the router wnat to
do. That is called port forwarding.

Finally, the firewall has to let packets addressed to port 80 through--
either on the router and on your computer, and your computer has to have
something (eg apache) listaning to port 80.