IP Address for Modem and for Router

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › IP Address for Modem and for Router

alisam

878 posts

Ultimate Geek
+1 received by user: 83

#196261 25-May-2016 07:06

I recently moved to using a separate modem and router (in the garage).

When I set up the Modem it was 192.168.1.1. Then I ran a piece of software which set the modem in bridge mode.

I set up the Router, again with 192.168.1.1 and both are working OK.

Later it dawned on me that I couldn't access the Modem using 192.168.1.1.

If I can give the modem a separate IP address from the Router then would I be able to access the Modem?

If so, how should I do this:

Router: 192.168.1.1 (and IP addresses to start at 192.168.1.3)?

Modem: 192.168.1.2?

or should it be vice-versa

or something else.

PC: Dell Inspiron 16 5640 (Windows 11 Home), Dell Inspiron 7591 2n1 (Windows 11 Pro), HP ProBook 470G1 (Windows 10 Pro), Intel NUC7I5BNH (Zorin)
Net: Grandstream 1 x GWN7062 Router, 1 x GWN7665 Access Point
Storage: Synology DS216play NAS, 2 x 6TB
Media: 3 x Amazon FireTV. Echo, Dot, Spot
TV: 2 x Samsung H6400 55" LED TV, Panasonic TH-P50G10Z 50" Plasma TV
Mobile: Samsung Galaxy A52 5G
Wearable: Gear S3 Frontier

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1559097 25-May-2016 07:16

You would need to give the modem a static IP address on a different subnet and then create a static route in your router to point to the WAN interface.

Depending on the type of router it's entirely possible that this can't be done.

alisam

878 posts

Ultimate Geek
+1 received by user: 83

#1559099 25-May-2016 07:23

sbiddle:

You would need to give the modem a static IP address on a different subnet and then create a static route in your router to point to the WAN interface.

Depending on the type of router it's entirely possible that this can't be done.

Vigor 130 and Edgerouter Lite 3 (probably overkill for me, but no point aiming low)

Behodar

11099 posts

Uber Geek
+1 received by user: 6082

Trusted

Lifetime subscriber

#1559102 25-May-2016 07:30

For what it's worth, when I had a similar configuration I found it was easier to plug a PC directly into the modem when I needed to reconfigure something. When in bridge mode, it's rare that I had to change anything on the modem.

Be warned that you lose NAT when plugged in directly, so make sure you have a firewall or other secure system :)

michaelmurfy

meow
13580 posts

Uber Geek
+1 received by user: 10912

Moderator

ID Verified

Trusted

Lifetime subscriber

#1559130 25-May-2016 08:14

1) Set the Draytek in bridge mode, set an IP on it (192.168.2.1) and ensure you're using the PPPoE passthrough feature.
2) On your ERL once everything is working set the interface (lets say this is eth0) up with an IP:

3) Enable NAT Masquerade to this too - set up a "Source NAT" rule like so (Firewall/Nat --> NAT on the ERL)

You should now be able to access http://192.168.2.1 on your ERL from your networked clients. This is from memory, and I have been up most of the night due to Thor + Wellington so not 100% sure if it is correct.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#1559529 25-May-2016 18:42

as others have said, stick it on another subnet. Most routers will happily route it long as its setup right, otherwise a simple static route and you will be away.

There are some modems that get a little grumpy at telnet connections outside of its subnet, natting would be required in this case.

for my setup i have 192.168.x.254 for modems, x being where each WAN is.

i have a separate virtual network within the router going out the specified WAN port for both the modem management 192.168.x.0/24 and a second one for VLAN 10 for internet itself from the router.

my lan sits on 10.3.57.1/24 (although this is becoming a push for a larger subnet.)

vpns, guest network, management etc all sit on 10.x.x.0/24 variants.

running 192.168.1.0/24 on both your WAN and your LAN is only going to confuse things in terms of routing.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

alisam

878 posts

Ultimate Geek
+1 received by user: 83

#1561072 28-May-2016 07:53

michaelmurfy:

1) Set the Draytek in bridge mode, set an IP on it (192.168.2.1) and ensure you're using the PPPoE passthrough feature.
2) On your ERL once everything is working set the interface (lets say this is eth0) up with an IP:

3) Enable NAT Masquerade to this too - set up a "Source NAT" rule like so (Firewall/Nat --> NAT on the ERL)

You should now be able to access http://192.168.2.1 on your ERL from your networked clients. This is from memory, and I have been up most of the night due to Thor + Wellington so not 100% sure if it is correct.

I didn't get very far.

Attached a laptop to the Draytek and couldn't get the login page.

Tried 192.168.1.1.

ipconfig said the Gateway was 47.72.179.254 (owned by Vodafone), but again I couldn't get in.

Should I do a Factory reset and start again, because at the moment I cannot get into the Modem.

Are there any advantages of using 192.168.2.1 over 192.168.1.1?

Dyson

Shop now for Dyson appliances (affiliate link).

mentalinc

3384 posts

Uber Geek
+1 received by user: 1023

Trusted

#1561075 28-May-2016 08:20

Looks like the dreytek is already doing PPPoE.

CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440

Quic: https://account.quic.nz/refer/473833 R473833EQKIBX

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#1561350 28-May-2016 18:06

regardless of if your running vdsl or adsl there, if your dreytek is tagging vlan 10, your computer will get a ip via dhcp. - dont use dhcp for internet on vodafone unless your on fibre, in my experience it just utterly fails after awhile, normally when your peaking out your line. Suspect some sort of queuing on Vodafones side.

set a static ip within the local ip space (192.168.1.1/24 in your case) to connect to the vigor130.

ild bet this is the case and its not a pppoe session on your vigor130 at all.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

Spyware

3818 posts

Uber Geek
+1 received by user: 1366

Lifetime subscriber

#1561372 28-May-2016 19:02

alisam:

I didn't get very far.

Attached a laptop to the Draytek and couldn't get the login page.

Tried 192.168.1.1.

ipconfig said the Gateway was 47.72.179.254 (owned by Vodafone), but again I couldn't get in.

Should I do a Factory reset and start again, because at the moment I cannot get into the Modem.

Are there any advantages of using 192.168.2.1 over 192.168.1.1?

Obviously have to put a static IP on laptop (on same subnet as DrayTek assuming you know what it is) otherwise it will receive the public address.

Spark Max Fibre using Mikrotik CCR1009-8G-1S-1S+, CRS125-24G-1S, Unifi UAP, U6-Pro, UAP-AC-M-Pro, Apple TV 4K (2022), Apple TV 4K (2017), iPad Air 1st gen, iPad Air 4th gen, iPhone 13, SkyNZ3151 (the white box). If it doesn't move then it's data cabled.

michaelmurfy

meow
13580 posts

Uber Geek
+1 received by user: 10912

Moderator

ID Verified

Trusted

Lifetime subscriber

#1561373 28-May-2016 19:04

@alisam the reason I suggested 192.168.2.0/14 for the IP addressing space of the Draytek (you'll need to set this up on the Draytek itself) is because the IP addressing on your ERL is in the 1.0/24 space, and your Draytek is not on your local network.