Differences between revisions 1 and 4 (spanning 3 versions)

Running webserver

Barrelfish webserver runs by fetching files over NFS share and serving them to users requesting the files. Currently it assumes that all files are in a flat directory without any subdirectories.

Modules needed

The webserver depends all the modules needed to get networking working, and on top of that it needs webserver module. Following is a webserver relevant part of the menu.lst

# For networking
module /x86_64/sbin/e1000n
module /x86_64/sbin/NGD_mng cardname=e1000
module /x86_64/sbin/netd cardname=e1000

# For webserver
module  /x86_64/sbin/webserver e1000 10.110.4.4 /local/nfs/website/barrelfish

The webserver takes following commandline arguments:

* cardname: Used to find the network services (This value is currently hardcoded to be "e1000" and hence ignored)
* IP address of NFS server: Used to mount the NFS location to get the files
* Path on NFS server: Where the files to serve on webserver are stored

Please refer to networking page for details about modules related to networking.

-  ⇤ ← Revision 1 as of 2015-01-11 12:21:52 → 
  Size: 1431
  Editor: shindep
  Comment:
+   ← Revision 4 as of 2015-01-11 12:43:02 → ⇥
  Size: 1108
  Editor: shindep
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
-The webserver depends all the modules needed to get networking working (described bellow).

== Using Networking in barrelfish ==

In order to use networking in Barrelfish, you will need following modules in your `menu.lst`:
+The webserver depends all the modules needed to get [[Networking|networking]] working, and
on top of that it needs webserver module.  Following is a webserver relevant part of the
`menu.lst`
-Line 14:
+Line 12:
+# For networking
 Line 17:
+# For webserver
module  /x86_64/sbin/webserver e1000 10.110.4.4 /local/nfs/website/barrelfish
-Line 19:
+Line 22:
-The first line starts the e1000n driver.  The next module `NGD_mng` provides services like port management, 
and the last module `netd` handles the background network traffic and provides services like ARP lookup.
The netd service is also responsible for getting an IP address with DHCP server.  In case you want to
give a static IP address to the NIC interface then you can pass commandline parameters providing ip address,
netmask, getway and DNS address to netd.  Here is an example:
+The webserver takes following commandline arguments:
 .* cardname: Used to find the network services (This value is currently hardcoded to be "e1000" and hence ignored)
 .* IP address of NFS server: Used to mount the NFS location to get the files
 .* Path on NFS server: Where the files to serve on webserver are stored
-Line 25:
+Line 27:
-{{{
module /x86_64/sbin/netd cardname=e1000 do_dhcp=0 ip=192.168.2.11 nm=255.255.255.0 gw=192.168.2.1 dns=192.168.2.2
}}}

Once the system is up and running (system will print the IP address it received over DHCP) you should be able 
to ping the IP-address.  If pings are working, then you have correctly configured network setup!
+Please refer to [[Networking|networking]] page for details about modules
related to networking.