Help Setting up a Bridge Network, Vista->LAMP

[sesproul]

Hello,

I am attempting to set up a Fedora11 LINUX, Apache, MySql, PHP (LAMP) server for development, that I can hit from my VISTA laptop, and I have a few very fundamental questions.

the Guest is up and running, with this environment.


***DISCLAIMER - I am very willing to read through other Posts, and google topics that apply, If you know the answer is well documented, please just give me the terminology to search and I'll read that first. I am new to LINUX Networking, and new to the VBox and as such am unaware often of the "Starting points" to start reading.


1. From VISTA how is the network path formed to actually point to the webserver on the Guest?
2. should I set up Bridged networking using the Wired or Wireless interface?
3. IN FEDORA, will my IP be dynamically created from the VBOX interface?
4. In FEDORA, how can I create a DNS name for the server i.e name the Webserver "FEDORA_WEBSERVER" so that from VISTA, I can point to a website like "http://FEDORA_WEBSERVER/Index.php"


Again, thanks for any help, If there is a good tutorial out there, please let me know.


Steve

[Perryg]

1. From VISTA how is the network path formed to actually point to the webserver on the Guest?
2. should I set up Bridged networking using the Wired or Wireless interface?
3. IN FEDORA, will my IP be dynamically created from the VBOX interface?
4. In FEDORA, how can I create a DNS name for the server i.e name the Webserver "FEDORA_WEBSERVER" so that from VISTA, I can point to a website like "http://FEDORA_WEBSERVER/Index.php"

1. Add the ipaddress and the name to the Vista hosts file.
2. Bridged works fine but you are restricted to having a router. Use host-only if you intend to use this without a router.
3. Use static addressing instead or if using host-only it will not matter.
4. No need if you follow #1.

[sesproul]

thanks for the feedback, so if I understand. I need to do the following :


1. Add a Static IP to the Fedora Instance.
2. Add this Static IP to the Hosts file in VISTA.

may this Static IP be anything, or is the network defined by the VBOX? *(i.e is it a 10.0.0.x network etc...)


the Hosts setting was the setting that simulates the loopback, that may work as I don't need to be visible to the regular LAN.

Thanks again - I'll try this and post my results.

Steve

[sesproul]

ok, this is turning into a great Crash course in Linux and Vista Networking...

So I changed to Host-Only, but couldn't quite figure out the Static IP in Fedora at the first shot, But after the change to the VBOX, IPCONFIG looks like this.

Code: Select all

C:\Users\Steve>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : KeyLAN
   Link-local IPv6 Address . . . . . : fe80::a455:29ef:26fe:87ae%11
   IPv4 Address. . . . . . . . . . . : 192.168.2.6
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::5d71:fa67:e34b:ce2e%14
   IPv4 Address. . . . . . . . . . . : 192.168.56.101
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 7:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : KeyLAN

Tunnel adapter Local Area Connection* 13:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 14:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:2c89:38b7:3f57:fdf9
   Link-local IPv6 Address . . . . . : fe80::2c89:38b7:3f57:fdf9%17
   Default Gateway . . . . . . . . . : ::

So from VISTA, it looks like there is a new network adapter with ip address 192.168.56.101, obviously the 192.168.2.6 is my wireless interface.

I read in one post to think like a packet, so I imagine that the 192.168.56.101 is the entry for the VISTA Hosts file maybe.

(one thing that strikes me as odd after reading some other posts, is the network supposed to be different, I work on two networks, Home and Work, and the LANS are different, with my home one the 192.168.2.x Network - Can I manually reset the Network of VBOX?

So the question is now... What settings do I use to set the Static IP of fedora?


Steve






I found this other post to gain access to the VISTA host File. http://forums.virtualbox.org/viewtopic.php?f=6&t=15507

[Perryg]

Host should be 192.168.56.1 Mask 255.255.255.0 no gateway
Guest should be 192.168.56.101 Mask 255.255.255.0 no gateway

I have no idea how it shows backwards for you but you can change the settings in the VBox main program and file -> preference -> network.
Click on the screw driver to edit or (view)

[sesproul]

thanks, I think I added the hosts-only option while at work, so it picked up the default DHCP settings from the current Wireless connection.

i just modified the virtual Boc Host only Network to statically be set to the following:

Host-only-VISTA2.jpg (37.54 KiB) Viewed 2594 times

I set the preferred DNS to the 127.0.0.1 (I read this on a page - if you feel this is wrong then I'll switch it accordingly.)


But now they both Match. As I am only going to be hitting the Guest as a DEV box, does it matter if the Host DHCP setting switches back and forth? If the VBOX is static the VISTA host file will always point correctly to that interface. 9Or at least I would expect it to)

As far as Gateway? Will setting the Wireless Gateway to empty, affect normal LAN ACCESS?


thanks


Steve

[sesproul]

On the LINUX side it looks like this now:

Code: Select all

[root@localhost ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:01:F4:27
          inet6 addr: fe80::a00:27ff:fe01:f427/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:363 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:30245 (29.5 KiB)  TX bytes:1152 (1.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

and the PING works from the VISTA side (but the more I look at it it appears as if the VBOX is responding to the Ping). But the HTTP://192.168.2.9 comes up as a broken link, I can hit the webserver from within LINUX (127.0.0.1) though.

Code: Select all

C:\Users\Steve>ping 192.168.2.9

Pinging 192.168.2.9 with 32 bytes of data:
Reply from 192.168.2.9: bytes=32 time<1ms TTL=128
Reply from 192.168.2.9: bytes=32 time<1ms TTL=128
Reply from 192.168.2.9: bytes=32 time<1ms TTL=128
Reply from 192.168.2.9: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.2.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

[Perryg]

You can't modify the settings like that. The host-only adapter is configured to use what is set in the preferences of VBox.
Look at that and you should see that it is:
Host should be 192.168.56.1 Mask 255.255.255.0 no gateway
Guest should be 192.168.56.101 Mask 255.255.255.0 no gateway
Then leave the host only adapter alone in the host (it should already be correct)
If you want to make it static in the guest you can set to to what I have above. Or leave it dhcp.
If you only have one guest it will always be the same address and you will not need to worry about it.

[sesproul]

It works!!

thanks.

so the VBOX setting for the Interface is 192.168.56.101 (this is the "Host-only Interface)
the FEDORA static setting is 192.168.56.1


the Mistake I was doing was thinking that the Interface IP of the Ethernet adapter VirtualBox Host-Only Network was the same IP as the Guest, the 192.168.56.101 was the IP of My machine on that interface. (I wasn't understanding the "dual Interface" concept that existed on my Laptop)

Then it made sense that on the other side of the Ethernet adapter VirtualBox Host-Only Network, is the interface for the Linux Guest. the "etho" 192.168.56.1 intrace (which is perceived by LINUX as a HW interface.

PerryG - Thanks for the help, I not only understand the setup now, but have a better understanding of networking in general.


Steve