How I hooked up VOIPo

[lost_]

So, I replaced Tomato with DD-WRT (http://www.dd-wrt.com). It's QoS is not nearly as nice as Tomato, but I'm hoping it's good enough.

I'm running Tomato on a Buffalo router -- no problem so far.

Now for the wiring hookup.

Wire from Cable Modem to WRT54GL WAN
Wire from WRT54GL LAN to RT31P2 LAN (I used Port 2)
Wire from RT31P2 LAN (Port 1) to RT31P2 WAN

Any particular reason why you needed to go through RT LAN to WAN? It's practically the same as RT WAN being connected directly to router LAN, without the dummy switching on the RT LAN.

I simply hooked up mine the way I have always hooked up ATA for years with no issue or any port forwarding needed:

Cable Modem -> Router -> ATA's WAN Port.

Also, instead of setting the static IP on the RT, just leave RT in DHCP mode and set the DD-WRT to hand out static IP to the RT. No need to manually set DNS server on the RT either.


EDIT: I read the original thread, and errr... well... if that works for you, great! (to quote DSLR: "on second thought, I do not wish to post").

[ctaranto]

Any particular reason why you needed to go through RT LAN to WAN? It's practically the same as RT WAN being connected directly to router LAN, without the dummy switching on the RT LAN.

The behavior for me is different. I'm guessing here, but possibly connecting to the LAN instead of WAN bypasses some "stuff" in the RT. I read about hooking things up this way and the poster gave a reason. I'll have to find the site/post.

I simply hooked up mine the way I have always hooked up ATA for years with no issue or any port forwarding needed:

Cable Modem -> Router -> ATA's WAN Port.

Yep. Tried that. Worked for a little while, but kept losing reauth.

Also, instead of setting the static IP on the RT, just leave RT in DHCP mode and set the DD-WRT to hand out static IP to the RT. No need to manually set DNS server on the RT either.

I could have used DHCP to assign the 172.20.0.3 address, but figured static reduces any lease and renewing issues that could happen during a call.

EDIT: I read the original thread, and errr... well... if that works for you, great! (to quote DSLR: "on second thought, I do not wish to post").

I'm not sure why, but Tomato didn't work for me with a WRT54GL. Wish it did. Maybe if I'm daring enough, I'll try it again.

[MisterEd]

EDIT: I read the original thread, and errr... well... if that works for you, great! (to quote DSLR: "on second thought, I do not wish to post").

I agree ... I've never seen such a simple installation made so confusing. Bottom line was he reset the RT and lost all the provisioning. In the end, had that not happened, the whole issue would have been a non-issue.

[ctaranto]

I agree ... I've never seen such a simple installation made so confusing. Bottom line was he reset the RT and lost all the provisioning. In the end, had that not happened, the whole issue would have been a non-issue.

For the first thread, yes, that's mostly true. But just connecting a LAN Port of the WRT to the WAN port of the RT caused reauth issues. The set up explained in this thread appears to have resolved that.

/c

[MisterEd]

For the first thread, yes, that's mostly true. But just connecting a LAN Port of the WRT to the WAN port of the RT caused reauth issues. The set up explained in this thread appears to have resolved that.

/c

You original post might mistakenly lead people to believe it has to be done that way. You might want to clarify your original post. 99.9% of the people wouldn't need to go through all that and I can't understand why you should have had to either.

[ctaranto]

You original post might mistakenly lead people to believe it has to be done that way. You might want to clarify your original post. 99.9% of the people wouldn't need to go through all that and I can't understand why you should have had to either.

I have updated the post where I begin talking about not getting Phone 1 lit. Good suggestion.

/c

[ctaranto]

I switched my WRT firmware from dd-wrt to Tomato (with hardc0re's mod to enhance performance) yesterday afternoon. Throughout last night and this morning, no loss of connection (calls are fine, no reauth issues). So far, so good.

If things go well with Tomato for the next week or so, I'll assume that the reauth issues potentially come from the NAT/firewall within the RT. Running Tomato and hooking up the WRT to the RT WAN port was problematic (at least for me).

Updates coming later...

-Craig

[tritch]

A quadruple NAT setup to get it to work It's amazing this setup is working without any problems. Personally, I would be hesitant to ever recommend such a setup.

If it's really necessary to have such a complicated setup, then it's either:
1) a bad ATA or
2) a bad ATA configuration/provisioning issue or
3) a bad router or
4) router setup problem.

It should be as simple as modem - ATA - router, or modem - router - ATA with a preferred single NAT at the most. Any other setup indicates a problem component and/or setup issue.