I spent three days figuring out how to properly configure my Airave 3G (airvana) so it will work from behind my router. So I thought I’d share my findings with the folks on this forum and hopefully save others a lot of wasted time! I’m going to assume you know something about networks in this discussion so you may need to look up a few things if you don’t know what I’m talking about.
The goal is to configure the Airave to work in the following configuration:
This is not the “recommended” configuration since Airave would like to be before the router so it can do its QOS thing. However, since I rarely use all 20MB of my internet pipe, I don’t care about the QOS issue and if I did, I could set it up in my router anyway. Also, I want to control my ip address range, etc. so I want my router to be in control, not the lame router that is built into the Airave.
Facts about the Airave 3G that helped me:
Now, here are the steps I took to put the Airave behind my router and correctly configure it to my network. BTW, my network is setup to use the default non-routable class C: 192.168.1.1, and I wanted the Airave to have a static IP address in my network of 192.168.1.161.
I really hope this helps people. I apologize if I left anything out – I did this about two weeks ago, and I may have forgotten something!
Awesome write-up, Justin! I'm sure this will save a lot of headache for a lot of folks!
In addition to your directions I also had to do the following to make it work with my router:
- while in Airave's admin page, selected SETUP tab
- while under SETUP tab clicked on "Use Static IP Address" and added the desired IP address as well as the default gateway address
IP adddress 192.168.X.X
Default gateway: 192.168.X.X
or if we use your example then:
IP adddress 192.168.1.161
Default gateway: 192.168.1.1
This did the trick and the mobile connection was finally up and running. I did this last Saturday and it's been running without a hiccup since then.
Very helpful post thank you!
Quick question - so the only wire you have (Airave related) is from your router's LAN port to the Airave's LAN port right? Or does it go into the Airave WAN port? (I'm guessing LAN)
I did everything as stated, now I have a dreaded amber blinking "Mobile" led.
This Airave had been hooked up thru WAN since we got it in July but we are sick of the dropped calls...I thought I would try the LAN setup, but now it doesn't work at all. I guess I will keep playing.
Ethernet ports to use:
To be clear, when connecting the Airave to the router, the cable coming from the router's LAN port should be plugged into the Airave's WAN port (not the LAN port). The Airave's WAN port is where the connection to the internet (and the rest of the local network) connects. The Airave's LAN port should only be used for connecting a computer to the Airave to configure the Airave via the web interface - that's the only use for the Airave's LAN port connection in this configuration.
My ASCII diagram:
[Cablemodem or DSL]<-----> [WAN]-[Router]-[LAN]<----->[WAN]-[Airave]
Hope that clarifies it a bit.
Sorry about a late response. It looks like Justin answered you question already thou. Like he said, you should plug the network cable into the LAN port on your router and WAN port on your Airave.
I just did this (and do this kinda stuff for a living) and these are my observations.
Step 4 is unnessisary since you will not be using the lan ports. Leave the standard settings there for reconfiguration later if needed and then it'll match what the instruction manual states. Changing it has no effect on performance once setup.
All that really needs to be done is to setup the static IP on the WAN Settings page to match the rest of your network. Choose an address that is in your Routers address but not in the DHCP range of the router (or, just like Step 7 stats, setup a static DHCP Lease). Once complete, only the airvana WAN port will be plugged into the back of your router.
I observed the same performance before and after doing things this way, however, I do NOT like having this unit between the modem and router because it takes forever to reconnect to the net and this unit seems to like to be restarted.
Joel makes a good point about not needing Step 4.
The question here is if you need to connect to the Airave web server via the LAN port (which is the only way to access it), would leaving DHCP on cause problems, since the IP address it will serve up will be on a different network than the Airave iteself. Not sure how it will handle things there. Not a big deal if you don't need to access it again. Performance wise, I agree with Joel that there should be no noticible difference with DHCP on or off.
Progress is being made! It's too bad that there is so little official documentation on this device for the "behind the router" configuration. No one I know wants to run this thing as a router!
The lan ports are independant from this, and for the purposes of configuration, I would leave the DHCP server alone as it will only advertise on the LAN ports.
This device is a "router" too. So, if you put the WAN port IP on the same subnet as the LAN port, it's technically an invalid configuration. Given my current happiness with this devices flawless operation...errr anyway.. I would not "test" this invalid configuration. It will also be easier for one to remember how to configure it by leaving the defaults so that ther operations manual instructions work the same for Joe user.
So, in my professional opinion, I would not do anything to the LAN side and leave the 192.168.17.x and DHCP alone. It will not conflict with any other DHCP server that is upstream from the WAN port. The other side effect of this is that you would no longer need to disable your wireless on your laptop while plugged into this device since they are on seperate IPs. So now, you can connect to the Airave web server AND lookup this thread on the net at the same time.
Message was edited by: joelabq
One major factor also is even with this setup, some users are still having an issue. You do not need to add the AiRave to the DMZ, just make sure IPSec Passthrough is enabled on the router end.