okay, i tried 4.2.2.2 on my PC'S Tcp/ip options, but on the router, the Static DNS is set up to the openDNS's addresses. Does this matter? Anywho, i took pics.
PS- Hey Guys jst a heads up, i appreciate the help, but its important i have internet by Monday, so that means ill have to buy a new router on Monday. I hope to resolve this problem though, thanks.
This is a prime example of what happens when you are double NAT'ed and double DHCP'ed.
From the screenshot of your computers LAN config it is obvious that your modem has its own SPI/NAT firewall together with a DHCP and DNS server.
Your computer gets a local IP of 192.168.2.1xx from the modem and gets the modems local IP 192.168.2.1 as gateway for the LAN and DNS server for the LAN.
The modem is also likely to have a web server running at 192.168.2.1 for configuration.
The other side of the firewall in the modem, the WAN side, will get a public IP from your ISP together with a gateway IP to where the modem has to send its packets destined for the internet. The WAN side will also get the IP addresses of your ISP's DNS erver(s).
There is one important screenshot missing among all of those you uploaded (of which half of them are irrelevant),
the routers Status/WAN screen.
There you can see which IP your router has on its own WAN port, and what gateway IP it has for the WAN port. Your packets will go nowhere without a gateway IP there.
I am also a bit confused on how you can get that public IP 98.192.113.xxx as the routers WAN IP when the WAN connection type is DHCP in the router.
There should not be any difference between a DHCP configured computer directly connected to the modem
(getting the local 192.168.2.1xx IP) or a router with the WAN type set as DHCP connected to the router - both of them should to get a local IP from the modem.
The first thing you should do know anyway is to go into the modems configuration page and check what WAN type it is set up for. Static IP/DHCP/PPPoE
are examples of WAN type in the modem.
You could also check if there is a setting for disabling the modems NAT/Firewall.
If your modems WAN type is PPPoE then you can bridge the modem and the router.
That involves:
a) setting the modems WAN type to Bridged mode sometimes also called RFC1483 mode
b) setting your routers WAN type to PPPoE and filling in the PPPoE user name and password fields.
Username and password are those which you previously had in your modem for the PPPoE connection, you should also have got them on a paper when signing up with your ISP. _________________ WHR-G125 x1 Eko 12307M std
WRT54GL x2 Eko 12307M std
WRT610N x1 Eko 13230M big
This is a prime example of what happens when you are double NAT'ed and double DHCP'ed.
From the screenshot of your computers LAN config it is obvious that your modem has its own SPI/NAT firewall together with a DHCP and DNS server.
Your computer gets a local IP of 192.168.2.1xx from the modem and gets the modems local IP 192.168.2.1 as gateway for the LAN and DNS server for the LAN.
The modem is also likely to have a web server running at 192.168.2.1 for configuration.
It would appear that you have not read this entire thread from the beginning.
@ the OP, do you have McAfee security suite ? It is bad about detecting "new networks" and restricting access to them with no notice. _________________ Party now. The end is upon us.
okay, i tried 4.2.2.2 on my PC'S Tcp/ip options, but on the router, the Static DNS is set up to the openDNS's addresses. Does this matter? Anywho, i took pics.
No, it doesn't matter. It does matter that you reverse some recent changes back to the point that you have a 93.xxxx WAN address. That is where you need to be for any possible progess.
The process that HardReset recommended on page 1 should have fixed any problems. The fact that it did not indicates a likely firmware mis-match for your router. Did you ever try Murkffs's suggestion to use the version recommended in the peackock thread ? I would also try the official stable build on the DD-WRT main page before I purchased a new router. _________________ Party now. The end is upon us.
It would appear that you have not read this entire thread from the beginning.
I did, and I saw your suggestion that it was a faulty Ethernet cable..
Can you then tell me where the 192.168.2.xxx IP's comes from when the router is configured as 192.168.1.1? _________________ WHR-G125 x1 Eko 12307M std
WRT54GL x2 Eko 12307M std
WRT610N x1 Eko 13230M big
This is a prime example of what happens when you are double NAT'ed and double DHCP'ed.
The cable modem does not do NAT. It delivers the IP address the ISP assigns him. In this case it is 93. something. _________________ Party now. The end is upon us.
That is impossible. If your rig ip is 192.168.1.~, you should NOT be able to access your modem at 192.168.100.~.
That is not impossible, it is normal. The NAT of the router translates the subnets.
Furthermore ( unrelated to the present subject ), it is a simple matter to add multiple subnets to a NIC, and it will communicate with them all at the same time. My screen shot shows my NIC with 192.168.1.77 AND 192.168.22.177 and I communicate with devices on both subnets. The cable modem also has multiple subnets on it's LAN, and one of them is admin range of 192.168.100.x which is where the admin gui is located. 192.168.100.1 can be opened from the computer with no router between them, even when the computer has the public IP it received from the modem via dynamic host configuration protocol.
I would stick with the Micro releases for now. I'm not sure which of the two to suggest first. If you hover over the abbreviated name of the build with the mouse, it's full name shows in th lower part of the browser. _________________ Party now. The end is upon us.
I didn't see any mention of this, so have you bothered to see if your connection works without the router? Could you take a screenshot of the WAN status page. _________________ Stop using old builds. Read the forum announcements.
Looking for bricks and spare routers for testing/tutorials.
Phew!!!! Im happy to announce that the issue WAS the build...i updated and everything is working fine, Murrfk got it right on the dot. I appreciate everyones help, u guys dont know how thankful i am for ur support.
Hmm. Even I am surprised at this. Normally I am dead wrong. Now read peacock note 3 and make sure you are using a proper recommended build. _________________ Don't worry if I make sense..be thankful I'm paying attention to your issue!
http://i31.tinypic.com/24mz3ms.png
