Ports won't foward, and another question, also need to verify something

Gabzor

New Member
Reaction score
0
hey guys i have a client who just ported at&t to verizon

the thing is any ports i open are not visible i figure because the router ip is 10.0.0.1 (netgear WNDR3400 v2)

and the modem is 192.168.2.1 (verizon actiontek)

the modem is not the newer modemrouter all in ones that verizon provides

and its not fios, but dsl with a static line.

so does the router's ip also have to be 192.168.2.1 (this is what i had to verify)

or is it 192.168.1.1?

i know as long as the subnet is the same, i can still have internet access

and i also know that all the devices connected to a network with a static ip, i probably have to change 1 by 1..


also how do i setup a dns for just one device? or do i need to somehow do it through a dmz of sorts?



also verizon didn't hook up a dsl filter, and i seem to be hearing some dsl noise even in the phone lines.. would it help at all to filter each phone + a inline filter for the dsl?


thanks guys
 
According to Verizon's website the Actiontec modems "also include routing capabilities". More than likely there is some setting in the Actiontec to set it to modem only or passthrough mode, something like that. Different manufacturers call it different things.
The very fact that "modem" has a lan ip is reason to belive it does some kind of routing. Once this is resolved you set your router to do the login to the DSLAM.

Why the hell is everything on static ip? Routers include dhcp servers for a reason.

Please clarify your question about DNS. What device, why etc?

If you are having DSL noise then filter everything including all extensions.
 
As you can tell by the private IP address of being behind the Verizon gateway..it is also a router.

So you're double NAT'd..something you do not want to do. Basically what you're stuck with is a network inside of another network which is then connected to the internet (yet a 3rd network technically).

You want to either just use the Verizon unit, or...reconfigure the Verizon unit to pass the public IP address to your own router (commonly called "bridging it")..so that your router obtains the public IP address on its WAN interface, thus port forwarding will work correct.
 
seedubya - staticip for everything, because for some reason their pos software has login problems for online orders with dynamic, so thats why they said they ported to a static

and their DVR needs a dmz + ddns to work on phones for some reason (some cheap chinese dvr)

verizon said they will put an inline, if they are still getting noise than i will put more filters


stonecat - thats what i thought, but when i went to the router, the NAT was off on it and it is indeed set as bridged mode, and the router i just entered the gateways and everything manually and any device that uses it has a gateway of 10.0.0.1
 
First your router will need to support DMZ - usually it's to a single interal IP address i.e. a DMZ host. (not really a DMz just a machine with all ports exposed to the net, except those otherwise forwared by the router, if you follow). The DDNS depends on what services are supported by your router OR you could put an updater on their server (or some other permanently switched on computer) to keep the IP updated.

stonecat - thats what i thought, but when i went to the router, the NAT was off on it and it is indeed set as bridged mode, and the router i just entered the gateways and everything manually and any device that uses it has a gateway of 10.0.0.1

This bit I'm just not following - I think you're saying that you already checked the modem - it's set to bridging with NAT turned off. The next bit I don't understand. Assuming DSL works the same in the States as it does here - on the router you would need to set up your login details, line settings (VPI/VCI) and LAN subnet. at this point.
 
Last edited:
On your Netgear...what IP shows up for the external interface in the status section on its web admin?

10ol11t.jpg


but the weird thing is on the modem
says the modem is
192.168.1.18

seedubya - i tried letting something pass through a dmz in the router, but it wouldnt show any ports as open

and yup bridged, NAT off on the modem.. login details are basically lan subnet, static/dynamic ip, gateway, dns

some you might have to mention if its pppoe or not
 
The Verizon gateway is not properly bridged yet. As you can see, on the Netgears red interface status...you have a private Class C IP address...192.168.1.18.

If the Verizon gateway was properly bridged, your Netgear router would obtain the public IP address from Verizon....this is the IP address that you most likely see when you go to some site like www.whatismyip.com

Right now as of the information in the screenshots you posted above, you're still double NAT'd. You need to reconfigure that Verizon gateway (combo modem/router). The PPPoE should be moved to your Nutgear router.
 
Did you remember to power cycle the modem after setting to bridge mode?

verizon told me specifically not to.. well the guy who installed the dsl

thanks stonecat.. they didn't mention if i should set the pppoe or not

what i don't understand is why is the modem showing the router ip as 192.168.1.18, when the ip for the gateway is 10.0.0.1?




verizon dsl tech provided me with

modem ip (192.168.1.1)
static ip, username/password
subnet
gateway
dns1
dns 2

i punched the exact info into the router
 
what i don't understand is why is the modem showing the router ip as 192.168.1.18, when the ip for the gateway is 10.0.0.1?

Any computer behind the Netgear will use the Netgears LAN interface as it's first gateway. Note that routers in gateway mode have 2x interfaces (red and green...internet and private).
 
Just wanted to add that some ISP's are using CGN (Carrier Grade NAT) for thei ipv6 transitions. With CGN instead of your ISP assigning a public ip, they assign you a private RFC1918 address. What does that mean? Means that you will have a double NAT. A NAT from your private internal addressing to the ISP's "outside" private address and then another NAT inside the ISP core to a "shared" public ipv4 address.

I know that ATT Uverse customers in some markets have been asked to change their internal addressing if they are currently using the 10.0.0.0 subnets internally or risk service interuption. This leads me to believe that they will be using that subnet for allocation on their customer facing devices for their CGN transition.

I expect to see alot of these implementations coming in the future from some ISP's.
 
Last edited:
i might have to call verizon for this one it seems.. the modem is being stubborn, and its actually just a modem.. has routing options.. no idea why :|
 
i might have to call verizon for this one it seems.. the modem is being stubborn, and its actually just a modem.. has routing options.. no idea why :|

If it has routing options..it is not just a modem. It's a combo modem/router....some of us nickname them "Brouters" because it's a router with a bridge. Most DSL ISPs have been using these for years now....you rarely ever see just plain old bridged modems anymore.
 
turns out verizon couldn't figure it out either..

copied the ip settings down from verizon

and hard reset the modem..
looks like the dsl installer set it to "routed-bridge" instead of a full bridge.. i only knew cause the internet light kept going on.. usually if its a full bridge it doesn't for these models :/

anyways thanks again everyone esp. stonecat saved my ass! :o
 
Dsl

Thats why DSL sucks lol.
Cable installs are always soooo much easiser. Plug in static IP settings and away you go.
Double NAT'ing technically works, but customers will just think the service stinks as they will have strange and random issues. We see it all the time over here. We always put the modem in bridge mode to correct it of course. Less of a problem now that most users opt for the all in one device.


Terry Moon
Computer Pro Inc
http://computerpro1.com
 
Back
Top