| [Wireless] WRT54G2 + Motorola 2210-02 Port forwarding does not w As said in the title i'm using a WRT54G2 router, a Motorola 2210-02 DSL modem with ATT DSL, and a Linksys wireless USB adapter. My girlfriend is connected by ethernet to the router using her onboard lan. I cannot get port forwarding to work for the life of me.
Modem IP: 192.168.1.254
Router IP: 192.168.0.1
My IP: 192.168.0.101 always
Gf IP: 192.168.0.100 always
Modem's port forwarding screen:
»img193.imageshack.us/img193/8620/modem.jpg
Router's port forwarding screen:
»img38.imageshack.us/img38/7329/router.jpg
Now.. what in god's name is 192.168.1.2? When forwarding ports from my modem this is the "host device" IP but I haven't the foggiest clue what that is supposed to be.
I've tried 3 different port checkers and none of them are open. I also tried assigning a static IP to my PC and not only did it not work, I couldn't access my modem anymore for some reason even though I was still connected to the net.
Any help? |
|
|
|
 SSidlovOther Things On My MindPremium
join:2000-03-03
Pompton Lakes, NJ
 ·Optimum Online
| Re: [Wireless] WRT54G2 + Motorola 2210-02 Port forwarding does n Why don't you try to change your router's IP to 192.168.1.2? Linksys routers usually have this in the basic setup. Then the modem will forward to the route (which it thinks is the HOST (unless it's intended that the setting is opening outgoing ports) and the router will have open ports forwarded to your PC. You will have to make sure your PC's point to the router's new IP if you change it.
Though if there is a way to make the modem a dumb bridge instead of a semi-router, I'd do that... |
|
| reply to nfef
I guess I could try that.. the router defaults to 192.168.1.1 but I changed it to 192.168.0.1 because when I was setting it up to begin with all the guides i've read say you shouldn't have the router on the 192.168.1.X IP because it will conflict with the modem.
How would I go about just putting the router in bridge mode? |
|
 NetFixerFreedom is NOT freePremium
join:2004-06-24
The 'Boro
 ·Vonage
 ·Cingular Wireless
·Comcast
 ·AT&T Southeast
3 edits | said by nfef :
How would I go about just putting the router in bridge mode?
It is difficult to tell who your ISP is because your first post shows "@bellsouth.net" and your next post shows "@qwest.net".
However, if you are actually in the former BellSouth area and your ISP is AT&T, you might want to look at these AT&T SE Forum FAQs:
»AT&T Southeast Forum FAQ »How do I set a Motorola 2210 to Bridged Ethernet mode
»AT&T Southeast Forum FAQ »How do I properly setup a Motorola 2210 modem with a Linksys router?
If Qwest also uses the Netopia 2210, the instructions might be similar, but most ISPs customize their modem/router firmware so I can't guarantee that the steps would be identical.
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
»portscan.dcs-net.net
»nature-pics.com |
|
| That's because my first post was from home and my second post was from work. 
Anyway I put the modem in bridged mode about 10 minutes ago, using my Linksys to do the PPPoE.. and using port checker tools online my ports are still closed. I don't get it. Windows firewall is off, router firewall is off, ports are set to forward to my IP...
I'm seriously stumped. |
|
NetFixerFreedom is NOT freePremium
join:2004-06-24
The 'Boro Reviews:
·Vonage
·Cingular Wireless
·Comcast
·AT&T Southeast
4 edits | All I can suggest at this point is that you check the Netopia 2210 settings shown in the images below. If all the firewall settings are "off", then the problem is with your Linksys router or your PC security settings. You might try doing a factory reset on the Linksys router and then restoring your settings to see if that helps.
FWIW, I don't forward the ports that you are trying to forward, but I do operate public servers on my AT&T DSL circuits using Netopia 2210 modems in bridge mode and a Linksys RV082 router and the numerous ports that I forward are not blocked. To my knowledge, AT&T does not block the ports that you are trying to forward.
EDIT: I just happened to notice something in your post. You said that the ports were "closed", not "blocked" or "stealth". The reason for that may just be that your server was not running when you tested the connection. A port showing as "closed" is normal when the port is not blocked but the service using the port is not running. I have posted below the result of a test I just did at the GRS ShieldsUP site showing the results when I forwarded port 80 and port 8080 to the same server. That server has a web service running on port 80, but not on port 8080. The port 8080 test shows the result as "closed" (as should be expected).
Here is the result of the same test when port 8080 is not forwarded (stealth, not closed).
Here is the result of one last test after port 8080 was forwarded to a server that was listening on port 8080 (just to show that it does actually work).
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
»portscan.dcs-net.net
»nature-pics.com |
|
