My solution to SKYPE is to use it as little as possible. I can't even use all my minutes.
As an alternative to SKYPE, some wireless plans support UMA. You maintain your own phone number and all the wifi calls are covered under one fee.
In the states, as far as I know, only T-mobile supports UMA. When you need it, it is a godsend. I've been in buildings where cellular can't reach the interior, but the UMA worked fine over the wifi.
Google Talk is supposedly similar, but google doesn't have the failure is not an option mentality of a telecom provider. [Less so past the AT$T breakup, but you get my point.]
UMA is an interesting technological black hole. It has a real potential for hacker mischief, so public documentation is a bit slim. My ISP, which sells their own VOIP, was blocking what they considered 3rd party VOIP. They denied it, but repeated complaints made the problem go away.
This part got answered later in the thread. It's because people are ignoring the router built into the modem and adding a second router, usually for reasons unknown.
This part didn't get answered, other than the fact that some people perhaps didn't realize their modem/router combo even had a router, so they added what they thought was the only modem, but it turned out they were running two modems in series. RTFM usually helps.
One last try. This is the article that started the ummm... discussion on the modem/router/bridge/box/whatever functions:
Is there anything in this one rant that you find wrong, dubious, debatable, argumentative, fishy, etc? Actually, I just found a small mistake, but I'm not telling.
What I thought I read (repeatedly) was that since the 4200 has only 1 Ethernet LAN port, it can't possibly house a router, or something to that effect. That's completely wrong, of course, and I wanted to point out that a router doesn't need more than 1 Ethernet port. We had several exchanges on the specific topic of whether the 4200 includes a router. It does. It apparently doesn't house a switch, contrary to the User Guide, but there's no question that it houses a router.
Huh? So you've morphed from "modem/bridge only, no router" to "yes, it has a router but most of the features are disabled"? We could have just started there and agreed right off the bat rather than all of this discussion.
You should have been focusing on whether the 4200 includes a router rather than whether it includes a switch. A switch is easy to see while a router takes a (tiny) bit of sleuthing.
A neutered router doesn't magically become some other type of network element. I wonder what you would have called the Linksys BEFSR11, a one port router. There's nothing weird or unusual about a one port router. Any multi-port NAT router you can think of starts as a one port router, to which a switch is bridged.
Ok, thanks, that's probably why you call the 4200 a modem, since you're used to ignoring and/or disabling its router.
Good so far, to which I replied that forwarding all the ports to a single IP is standard router stuff. Every junk router does it. Linksys calls it a DMZ. It's barely worth mentioning, except that it's nice that they do it by default rather than having the customer explicitly do it.
But then you went on to say that forwarding all the ports to a single IP meant that adding more than one computer would result in the extra computers not working, to which I pointed out that that has nothing to do with port forwarding, but is simply the fact that only a single IP address is available. No sense worrying about port forwarding when you don't have an IP address to forward to.
I think we've addressed everything, some more than once, except your paragraph that begins with "There's one other item that might be of interest." There wasn't anything in that paragraph that made sense, so I assume your small mistake is there. I'm not worried about correcting all mistakes, especially small ones. I just wanted to figure out what you were trying to say. I'm not sure, but I think it might relate to the "redirection" topic that you kept steering back to for some reason. If so, we're done.
On the VPN stuff, I give up. My head hurts and the wall is getting damaged.
It makes sense to me. It was my initial explanation of how the DSL modem was redirecting outgoing traffic to its management port. I don't think I could explain it much better.
Agreed. I'm now behind on my year end bookkeeping and billing. If I go broke, it's your fault. Actually, I was looking for a suitable diversion.
Ok. Bug me if you want to try again. I had to learn most of that the hard way. It wasn't in any of the books on VPN setups.
I see Linksys calls it a one port router. ;-) This is better than calling it a modem I suppose. It at least warns the use to think about double NAT, DMZ, etc.
Something just dawned on me and I apologize that I didn't recognize it much earlier.
When you talked about disabling the 4200's router and how it then forwarded all ports to a single IP, I should have recognized the situation and complained right away. I think we agree that disabling the router section essentially turns the 4200 into a DSL-Ethernet bridge. Bridges operate at Layer 2 and have absolutely no concept of ports. Therefore, they can't do any port forwarding.
Port forwarding refers to rewriting the destination IP when the destination port matches a certain value, and bridges don't rewrite destination IP's. Your description of port forwarding led me to believe that the router section was still active, since only the router can do port forwarding, but I see now that you were talking about standard bridge behavior and not port forwarding at all. The use of "port forwarding" when port forwarding wasn't involved was unfortunate.
You also mentioned that, with the 4200's router section disabled, you can only plug in one computer, and you made it seem like a limitation, saying additional computers wouldn't work. Again, though, that's standard bridge behavior. Your DSL ISP probably only allows you one IP address. If you need more, you need a router. (You also tangled up the port forwarding stuff into that mess, but it has no place there.)
Next, you mentioned that the 4200 can only do NAT to one device with the router section disabled. Again, that's not quite right. Bridges don't do NAT. (Bridges operate at L2 and have no concept of IP addresses.) What you should see is the single IP address allocation allowed by your ISP. There's no NAT involved unless the router section is active.
This clears up just about everything for me. Let me know if you have any questions or clarifications.
I'm avoiding the VPN stuff. I'll test it myself someday, just to satisfy my curiosity.
I used a BEFSR11 for many years, which is why I used it as an example. In my case, the "1 port" aspect warned me that I had to supply my own switch. (I'm not sure how double NAT and DMZ issues apply here? You wouldn't pair it with another router.)
But yeah, there's no shame in a 1 port router. I think they fell by the wayside when people started expecting a switch to be included, but to be honest I typically only use 1 of the 4 ports anyway, ignoring the other 3. More and more, I'm installing Gigabit networks, so everything is Gig until I get to the single link to the gateway router, which can be 100Mb since that's still much faster than the ISP link. Everything internal flies, including mail server and other intranet stuff.
Oh, ok, it makes sense now, but only after holding the following sentence up to a mirror (since it's completely backwards): "The DSL modem intercepts all traffic on the WAN (DSL) side destined to the management IP address (192.168.1.1)."
Change WAN to LAN and DSL to Ethernet. Little things like that tend to throw me a bit.
I think I asked the same question 3 times and got the same answer 3 times, none of which answered my question, so I'm willing to let it rest. :-)
If you wanted wifi, you would have to pair it with another router, not just a switch. Well I never saw a switch with wifi. I don't think they sell the plain WAPs these days, though I still have two Dlink WAPs (B speed) if I really wanted to put a WAP on a switch.
No, you'd never intentionally pair it with a second router. If you wanted Wifi, you'd pair it with an access point, but you'd most likely connect that AP with a switch to give you a couple of wired ports at the same time.
Note that any wireless router can be configured as an access point. Sloppy installers/users will forget to do that configuration, resulting in two routers in series. Not good.
If I bought a wireless router, then isn't it far less work to simply DMZ to the the router instead of having to figure out how to make the router be a WAP? For one thing, I don't have to delve into the guts of a what the ISP peddles, but can simply use as little as necessary on the modem then do the heavy lifting on the router that I purchased which has support and detailed documentation.
What's to figure out? Disable DHCP, connect the upstream router to a LAN port versus the WAN port, and you've turned a wireless router into an access point. That's not a lot of work. If you're comparing the number of mouse clicks compared to DMZ'ing the first router to the second router, it's probably a wash at maybe half a dozen, max.
Every situation is different, but daisy chaining routers would very rarely be my first choice.
HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.