Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Installing CentOS 5.5 on Virtual Box Post 302484787 by motoko on Monday 3rd of January 2011 08:26:44 AM
Old 01-03-2011
Installing CentOS 5.5 on Virtual Box

Hi,

I have installed VirtualBox, downloaded CentOS 5.5 and created a VirtualMachine where i have installed the 'server' versión of CentOS 5.5

As I installed Virtual Box a new network device appeared '192.16.1.250' in my 'real' machine. I was unable to reach my webserver so i istalled CentOS once more with the server gui trying to get more information... inside my vm my IP is 10.0.2.15 i can reach apache using localhost or 10.0.2.15 but i can't reach my server from outside the vm... i have tried both 192.162.1.250 and 10.0.2.15 from other computers in the same net, but i dont any respone.

I can load websites in my vm so i have internet access. I have disabled the firewall in the vm but that doesn't solve the problem... any clue where the problem is?
 

9 More Discussions You Might Find Interesting

1. Ubuntu

CentOS, Fedora & RedHat in 1 box

Hi Linux gurus, My boss had asked me to setup a box consisting of this 3 OS (CentOS, Fedora, RedHat) for autopatching. So, whenever there is new patches for CentOS from the internet, this box will grab it, implement it, if tested ok and approved, the patches will then be push to Production... (23 Replies)
Discussion started by: raybakh
23 Replies

2. Solaris

virtual box images

Does anyone know if you can use a virtual box image on different O/S's and be able to move it from one server to another of different O/S if needed? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

3. Windows & DOS: Issues & Discussions

Virtual Box

I am trying to create a new virtual machine (Red Hat) but I am getting the following error I am completely new to VB and I am probably missing something. Any help will be greatly appreciated. (4 Replies)
Discussion started by: Xterra
4 Replies

4. Red Hat

deleted a virtual machine with critical data under CentOS

Hi all, I'm in a pretty messed-up situation, hope you can give me a hand. I deleted by accident a folder containing a VMware server virtual machine, that contains most critical information. The host OS is CentOS 5.5, which I believe by default uses Ext3. I shut down the PC intermediately... (2 Replies)
Discussion started by: starriol
2 Replies

5. UNIX for Dummies Questions & Answers

Sun Virtual box

hi Am Using Windows vista machine where i installed Sun Virtual Box on Which i installled Solaris 10.. am not able to ping my windows machine from Sun OS neither viceversa.. Can someone help me out to get this sorted please .... (2 Replies)
Discussion started by: Sojourner
2 Replies

6. Red Hat

Resizing root virtual disk on the CentOS

Hello, Can someone suggest me what I missing, I re-sized a root virtual disk to 30GB on the CentOS VM. After re-sizing the disk, I booted the OS and ran fdisk -list command I was able view the size of the disk as 30GB. Paritions in the vm before I resize are: /boot - Primary parition /... (1 Reply)
Discussion started by: bobby320
1 Replies

7. Solaris

Change hostID of Solaris 10 virtual/guest machine installed by Virtual Box 4.1.12 on Windows-XP host

Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12). I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies

8. IP Networking

ssh on virtual box (4.0.4)

Hello, I have two virtual machines ubuntu on virtual box vm1 and vm2 , i'd like to use ssh to connect from vm1 to vm2, please what's the configuration should do? Thank you (1 Reply)
Discussion started by: chercheur857
1 Replies

9. Red Hat

Hack a centos Linux box

HI, I have a Centos linux box and there is interface connect to internet. I stop the iptables in this box . After a few day , I find the linux box have been hacked and install some perl script into the box . Could anyone tell me how the hacker can login into the centos box without knowing... (1 Reply)
Discussion started by: chuikingman
1 Replies
RSOCKD(8)						      System Manager's Manual							 RSOCKD(8)

NAME
rsockd - SOCKSified SOCKS server SYNOPSIS
rsockd [ -ver | -i | -I ] DESCRIPTION
rsockd is the SOCKSified version of the SOCKS server sockd. Functionally rsockd is identical to sockd except that it may (though not nec- essarily has to) make use of other SOCKS servers to reach some destinations. A number of rsockd's can be strung together or organized in a cascade or other more complicated structures to serve the needs of a particular network configuration and restrictions. Obviously this complicates the issues and make the setup and maintenance of the firewall more difficult. So use sockd instead whenever you can. This document only describes the features of rsockd that are different from sockd. You should read sockd(5) carefully to gain a basic understanding of of how the SOCKS server works. When rsockd receives a request, it checks the request again its configuration (in exactly the same way that sockd does) to decider whether the request is to be accepted. The primary difference between sockd and rsockd is in how they establish connection to the destination host of a accepted request. sockd assumes that it can connect directly to the destination host and proceeds to do so. rsockd makes no such assumption. Instead, it consults another configuration file to decide whether it can connect directly to the particular destination host or whether it has to use a proxy connection through another SOCKS server. In other words, it behaves just like a versatile SOCKS client in this regard. Therefore rsockd requires not only the SOCKS server configuration file /etc/sockd.fc or /etc/sockd.conf to decide whether to accept or reject a request, but also the client configuration file /etc/socks.fc or /etc/socks.conf to decide how to reach the destination host. If it is a multi-homed version and supports RBIND, it also needs the route file /etc/sockd.fr or /etc/sockd.fr to decide which net- work interface to use for a connection. Look at it in a different way, you can think of sockd as a special case of rsockd, one which can connect directly to all destination hosts. In fact, an rsockd using the client configuration consisting of only this line direct ALL 0.0.0.0 is functinally identical to the regular sockd. Anther thing to mention is related to the use of identd. Only the SOCKS server which the requesting host directly connects to can find out the identity of the real user. Suppose user x on host C connects to rsockd on server B which in turn connects to sockd on server A in order to reach destination z. Host B can query identd on host C to find out whether the user is indeed x. To host A, the request appears to orig- inate from user x on host B. An identd query from Host A to host B returns the userid that owns the rsockd process on host B, not the real user x. OPTIONS
See sockd(8). EXAMPLES
The follwoing is an example of the client configuration file. See related man pages for examples on server configuration and route files. # /etc/socks.conf for rsockd of domain rnd.xyz.com # # Use proxy connection through SOCKS server on socks.market.xyz.com # to reach hosts within market.xyz.com sockd @=socks.market.xyz.com .market.xyz.com 0.0.0.0 # # Use direct connect to all other hosts within xyz.com direct .xyz.com 0.0.0.0 # # Use proxy connection through SOCKS server on gateway.xyz.com # to reach all others sockd @=gateway.xyz.com ALL 0.0.0.0 FILES
/etc/sockd.fc, /etc/sockd.conf, /etc/sockd.fr, /etc/sockd.route, /etc/socks.fc, /etc/socks.conf, /etc/inetd.conf, /etc/services, /var/adm/messages, /etc/syslog.conf SEE ALSO
sockd(8), socks_clients(1), sockd.conf(5), sockd.route(5), socks.conf(5), make_sockdfc(8), make_sockdfr(8), dump_sockdfc(8), dump_sockdfr(8) AUTHOR
Ying-Da Lee, ylee@syl.dl.nec.com May 6, 1996 RSOCKD(8)
All times are GMT -4. The time now is 09:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy