If there is no function in V4 that you require, we would suggest downgrading to V3.30 for routers. V4 is only suggested if you have wireless cards in the router needing 802.11n support. Many customers have found issues in higher versions of the OS, some are still running V2.9, it just depends on what functions you need on that router.
Give it a try... Regards, Titan Wireless WISPA Vendor 3914 Gattis School Rd Suite 102 Round Rock, TX 78664 Office (512) 942-6069 Fax (877) 538-6571 www.titanwirelessonline.com The content of this message is Titan Wireless LLC Confidential. If you are not the intended recipient and have received this message in error, any use or distribution is prohibited. Please notify me immediately by reply e-mail and delete this message from your computer system. Thank you. Grant Stufft wrote: > Hi, > > Any MT gurus hanging out tonight. We have a powerouter 732 that we > upgraded from v3.22 to 4.17 tonight. When we upgraded it complained > about a new license and we did the automatic upgrade and it rebooted > just fine. The problem is that I cannot reach it now via the public > ip addresses. Was working great before the upgrade. I can access it > just fine over the two routed internal interfaces but not the masq > interfaces. We have three different sources of bandwidth on 3 of the > ethernet interfaces and two of the ethernet interfaces have our > rfc1918 addresses with clients on them. There are masq statements for > each of the 3 bandwidth interfaces for 192.168.0.0/16 > <http://192.168.0.0/16> to only go out that particular interface. We > then use policy routing to send the traffic out the different > interfaces. It was working fine until the upgrade. Now torch shows > that there is no traffic going over the interfaces. If you go to the > nat statements and look at the masq statements, the counters are > increasing like they are being hit but the traffic is not leaving the > interface. > > Any idea what may be happening or more importantly what information is > needed to properly get this working again and fixed? Worked very well > before and to my eyes, everything looks good. > > Thanks > > > ------------------------------------------------------------------------ > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
