I am on a local area network that has no external access to the internet. However I have been tasked to find a way to allow certain machines to access the web (HTTP, HTTPS, etc) via a wireless card on their laptop. So my question is, is there a way to tell the browser which NIC it should be using. Such as setting up IE for the local LAN, and say FireFox for the WAN? The browser setup doesn't really matter all that much just that one browser is LAN only and one browser is WAN only.


It's rather question of routing. Default route through WiFi, while route with your local LAN mask through Ethernet.

Assuming, that WiFi card has IP and Eth card you'd have routing table something like:

Network Address   Netmask          Gateway Address  Interface       Metric      1   1

See MS KB article on basic routing.

  • Do you even need to make the default route through the WiFi? If the WiFi has the route to the Internet, and the LAN does not, then the WiFi should be chosen as the path for any IP address on the Internet, shouldn't it? – John Saunders May 7 '09 at 11:18
  • You meant like some magical auto-discovery? I'm not sure how well would that work. With static routing there's no need for guessing. – vartec May 7 '09 at 11:21

What kind of environment are we talking about? The problem here is introducing an internet connected host practically bridged into your isolated local network. I doubt finding a way to access the internet included uncontrolled access from those machines across both networks at the same time?

If the wifi-connected clients gets compromised or even just slightly misconfigured you'd open up the entire local network for grabs depending on its configuration (do you use domain isolation and require ipsec and isolate all clients from eachother?).

It sounds better to just set up a firewall (and/or a proxy as suggested) on the local network that allow whatever http traffic you need for the specific clients only. That way you're still in control.

But if not, then I'd simply disconnect the client from the local network and only use the internet-facing wifi when needed - with no local network access available. That'd feel a tiny bit more secure if it was me anyway. The local client firewall could be configured to lock things down when not connected to the domain/local network. It's still scary though ^^

  • +1 - this sounds like a management-imposed security failure. If the wireless isn't properly locked down and a malicious person gets onto it, they can then hack one of the clients and get onto the network which isn't connected to the internet. You'd be better off banning wireless and having a proper firewall and/or proxy on the wired network. – pjc50 Nov 25 '09 at 14:31

You don't tell the browser, this is done at OS level.

Just make sure there is a gateway specified for the wireless card in the TCP/IP settings and not for the Ethernet card.

That way it'll route LAN traffic over the Ethernet and anything it doesn't know about over the wireless.


This is really a routing question ... Just make sure the default route is set for the wireless gateway


Nathan is right about it being OS level. Can you not instead put a proxy server in place? That's one of the big main purposes for them.


You can setup a proxy in a browser, that will allow them outside access. You can configure that in Firefox or IE individually.

Depending on the IP address you should be able to route that through the Ethernet or Wireless adapter.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.