Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By fhsm on
This is hardly a Drupal question (sorry) but I'm not sure where else to ask it so here goes:
I'm working on building a Drupal intranet for a department at my school. Those who will use the system currently connect to the internet and other services over a wired connections. We have no control over that system what-so-ever. It uses DHCP to auto assign everything (ip, gateway, dns etc).
For a number of reasons we do not want to put the site on the web or on the university infrastructure. As a result we do have total control over the server.
Because almost everyone already has a wireless card I though an easy solution might be to run the system over wi-fi (over which we've got full control also). Given the back and forth nature of use it would be very annoying having to enable and disable an adapter to swap between internet and intranet. Thus I need to have two live connections and a way to route traffic accordingly. Is this possible even in theory? Does anyone have any tips on how to actually do it?
Ideally I don't want to require a bunch of config on the client side (particularly given that clients use a mix of linux, os x and win).
Thanks!
Comments
port forwarding
As you've guessed, not a Drupal question, but I think port forwarding is the answer.
The server with Drupal on it would need a virtual host to listen to the IP and the port combo you're using, hence the client would/could use an address like this: http://111.222.333.444:9999/ , the router would forward traffic on port 9999 (there's probably a better port to use) straight to the IP of the server running Drupal.