| Westell 6100 in "Bridge" mode but no WRT54G Port Forwa I'm on ADSL through Cincinnati Bell's Zoomtown service. I have a Westell 6100 that I connected directly to my computer. I accessed it's web config via 192.168.200.1 and I changed it from "routed bridge" to "bridge" and I've turned off DHCP on it.
That Westell is then plugged into a Linksys WRT54G running the Linksys firmware (this is one of the 2MB models and DD-WRT micro didn't run well on it.) The WRT54G is accessed via 192.168.1.1 and it's getting the external 74.xxx.xxx.xxx IP address. I've cloned the MAC address of the Westell onto the WRT54G.
On my Windows 7 computer I assigned a static IP. I then setup port forwarding (both TCP & UDP) on the WRT54G opening the ports to my Windows 7 computer.
But the ports aren't reachable. The applications report that they're un-reachable and so does Canyouseeme.org.
Any suggestions? It's been at least 4 and half hours since I switched the Westell into bridge so the DHCP lease should have expired. Cincinnati Bell/Zoomtown doesn't use PPPoE and there isn't a login I need to enter. |
|
 wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | Re: Westell 6100 in "Bridge" mode but no WRT54G Port F said by DorcasGood:I then setup port forwarding (both TCP & UDP) on the WRT54G opening the ports to my Windows 7 computer
But the ports aren't reachable. The applications report that they're un-reachable and so does Canyouseeme.org The program that's going to be using the ports must be up, running and listening on the ports
Use the canyouseeme.org to check the ports again then have a look at the westell firewall log it will show if the firewall dropped the traffic or passed it to the lan device |
|
| Still no go. The three apps I'm trying to get working are Bittorrent, Soulseek, and RealVNC. RealVNC starts with Windows and runs as a service. The other two I launched one at a time and tested but they're reporting the ports are blocked (and so does canyouseeme.org). |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | Can you post the contents of the westell firewall log |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | reply to DorcasGood
I'm asking for the westell firewall log when I should be asking for the linksys firewall log |
|
| reply to DorcasGood
Hmm, the WRT54G has an option under Administration > Log and I clicked "enable". But under that are two buttons: Incoming Log and Outgoing Log. Clicking on those gives you a popup window with the source IP and destination port. That's it.
Is there another way to get at it? |
|
|
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | Sounds like you need to do the port check again then look at the log
This ip address should be in it 204.16.252.112 |
|
| I am such a dumbass. I had my static IP set to ".30" instead of ".130". Thanks for trying to help, guess I just needed a fresh morning to look at this after spending the last 5 days assembling and setting up a new computer and router. Sigh. Thanks again! |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | The firewall log would have shown that |
|
| Yeah I'm just not sure the WRT54G has a detailed log like that. It just shows the port # not the IP it's sent to. Seems to be a really stripped down router that nobody likes from what I've found on the internet. Sounds like a good reason to upgrade to the WNDR3700  |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | Would you mind enabling the log and posting it's contents |
|
| There isn't a way to get a text file of the logs but here are some screen shots.
WRT54G Log 1.png shows the admin screen on the router where I've turned the log on.
WRT54G Log 2.png shows the window that appears when I click the button labeled "Incoming Log". It just shows the destination port not any of the port forwarding information that would include the destination IP.
WRT54G Log 3.png shows the window that appears when I click the button labeled "Outgoing Log". It just shows the my IP, the destination IP, and the destination port. |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | Thanks!!! for posting this information
If I'm not mistaken the incoming log only shows traffic for ports that have been fowarded no other incoming traffic is logged
Not showing the incoming local ip is odd when the outgoing log lists the local ip, public ip and port number |
|
| Ooh good point, I'll have to check if it only shows for ports that are forwarded. I'll try it tomorrow.
Yeah, it's pretty sparse, like I said, gives me another excuse to upgrade |
|
wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | said by DorcasGood:Yeah, it's pretty sparse, like I said, gives me another excuse to upgrade I don't see the lack of information as a bad thing this type of information is seldom looked at or used
It is a handy troubleshooting tool |
|
