• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

subnet question

T

thenewnoise

Senior member
hi, i have have dsl modem that has the address of 192.168.1.1 and its on subnet 255.255.255.252. i have a router connected to the modem and it uses nats to connect 4 computers to the dsl. what i need to do is access the modem utility page from one of the computers behind the router. those computers are on the subnet of 255.255.255.0. is it possible for me to access the modem from these computers and if so how?😕
 
Just aim at the right address, the system will handle the subnet resolution.

Good Luck

Scott
 
i tried that before abd all i get is the ie "can not find server" error. but if i plug a computer right into the modem it works fine. any ideas?
 
Are there any other addresses associated with the DSL modem?

What manufacturer / model number is it?

What you using to access it?

Gotta know


Scott


 
to gain access you just go to http://198.162.1.1

its arsecom netdsl 800

the modem gets the ip address from msn and then asigns the thing connected to it (my router) the address 192.168.1.2 then the router uses nats to hook the other 4 computers up
 
What range of addresses is your router handing out (not the DSL modem)?

If the router is also handing out 192.168 addresses, it may be intercepting the packets (or actually, not routing them because it looks to the router like you're on the same network...routers don't route to the "same" network).

If that's the case, change your DHCP addresses coming from the router to 192.168.100.x (or anything that's not 192.168.1.x).

Good Luck

Scott
 
.. ok why are you using the subnet mask 255.255.255.252 on a 5 node network ..? and maybe im missing something, but why complicate matters by putting them on different networks .. they should all be able to coexist on one network .. .. and anyway even if they had to be on different networks, there is no reason to use different subnet masks .. the mask is just a mask .. if u have 15 networks, you could still use the subnet mask 255.255.255.0 and then use network id's 192.168.0-192.168.14 ..just complicates things ..

and are you trying to make them "different networks" by using different masks? but say another node has 192.168.1.1 .. that would produce weird problems as well .. i dunno maybe im not seeing ur net correctly , but thats what i think 'is happening, definitely no reason to use a diff subnet mask .. . .. the subnet (network id) is actaully 192.168.1 (mask is 255.255.255.0 ..
-neural
 
no no, msn doesnt want you networking the computers so they sent this modem thats on the subnet of 255.255.255.252 so that you cant put more than one computer on the network(the modem gets 192.168.1.1 and the thing connected to it gets 192.168.1.2). so i have to use nats with the router. thats why they are on different subnets
 
whoa...

okay... MSN uses an internal class-c setup? that's werid... not that I have anything to scale this against.

so your modem is 192.168.1.1? which is weird... because I thought a modem was a layer 2 device... not a layer 3 device, so how did it get an IP address?

and then your DSL router is 192.168.1.2?

okay... correct me if i'm wrong...

but a subnet of 255.255.255.252 leaves 2 useable host addresses per subnet right... but if you can't use the first and last address... and there are only two addresses... can this be a valid class c subnet?

bah... i'm confused.... just listen to ScottMac... he knows what' he's talking about. it would make sense to reassign the internal network address used by the router.
 


<< .. the mask is just a mask .. if u have 15 networks, you could still use the subnet mask 255.255.255.0 and then use network id's 192.168.0-192.168.14 ..just complicates things .. >>



Umm, no. If you use a subnet mask of 255.255.255.0 then the network ID is xxx.xxx.xxx.0 (only one network), essentially making it a classfull address again (Class C). The subnet mask is created by how many bits are borrowed from the host field. For ex. On a class C you borrow 3 bits (11100000; 1=being borrowed for subnet, 0=hosts). Your SNM is gonna be 255.255.255.224 with .32, .64, .96, .128, .160, and .192 as the SN IDs. 6 Subnets with 32 hosts per subnet.

My bad. Didn't see the last octect up above was missing. I see what you mean. 192.168.0.xxx - 192.168.14.xxx all using 255.255.255.0 is in total 15 networks.
 
OK. This is the setup, as I interpret it:

The DSL provider is using a .252 mask: two usable addresses, my side and your side. The provider side is 192.168.1.1, the address available to the user is 192.168.1.2. THe "DSL modem" is acting as a bridge (probably a 1493 ATM kinda bridge), and the default gateway the the user is s'posed to aim at is 192.168.1.1 (255.255.255.252).

The user has connected the output from the "modem" into the WAN port of his router (one input, four switched Ethernet ports out). The WAN port of the router is set for 192.168.1.1 (255.255.255.252).

The router is providing DCHP addressing for the (1-4) connected computers. By default, at least some of the routers are putting out 192.168.1.XX addresses to the LAN side, probably starting at ".1" The user has not yet told us what the inside addresses are that the router is putting out. IF they are 192.168.1.XX addresses, then that would be the problem...He would be routing from a 192.168.1.XX/24 network to a 192.168.1.0 /30 network...possibly with two of the devices using 192.168.1.1 or .1.2 (or actually NOT routing, because the router is seeing the "same" network on both interfaces...or at the very least has initiated some "WTF?" process and refuses to cooperate).

If he sets the router up to dispense just about any other address (like 192.168.100.xx) or anything that isn't 192.168.1.something, I think it'll fly.

As it is now, I think the inside "default Gateway" address is 192.168.1.1, the WAN interface is 192.168.1.2 with a default gateway of 192.168.1.1 (an address that exists on both sides of the WAN interface)...since the LAN 192.168.1.1 is directly attached, that's where the router is sending the packets. The packet gets to the LAN interface, is routed to the WAN interface, then gets routed back to the LAN interface instead of down the line to the provider.

That's my guess, I'm sticking with it 'till I hear some more specific information.

FWIW

Scott
 
Sounds kosher to me. You can't have the WAN side and the LAN side of the router on the same network. The router doesn't know which way to send the packets. Also worth testing is configuring the gateway for the clients as 192.168.1.1 and then again as 192.168.1.2. See if that helps.

 
ScottMac you got a few things mixed up

lets started like this

DSL Mode - 192.168.1.1, and the Public ip address
Router - 192.168.1.2

both of those on the subnet 255.255.255.252

now

the router is 192.168.1.2
the 4 computers are 192.168.1.100-104
the default gateway for those computers is 192.168.1.2 (the router)

they are on the subnet of 255.255.255.0

here is a screenshot of the router setup screen incase i messed something up or forgot something




 
I'm still pretty sure that if you change the INSIDE addresses to something other than 192.168.1.xx that it'll work.

Try .2.xx or higher.

Good Luck

Scott
 
Well if your router has an interface on 192.168.1.0/30 and your PC's are on 192.168.1.0/24 the router won't know how to reply to them if they ping him. He has no router to the /24 network and this will drop the packet.

Like Scottmac says you need to change the inside address of the router (the one on the interface attached to the PC's) to be something other than 192.168.1.x and renumber the PC's to be on that subnet.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top