Direct link to static IP device
- Thread starter Lisapete
- Start date
Soldato
- Joined
- 20 Oct 2008
- Posts
- 12,082
You don't say what you've tried.
If you're connecting directly to a PC's Ethernet port then you'll need to assign a static IP to it.
If you're connecting directly to a PC's Ethernet port then you'll need to assign a static IP to it.
Permabanned
- Joined
- 9 Aug 2008
- Posts
- 35,711
I have a sheep that wants to be a dog but a fish with eyes is not close enough rabbit.
^^ This is what it sounds like in non technical terms. A little more info required.
^^ This is what it sounds like in non technical terms. A little more info required.
Sorry,
Laptop to the webrelay all with Ethernet. What do I set to be static IP?
This is what I have http://sigma-shop.com/product/111/2-channels-web-relay-board-pcb.html
Default:
IP address: 192.168.1.199
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Username: admin
Password: admin
Soldato
- Joined
- 20 Oct 2008
- Posts
- 12,082
Google 'windows set static IP' for plenty of guides.
Use the same settings as the web relay, but change the IP to 192.168.1.100.
Use the same settings as the web relay, but change the IP to 192.168.1.100.
Associate
- Joined
- 26 Nov 2011
- Posts
- 1,121
- Location
- West London
As I see it you want to run a cat5 cable directly between the webrelay and a laptop. Depending on the laptop and the webrelay, you might need a crossover cable.
Also need to set the laptop with a static IP, and then it should work.
If you have a switch or router setup that you can connect it to, then that will probably make life easier!
Also need to set the laptop with a static IP, and then it should work.
If you have a switch or router setup that you can connect it to, then that will probably make life easier!
This is as good a place as any for a rant – *why* do things come set to a static IP address by default? What planet are these manufacturers living on where DHCP isn't something that goes hand-in-hand with having a network? I mean you could just plug the thing in and then go and find it on your network by looking at the DHCP server leases, or you could faff about setting a static address on your laptop to kick it into DHCP mode and then remember to change it back before plugging it back into the network.
It makes no sense, surely DHCP with an Auto-IP fallback is preferable?
It makes no sense, surely DHCP with an Auto-IP fallback is preferable?
Soldato
- Joined
- 20 Oct 2008
- Posts
- 12,082
A static, and documented, IP address provides a 100% guaranteed way of accessing a device. It assumes some basic networking knowledge, but nothing 2 minutes on Google wouldn't tell you.
If a device is configured for DHCP, and then doesn't find a DHCP server, it will end up with a 169.154.n.n address (fairly useless, but safe). Having a device assign itself a 'valid' IP address just because it couldn't see a DHCP server could cause problems.
In this case 192.168.1.199 seems like a sensible option. 192.168.1.n is probably the most commonly used default subnet. The use of .199 is high enough to avoid most clashes. For a very large majority of small networks it would just work.
If a device is configured for DHCP, and then doesn't find a DHCP server, it will end up with a 169.154.n.n address (fairly useless, but safe). Having a device assign itself a 'valid' IP address just because it couldn't see a DHCP server could cause problems.
In this case 192.168.1.199 seems like a sensible option. 192.168.1.n is probably the most commonly used default subnet. The use of .199 is high enough to avoid most clashes. For a very large majority of small networks it would just work.
Auto IP is what makes the 169.etc addresses.
If you want it even more predictable then DHCP by default, falling back to a static IP rather than APIPA. Best of both worlds. These devices have DHCP clients built in so it's not like it's a feature that would cost money to put in.
It's just irritating having to wire it into a laptop (often after digging out a power injector) when a more sensible out of the box default would make life a lot easier.
If you want it even more predictable then DHCP by default, falling back to a static IP rather than APIPA. Best of both worlds. These devices have DHCP clients built in so it's not like it's a feature that would cost money to put in.
It's just irritating having to wire it into a laptop (often after digging out a power injector) when a more sensible out of the box default would make life a lot easier.
Soldato
- Joined
- 20 Oct 2008
- Posts
- 12,082
I can see where you're coming from, but auto fail back to a 169. address is what's supposed to happen. I don't want network devices to start assigning themselves valid IPs just because they can't see a DHCP server at that moment.
What should be default behaviour be if your connecting multiple versions of the same kit to a network? You wouldn't want them all to come up using the same IP address just because a DHCP server isn't available.
A dedicated button (or a special way of using the usual reset button) to enable/disable DHCP could be useful (although you've then go another way users can poke about and potentially break things).
What should be default behaviour be if your connecting multiple versions of the same kit to a network? You wouldn't want them all to come up using the same IP address just because a DHCP server isn't available.
A dedicated button (or a special way of using the usual reset button) to enable/disable DHCP could be useful (although you've then go another way users can poke about and potentially break things).
Personally I'd like everything to do DHCP out of the box, since a network without DHCP is an exception rather than the rule. If that means the kit comes with a little piece of software to find it on the network for people who can't work DHCP then so be it.
Soldato
- Joined
- 20 Oct 2008
- Posts
- 12,082
I'd agree that in most cases DHCP as the default would make complete sense. It should however still fall back to a 169. address if a DHCP server isn't available.
Many devices do already default to DHCP. For example I can't remember having to deal with a network printer that didn't work in that way.
Many devices do already default to DHCP. For example I can't remember having to deal with a network printer that didn't work in that way.