Products > Test Equipment

East Tester ET3502 LCR-Bridge

<< < (20/33) > >>

KungFuJosh:
They were making a binary comparison for some reason. 🤷

tatel:

--- Quote from: Martin72 on July 31, 2024, 05:00:44 pm ---How do you get this data out of the hex file?

@Josh:

See pic...
Normally I know that when you activate DHCP, it takes a while and then the network data is “pulled”.
Here the menu remains as it is, regardless of whether it is on or off(DHCP).

--- End quote ---

Can you change IP, netmask and gateway? If so I would try to put a network configuration compatible with your network and deactivate DHCP (edit: on the new device, not in your network).

On a windows PC, ipconfig command, executed on a terminal, shows IP address of the PC, netmask and gateway. Then you could manually set the new device to use any free IP address in the range 192.168.X.1 to 192.168.X.254. Netmask and gateway would be the same you have in your PC.

But, since you use DHCP in your network, you need to make sure there's no chance DHCP server could try and assign to other device the IP address you want for the new device, nor that you assign to the new device an IP already in use.

You should get into your router, which is the gateway. Probably it would be enough to point your web browser to the IP of your gateway, i.e: http(s)://192.168.1.1 or something like that. There you should look at DHCP server configuration carefully.

Usually DHCP servers are configured to never assign IP addresses in some arbitrary address pool of your LAN, i.e. it assigns addresses, say, between 192.168.1.2 and 192.168.1.200. In that case you would manually assign to the new device any (free) address between 192.168.1.201 and 192.168.1.254. That way the new device will not need the DHCP service, it will work, and the remaining devices in the network will continue to do their DHCP business as usual.

On a home LAN, unless you modified something, probability of netmask not being 255.255.255.0 must be about 1 ppb. That netmask is what defines the number of devices your LAN can have. 255.255.255.0 means the three first groups of 8 bits in the IP address are fixed, and that only the last 8 bits are unlocked. So devices in that network can get addresses between X.X.X.0 and X.X.X.255 => 256 devices, each with its own IP address.

But, by definition X.X.X.255 is the broadcast address, used to send messages to all devices in the network, and X.X.X.0 is the network address (of your entire LAN), used for routing between networks. So you can't assign any of these two addresses to a device in your LAN. This leaves you with 254 possible addresses. The router/gateway usually gets the first address, but it could be any of these 254 addresses.

If I'm getting it right, some guy from East Tester told you to use an 192.168.1.0 as *netmask*? It has to be a communication error. Otherwise you'd have to guess he's high on something

(multiple edits for clarity)

tatel:
Netmask in the video is 255.255.178.0 and gateway 192.168.178.1?

Using CIDR notation 255.255.255.0 is /24, meaning 24 bits are locked. You can do your subnetting any way fits you. If you need more than 254 addresses in your LAN, you could use a /16 bit netmask, and have 65534 addresses available. But the mask would be 255.255.0.0

You could use a /17 bit netmask and that would leave half the addresses available on a /16 subnet, but netmask would be 255.255.128.0

A /18 bit netmask would be 255.255.192.0

I'm not aware that netmask could use fractions of a bit. So that netmask is wrong. Perhaps they have a typo and it would be 255.255.128.0 which corresponds to a 17 bit netmask. If you need 32766 IP addresses available in your LAN, that's the way to do it.

Let's see what ipcalc says. We are going to use gateway' address and netmask of 17 bits to see what the resultant networks are:

tatel@gis:~$ ipcalc 192.168.178.1/17
Address:   192.168.178.1        11000000.10101000.1 0110010.00000001
Netmask:   255.255.128.0 = 17   11111111.11111111.1 0000000.00000000
Wildcard:  0.0.127.255          00000000.00000000.0 1111111.11111111
=>
Network:   192.168.128.0/17     11000000.10101000.1 0000000.00000000
HostMin:   192.168.128.1        11000000.10101000.1 0000000.00000001
HostMax:   192.168.255.254      11000000.10101000.1 1111111.11111110
Broadcast: 192.168.255.255      11000000.10101000.1 1111111.11111111
Hosts/Net: 32766                 Class C, Private Internet


So, even if that netmask would be the right one 255.255.128.0, which it isn't, this device will be able to speak only to other devices with IP address between 192.168.128.1 and 192.168.191.254. Quite probably you LAN is out of that range?

I think, you need to change that device network configuration and adapt it to your LAN configuration, as explained in the previous post. It should work with the usual 255.255.255.0 netmask as long as device's IP is in the address range of the LAN configured in your router. If not, get into your router via web browser, take some screenshots of your LAN configuration, and send it to these guys.

Martin72:
Thanks to everyone for the excursion on the subject of networks.
I had already done this "back then" with the ET3502, i.e. manually assigned the addresses.
I haven't tried it with the ET3503 yet, I was too focused on the DHCP thing because East Tester had promised me to test the device before shipping.
Yesterday, after watching the videos again, I suspected that DHCP doesn't work anyway and that you generally have to enter the addresses manually.
I'll try that today and then let you know.

tatel:

--- Quote from: Martin72 on August 04, 2024, 10:33:05 am ---I had already done this "back then" with the ET3502, i.e. manually assigned the addresses.

--- End quote ---

Yeah, I was pretty sure you know how to configure network settings. But seeing people wondering about netmask, etc, I posted it, just in case...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod