Toya Service: Using Cisco EPC3825 Modem for Single Subnet IP Address Allocation

Homies,

I have a Cisco EPC3825 Cable Modem provided by my Toya service provider. A coaxial cable enters it. It has Wifi and ethernet sockets. Devices connected to the modem get addresses from DHCP, the IP of the modem itself also changes over time.

Problem:
Although each of the devices at home connects to the Internet, I have problems with communicating them with each other. After days of searching the net and experimenting, I've come to the conclusion that each of my devices gets an address on a different subnet, and apparently this is a hindrance to most of the things I'm trying to achieve. The ability to configure this hardware from Toya is blocked.

Is it possible, however, without buying additional equipment, to make the devices receive addresses from one subnet?

I tried to deal with the problem with the router from my previous apartment - the Linksys wag120n - but to no avail. I read in another thread ( Link ) that this equipment cannot connect more than a single device, but I don't really understand why. I know that there are threads on the forum in which people recommend specific models, but I want to know which parameter is responsible for that?
In response to the cited topic @bogiebog wrote that it must be an "ethernet modem" - then you can find out that something is an "ethernet modem" because usually in product descriptions this phrase is not used?


ADDITIONAL INFORMATION

The only way that the user (at least officially) can interfere with the configuration is to change the channel, signal strength and turn on and off wifi in the client panel on Toya's website.
I found the address of the modem's configuration panel, but the login details are not factory-set and I could not guess.

I try to create a network in which:

- all devices will see NAS (WD MyCloud). The main computer and NAS would be wired to the modem.

- Android devices (and not only), will be able to receive streams (remote control for gaming, among others) from the main PC using applications such as: Moonlight, Remotr, KinoConsole / KinoRemote.

- devices will see each other in network neighborhood. Mainly it is about devices with windows, but also various other OSes. (not necessary, but probably not a problem at this stage?)

You have not provided basic information about addressing on individual devices. What are these IP addresses and are they on the same subnet or not?

I mentioned that it seems to me they are not on the same subnet.
I am away from home now, I will write some examples of addresses in a few hours.

I am waiting for specific information.

In fact, it is unlikely that devices will get addresses from different subnets.
in particular, I admit the possibility that devices connected via wifi have a different subnet than those connected to the router's LAN port, although these are very rare cases.
You can also isolate clients from each other. I have looked at the manual for this device and there is no indication that any of the above cases occurs. By default, devices should receive addresses from the 192.168.0.0/24 network

Enter the sourced addresses and masks.

czuker wrote:

You can also isolate clients from each other. I have looked at the manual for this device and there is no indication that any of the above cases occurs. By default, devices should receive addresses from the 192.168.0.0/24 network

As far as I know, Toya has its own configuration for this device and it is not the default. Even the management of basic router configurations is only available through the provider's website.

czuker wrote:

Enter the sourced addresses and masks.

Then we will discuss this topic further.

Main PC, Win7 (via cable):

Laptop, WinXP (wifi)

Smartphone, Android (wifi)

SBC connected to TV, Android - RemixOS (wifi)

WD MyCloud network drive (via cable):
I do not know how to check, it is not visible in the network neighborhood. I can access the web page listing my files but not the device settings - although it seems possible. I would have to take a moment to read about it.
When I conduct a LAN scan from my smartphone (10.9.76.7), I pop up with 20 addresses that belong rather to other people and none of them from MyCloud.

From what I can see, the operator applied the / 21 mask for your lan which gives your DHCP server 2048 addresses to assign, therefore DHCP assigns addresses from different subnets randomly, with the mask / 21 the devices will be visible in the network without any problems.

If you have a problem with connecting devices, contact the operator and ask him to change the lan subnet mask from 255.255.248.0 (21 bit) to 255.255.255.0 (24 bit) in the device configuration, this will solve the problem definitively.

This is how I look at these screenshots with addresses and one thing comes to my mind (although I do not know this TOYA operator) but it looks as if your router is just a modem connecting you to the operator's network, and all routing, dhcp, nat operations are performed they were on some operator's edge device, I suppose it is the device responsible for the network segment, therefore it has a mask / 21, but I am not able to come up with the idea behind the operator in making such a large bridge and potentially allowing customers to communicate with each other within one network.

The second option that remains is to use the old router, connect it with a DSL socket to the lan port of the toya operator router, set the WAN port in it to get the address from dhcp, and then set your wifi and your lan as you like.

Thanks for the answer,
Actually digesting what you wrote, the request to the operator to change this mask looks most promising, but I assumed a bit that they did not satisfy such cravings. I will definitely try.

waluszek wrote:

From what I can see, the operator applied the / 21 mask for your lan which gives your DHCP server 2048 addresses to assign, therefore DHCP assigns addresses from different subnets randomly, with the mask / 21 the devices will be visible in the network without any problems.

Then why can't they see each other?

I did a little testing and found that however:
- The main PC (desktop PC with W7) is seen with a laptop with XP in the network environment (there is access to XP shares).
- the smartphone sees the host PC's media server (but does not connect to it).

But only so many I was able to find working connections. The most interesting to me is why none of the above-mentioned devices can see the NAS - and in addition to the shares, it also has a media server (everything is turned on - it works when it is connected directly to the PC with a cable). This and efficient streaming are the key issues for me.

Quote:

The second option is to use the old router, connect it with a DSL socket to the lan port of the toya operator router , set the WAN port in it to get the address from dhcp, and then set your wifi and your lan as you like.

I have no talent for networking, so I guess I don't really understand - Connect the cable going from one of these Ethernet ports of the operator's modem to the DSL port on the router? How is that? They come in different sizes, is it possible?

in the way shown in the graphic, I would not connect because we have Ethernet on the one hand and DSL on the other.
The physicality is the same, but the technologies are completely different.
I don't know why you want to combine it but definitely not like that.

As for IP addressing - I have the impression that the operator's device works in bridge mode and all your devices get addressing from the operator. As a result, they are all (simplified) visible to other users of the Toya network.
Can you change the operating mode of the operator device from bridge to router?

czuker wrote:

in the way shown in the graphic, I would not connect because we have Ethernet on the one hand and DSL on the other.
The physicality is the same, but the technologies are completely different.
I don't know why you want to combine it but definitely not like that.

This is the solution proposed by Waluszek (I forgot to mark who he is quoting in this passage). Maybe he didn't check what type of router I have (?). BTW, on the physical side, these ports are different, DSL is smaller.

czuker wrote:

As for IP addressing - I have the impression that the operator's device works in bridge mode and all your devices get addressing from the operator. As a result, they are all (simplified) visible to other users of the Toya network.
Can you change the operating mode of the operator device from bridge to router?

I can't, I only have access to the signal strength, channel and wifi switch (on / off) settings. Devices of other operator's clients are actually visible during the LAN scan. What's funny, when I do such a scan from my smartphone, I do not see my other own devices.

Generally speaking, it doesn't really seem to me that the addresses are actually in the same subnet - except for an XP laptop and a Win7 PC - that's why they saw each other in the network neighborhood. Today I checked it with this tool: http://www.meridianoutpost.com/resources/etools/network/two-ips-on-same-network.php

The operator has 48 hours to respond to my report, so for now I can only wait. If you have any other ideas, I would like to read it.

I do not want to recalculate masks and addresses, so I will not answer if the addresses are from the same subnet. But the devices that share the same Gateway tend to be in the same subnet.
As for the general solution. You can connect a router with a port marked as WAN to the operator's device. The router you have can be connected to the ADSL service in Netia or Orange

Well, the easiest way to find out if the gateway is in the same subnet, the gate must always be in the same subnet as the device. A point for this tip.

I understand that every router with a WAN port is of the right type, therefore.
I have already chosen ...
It would be enough, however, if this Toy device gave me addresses from one network and completely without additional hardware. It's just a matter of configuration.
I will wait until I get a response directly from the operator, or maybe someone also has Toye or knowledge about it.

Having your own device has the advantage that you have full control over its configuration and is the first level of protection against other Toya client users.

I'm sorry, in fact, the router you wrote about has a DSL connector and you need an xDSL router,

Contact TOYA, for the first time I see such a solution that the operator of your router at home sets the BRIDGE mode and gives such addressing, besides, such a setting may be on the device which broadcasts addresses that the network clients should not see each other. Therefore, you cannot see your devices on the network.

The solution with the router in BRIDGE is used to forward the Public IP to the client router, not for such actions.

waluszek wrote:

DSL and you need an xDSL router

Each xDSL device is a DSL device. xDSL is a collection of different DSL varieties: ADSL, HDSL, RADSL, SDSL, VDSL etc.
DSL (Digital Subscriber Loop) is a technology for transmitting data over a subscriber (telephone) line.

I meant a general description All routers I saw with xDSL in the description had a wan input in the form of RJ45. in each search engine after entering xDSL, routers pop up, such as the author of the thread is needed.

Just because sellers write so massively doesn't mean it's correct. They confuse ethernet, where RJ45 is used, with real xDSL. See what it's like on the router manufacturer's website and they probably know what they're making:
https://www.asus.com/pl/Networking/xDSL-Modem-Routers-products/

Hey, I understand you want to be correct and teach others this, but since everyone is used to xDSL specifying a router with an RJ45 WAN socket, it might be better not to cause confusion. It won't change anything and creates an unnecessary mess.

waluszek wrote:

since everyone got used to it

Once upon a time, everyone got used to the fact that the earth is flat. Who bothered this?

@Turusan
Buy your own router with a WAN port - enter the address of the router in Cisco in the DMZ, you will have what you want and decide everything for yourself.

I got a response from the service provider that this equipment is not intended for creating a home network and a suggestion to invest in a router. So it is confirmed - it looks like this addressing is normal and they do not change this configuration. It needs to be treated more like a modem. So I close the topic.