I just connected my iMac (Jaguar) and eMac (Panther) to a Linksys router and my cable modem. I configured the router via my web browser as instructed and both computers can access the internet. A probem occurs however when I try to down a file such as a quicktime movie. The router "freezes" and no further data transmission takes place. I have to reset the router and it then works fine. I'm a little confused about this PPPoE setting. Do I have to turn this on on both machines? My ISP (Shaw) uses dynamic addresses.
PPPoE isn't applicable to you if your using a cable internet connection. PPPoE (Point to Point Protocol over Ethernet) is used for DSL internet users.
You may want to unplug your modem and router for a 1-2min. to release your IP. Plug in your modem then the router and that should resolve everything. Could be a matter of one of the machines holding on to the old IP address?
This way the router will pull a new IP from your ISP's DHCP server, anotther option is to call Shaw and have them release your IP if the above doesn't work.
Also, if you are using a router, there is nothing to set up on the Macs. They both get set to ethernet and DHCP. They get everything they need from the router.
Have you updated the router firmware to the latest version?
I bought a Linksys router for my mom (wired-only type router, also connected to Shaw, and no, PPPoE is not needed) and it had a very similar problem. Everything worked fine, until you tried to connect to Windows Update (yes, my mom's using XP - I'm working on that) or a site with a Flash animation. Then the router locked up solid, and all you could do was hit the reset button on the back to get it up and running again. The really funny thing is her other system, an old Win98 box, could hit Windows Update with no ill effects - it was really weird. First, we exchanged it for a new one, figuring it was just DOA-ish. Same problem. Then, I phone Linksys tech support a couple times to try and get an answer, but never got one. They said it was a known problem, but really didn't have a good answer as to how to fix it. But then magically a few weeks later a new firmware update showed up on their site which fixed the problem (the release notes didn't say it would fix the problem, but it did).
So, my first suggestion is to make sure you're running the latest firmware. Even if the release notes don't say anything about your particular problem, it may fix it anyway.