When we went to do the first one of these, we eventually ended up with ActionTec support and Qwest both on the line, and it turned out that the ActionTec didn't support a block of IP's with a /30 mask - it had to be /29 or greater. We gave the customer a /29, went through the setup with ActionTec, and it worked fine since. This was about 4 months ago. Anyways, the firmware that ships on the Qwest ActionTec's is a custom build for them (which is why there is so little config to do when you get one). I think this is the cause for a lot of the problems. Qwest released a new firmware version a month or so ago that may fix the routed space problems (and a security update). Nate - I checked, we don't have real instructions yet, just the stuff Justin jotted down while ActionTec support was running through with our customer. He's working on them over the next week or two, so when we get them done I'll try and remember to send something over to you. > > We've heard from a bunch of clients that they just plain don't do static > > routing in the version that Qwest ships. > > Really? Who told you that? > > Jima > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org tclug-list at mn-linux.org > https://mailman.real-time.com/mailman/listinfo/tclug-list > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list