site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
34775
Share Topic
Posting?
Post a:
Post a:
Links: ·AT&T West Line Monitors ·AT&T West FAQ ·General SBC FAQ ·PBI Reviews ·AT&T Services
page: 1 · 2 · 3
AuthorAll Replies

networKnoob

join:2011-11-18
Arlington, TX

reply to StLCardsFan

Re: [Home Network] Motorola NVG510 (IPDSLAM) IP Passthrough

We actually have a client that just got the IPDSLAM service. They have the NVG510 with 18Mbps. This is a business account and they would not walk me through the setup to get it to talk to a tz100 sonicwall firewall/router correctly. They wanted to charge $15/month for support plus. They couldn't even tell me if would work properly with a sonicwall tz100. I'm not going to sign up for a support contract if it's not guaranteed to fix the issue!

I attempted to get it working properly myself by setting up ip passthrough to the sonicwall.

I used the dhcp-fixed settings as per this article.

http://broadband.custhelp.com/app/answers/detail/a_id/21989

Then I setup the sonicwall with the following information

X0 WAN Primary IP: 108. ipv4 broadband ip address from NVG510
GATEWAY: 108. ipv4 gateway address from NVG510
DNS: pointed to 192.168.1.253(NVG510 local ip) and also tried the dns servers listed in the NVG510 as well
subnet: Tried 255.255.0.0 and 255.255.255.0

I had a cable running from port 1 on NVG510 to WAN port of Sonicwall and a cable running from the LAN port of the sonicwall plugged directly into my laptop. With any of the combination of settings above I could never get out to the internet nor access the sonicwall or NVG510 locally.

Am I going about this correctly? BTW, Motorola gave me the link above so I did get help from them. I also read about an other feature called router cascading. Would this apply in my this case?


wayjac
Premium,MVM
join:2001-12-22
Indy
kudos:1

The dhcps-dynamic and dhcps-fixed both require the ip passthrough device to be configured as a dhcp client

You need to select the manual option when you want to set the tcp/ip info on the ip passthrough device

You should also make sure that the ip passthrough device uses a subnet other than 192.168.1.0 that is the default subnet of the 510


networKnoob

join:2011-11-18
Arlington, TX

Is it possible to change the subnet of the nvg510? I am not around the device so I am unsure right now. Our sonicwall, servers, and workstations use the 192.168.1.0 subnet and it would be too much work to change all that around for the internet connection.



wayjac
Premium,MVM
join:2001-12-22
Indy
kudos:1

said by networKnoob:

Is it possible to change the subnet of the nvg510?

Click on the home network link.......then click the subnets & dhcp link

networKnoob

join:2011-11-18
Arlington, TX

reply to networKnoob
So I finally got the NVG510 working properly with the Sonicwall TZ100! My settings are as follows.

Firewall > IP Passthrough

Allocation Mode: Passthrough
Default Server Internal Address: blank
Passthrough Mode: manual
Passthrough Fixed Mac Address: Sonicwall mac address

Note: When you select manual it doesn't let you type anything so I selected dhcp-fixed then put it in and changed it back to manual. However this may not even be needed for manual mode.

Home Network > Subnet & DHCP

Default IPV4 Address: default
Subnet Mask: default

DHCP v4 Start Address: default
DHCP v4 End Address: default

Public Subnet On:
Public IPv4 Address: my public gateway address
Public Subnet: subnet for my public ip subnet which ends in .248
DHCPv4 Start Address: first useable public/static ip address
DHCPv4 End Address: Last useable public/static ip address
Primary DHCP Pool: public

Home Network > Wireless: off

Sonicwall Configuration:

Wan Primary IP Setup: public ip, dns, and gateway provided for static ip.

Everything works now with NVG510 plugged into the WAN port of the sonicwall and then the main switch plugged into the LAN port of the sonicwall.



wayjac
Premium,MVM
join:2001-12-22
Indy
kudos:1

It looks like you didn't change the ip address of the nvg510 is this true?

Why did you make changes to the public subnet settings


lenzar

join:2011-12-23

reply to networKnoob
networKnoob
Would you please explain in more detail the configuration you have done in the Sonicwall Thanks!



SeanL

@sbcglobal.net

reply to webcrawler42
I got it to work as a modem with a WRT140N

So when you plug in your router to the wireless gateway, the gateway will assign it an ip address. This is the casade router ip address. So for me, it was 192.168.1.64. You also need to set the ip addresses and subnet that the router is in, so for me my router is in 192.168.2.0 with subnet 255.255.255.0. Its internal ip address is 192.168.2.1, and its external is 192.168.1.64 (need to be different subnets for this to work).

Also on the wireless gateway, set up default server (i think its in the ip passthrough section). Just tell it to send all traffic to your router (i.e 192.168.1.64). Passthrough doesnt work, default server does!

Disable wireless on the gateway while you're at it.

Now go to your router and make sure that it's internet address is 192.168.1.64 (should get it automatically). Make sure its internal address is correct, and that its in the subnet you specified on the cascade router section. Now restart everything (gateway, router, computer), and you should be good to go.

The main thing is you need default server and cascade router on the gateway, and your internal ip and external ip for your router need to be on different subnets.



tcaradonna

@sbcglobal.net

Why are people making such a big deal about turning off the wireless? If you are using the passthru on the NVG510, how are you going to access the router to make changes other than directly wiring a connection to it?

I suggest keeping the wireless on, but only using it for easy modem servicing. Use your regular firewall/router for normal household internet traffic. That's how I'm using it, and I'm quite happy with the setup.

I also heard directly from a ATT service tech that there is an update scheduled very soon for fixing this dynamic IP passthru problem, which is a known issue to them.



wayjac
Premium,MVM
join:2001-12-22
Indy
kudos:1

said by tcaradonna :

If you are using the passthru on the NVG510, how are you going to access the router to make changes other than directly wiring a connection to it?

Just by typing the nvg510 ip address into a web browser


kernel

@sbcglobal.net

reply to tcaradonna
I am accessing the NVG510 through my regular router.
Both of my devices are next to each other and will create wireless interference.
So disable the wireless on the NVG510.

Tutorial:

»www.ron-berman.com/2011/11/24/mo···e-users/



jables

@sbcglobal.net

reply to wayjac
Yeah but how would someone get the wpa-2 key?



kernel

@sbcglobal.net

You get the WPA2 key from your own router, not the NVG510.

You are accessing your own router wirelessly, then your own router connects by a cat5 cable to the NVG510.


cFig

join:2012-02-02
Searcy, AR

reply to webcrawler42

said by wayjac:

A public ip address with a subnet mask of 255.255.255.255 is very normal

I don't know if that's true, but I know I had the same problem with my NVG510, and all I did was switch from "DHCPS-fixed" to "manual" in the NVG510 GUI and switch to Static IP for my internet connection type in my Linksys/Cisco E1000 and it automatically registered ip, subnet mask, gateway, and dns server addresses in each respective field. I simply changed the subnet mask back to what it was before I used IP Passthrough, and switched the DNS servers to 68.94.156.1 & 68.94.157.1 respectively (these are the dns server addresses for at&t service).

I know that this ip address can change over time, but I've found that it usually doesn't unless I upgrade my service, which usually ends up with me getting a new gateway anywho. If you decide to use my method, and one day your internet goes out, all you have to do is switch back to "DHCPS-fixed" in the NVG510 and DHCP in your linksys, reboot both, then switch them back to "manual" and Static IP, and replace the subnet mask and dns server addresses again.

Sure, it could be a bit of a headache if your IP changes very often, but in most cases, I've found that it doesn't. Cheers!

Sunday, 03-Jun 18:10:36 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics