How to connect a special device in a network
up vote
4
down vote
favorite
I have a question which is puzzling me.
I have a couple of custom electronic devices (are identical, one is a master and the other is a slave) which implement only up to level 2 of the ISO/OSI layer, so they have only a (different) MAC address
If I connect one of them to my PC with a straight connection (e.g. the ethernet cable from the PC's ethernet card to the ethernet port of the device) , then I can connect and exchange data.
Now I have a more complex situation to handle.
The two devices are installed on a pole along with an IP camera. These 3 elements are named “sensor group”. I can have up to 7 sensor groups installed in a given area, for a specific task.
I need to connect those 7 sensor groups to a single local PC, in a room, with a specific SW (developed by myself) running.
I was thinking to use a network switch for each sensor group with a cabling (maybe fiber) to a network switch to which the PC is connected to. So, each sensor group, thanks to its local switch can communicate to the PC.
Now my point is: which kind of equipment I need to use (layer 2 switch, layer 3 switch, hub, router ...) in order to allow both a connection between the SW on the PC and each specific custom device in a sensor group, and to receive the RTSP stream from the camera, too?
I am really struggling because it is the first time for me to face this kind of need with these “only-MAC” devices.
Thanks!
LuKa
mac-address
New contributor
|
show 1 more comment
up vote
4
down vote
favorite
I have a question which is puzzling me.
I have a couple of custom electronic devices (are identical, one is a master and the other is a slave) which implement only up to level 2 of the ISO/OSI layer, so they have only a (different) MAC address
If I connect one of them to my PC with a straight connection (e.g. the ethernet cable from the PC's ethernet card to the ethernet port of the device) , then I can connect and exchange data.
Now I have a more complex situation to handle.
The two devices are installed on a pole along with an IP camera. These 3 elements are named “sensor group”. I can have up to 7 sensor groups installed in a given area, for a specific task.
I need to connect those 7 sensor groups to a single local PC, in a room, with a specific SW (developed by myself) running.
I was thinking to use a network switch for each sensor group with a cabling (maybe fiber) to a network switch to which the PC is connected to. So, each sensor group, thanks to its local switch can communicate to the PC.
Now my point is: which kind of equipment I need to use (layer 2 switch, layer 3 switch, hub, router ...) in order to allow both a connection between the SW on the PC and each specific custom device in a sensor group, and to receive the RTSP stream from the camera, too?
I am really struggling because it is the first time for me to face this kind of need with these “only-MAC” devices.
Thanks!
LuKa
mac-address
New contributor
Hello Lukariello and welcome to NE. What kind of things are the special devices?
– jonathanjo
2 hours ago
I'm sure you meant RTSP (real time streaming protocol, used by some cameras) not RSTP (rapid spanning tree protocol, used on switches), so I edited as such.
– jonathanjo
2 hours ago
Hi jonathanjo, the special devices are custom made electronics equipments which are able to perform real time environment analysis like specific gas presence in the air. They are “safe” and so communicate via rs 232. Their eth connection is for maintenance and set up purposes and for real time data transmission to perform specific debug.
– Lukariello
2 hours ago
I understand the need for basic and trusted mechanisms for things like safety monitoring. Nonetheless, you might consider getting them adapted to work with IP, which then frees you up on the networking side. I do a lot of telemetry work and my clients have found a lot of benefit from this, even putting serial converters in for RS-485 and RS-232 devices. It certainly doesn't suit everything -- and often introduces security concerns -- but I'd definitely recommend considering it.
– jonathanjo
2 hours ago
The point is that the use of serial comm is due to safety aspect strictly regulated by standards which do not allow IP communications. Anyway, my concern is not about serial communications but about eth port connections. That latter kind of connection is only for debug/setup purposes and the point is being able to connect from the monitoring pc to each of the custom device without going near the pole where each device is mounted.
– Lukariello
1 hour ago
|
show 1 more comment
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I have a question which is puzzling me.
I have a couple of custom electronic devices (are identical, one is a master and the other is a slave) which implement only up to level 2 of the ISO/OSI layer, so they have only a (different) MAC address
If I connect one of them to my PC with a straight connection (e.g. the ethernet cable from the PC's ethernet card to the ethernet port of the device) , then I can connect and exchange data.
Now I have a more complex situation to handle.
The two devices are installed on a pole along with an IP camera. These 3 elements are named “sensor group”. I can have up to 7 sensor groups installed in a given area, for a specific task.
I need to connect those 7 sensor groups to a single local PC, in a room, with a specific SW (developed by myself) running.
I was thinking to use a network switch for each sensor group with a cabling (maybe fiber) to a network switch to which the PC is connected to. So, each sensor group, thanks to its local switch can communicate to the PC.
Now my point is: which kind of equipment I need to use (layer 2 switch, layer 3 switch, hub, router ...) in order to allow both a connection between the SW on the PC and each specific custom device in a sensor group, and to receive the RTSP stream from the camera, too?
I am really struggling because it is the first time for me to face this kind of need with these “only-MAC” devices.
Thanks!
LuKa
mac-address
New contributor
I have a question which is puzzling me.
I have a couple of custom electronic devices (are identical, one is a master and the other is a slave) which implement only up to level 2 of the ISO/OSI layer, so they have only a (different) MAC address
If I connect one of them to my PC with a straight connection (e.g. the ethernet cable from the PC's ethernet card to the ethernet port of the device) , then I can connect and exchange data.
Now I have a more complex situation to handle.
The two devices are installed on a pole along with an IP camera. These 3 elements are named “sensor group”. I can have up to 7 sensor groups installed in a given area, for a specific task.
I need to connect those 7 sensor groups to a single local PC, in a room, with a specific SW (developed by myself) running.
I was thinking to use a network switch for each sensor group with a cabling (maybe fiber) to a network switch to which the PC is connected to. So, each sensor group, thanks to its local switch can communicate to the PC.
Now my point is: which kind of equipment I need to use (layer 2 switch, layer 3 switch, hub, router ...) in order to allow both a connection between the SW on the PC and each specific custom device in a sensor group, and to receive the RTSP stream from the camera, too?
I am really struggling because it is the first time for me to face this kind of need with these “only-MAC” devices.
Thanks!
LuKa
mac-address
mac-address
New contributor
New contributor
edited 2 hours ago
jonathanjo
10k1632
10k1632
New contributor
asked 2 hours ago
Lukariello
212
212
New contributor
New contributor
Hello Lukariello and welcome to NE. What kind of things are the special devices?
– jonathanjo
2 hours ago
I'm sure you meant RTSP (real time streaming protocol, used by some cameras) not RSTP (rapid spanning tree protocol, used on switches), so I edited as such.
– jonathanjo
2 hours ago
Hi jonathanjo, the special devices are custom made electronics equipments which are able to perform real time environment analysis like specific gas presence in the air. They are “safe” and so communicate via rs 232. Their eth connection is for maintenance and set up purposes and for real time data transmission to perform specific debug.
– Lukariello
2 hours ago
I understand the need for basic and trusted mechanisms for things like safety monitoring. Nonetheless, you might consider getting them adapted to work with IP, which then frees you up on the networking side. I do a lot of telemetry work and my clients have found a lot of benefit from this, even putting serial converters in for RS-485 and RS-232 devices. It certainly doesn't suit everything -- and often introduces security concerns -- but I'd definitely recommend considering it.
– jonathanjo
2 hours ago
The point is that the use of serial comm is due to safety aspect strictly regulated by standards which do not allow IP communications. Anyway, my concern is not about serial communications but about eth port connections. That latter kind of connection is only for debug/setup purposes and the point is being able to connect from the monitoring pc to each of the custom device without going near the pole where each device is mounted.
– Lukariello
1 hour ago
|
show 1 more comment
Hello Lukariello and welcome to NE. What kind of things are the special devices?
– jonathanjo
2 hours ago
I'm sure you meant RTSP (real time streaming protocol, used by some cameras) not RSTP (rapid spanning tree protocol, used on switches), so I edited as such.
– jonathanjo
2 hours ago
Hi jonathanjo, the special devices are custom made electronics equipments which are able to perform real time environment analysis like specific gas presence in the air. They are “safe” and so communicate via rs 232. Their eth connection is for maintenance and set up purposes and for real time data transmission to perform specific debug.
– Lukariello
2 hours ago
I understand the need for basic and trusted mechanisms for things like safety monitoring. Nonetheless, you might consider getting them adapted to work with IP, which then frees you up on the networking side. I do a lot of telemetry work and my clients have found a lot of benefit from this, even putting serial converters in for RS-485 and RS-232 devices. It certainly doesn't suit everything -- and often introduces security concerns -- but I'd definitely recommend considering it.
– jonathanjo
2 hours ago
The point is that the use of serial comm is due to safety aspect strictly regulated by standards which do not allow IP communications. Anyway, my concern is not about serial communications but about eth port connections. That latter kind of connection is only for debug/setup purposes and the point is being able to connect from the monitoring pc to each of the custom device without going near the pole where each device is mounted.
– Lukariello
1 hour ago
Hello Lukariello and welcome to NE. What kind of things are the special devices?
– jonathanjo
2 hours ago
Hello Lukariello and welcome to NE. What kind of things are the special devices?
– jonathanjo
2 hours ago
I'm sure you meant RTSP (real time streaming protocol, used by some cameras) not RSTP (rapid spanning tree protocol, used on switches), so I edited as such.
– jonathanjo
2 hours ago
I'm sure you meant RTSP (real time streaming protocol, used by some cameras) not RSTP (rapid spanning tree protocol, used on switches), so I edited as such.
– jonathanjo
2 hours ago
Hi jonathanjo, the special devices are custom made electronics equipments which are able to perform real time environment analysis like specific gas presence in the air. They are “safe” and so communicate via rs 232. Their eth connection is for maintenance and set up purposes and for real time data transmission to perform specific debug.
– Lukariello
2 hours ago
Hi jonathanjo, the special devices are custom made electronics equipments which are able to perform real time environment analysis like specific gas presence in the air. They are “safe” and so communicate via rs 232. Their eth connection is for maintenance and set up purposes and for real time data transmission to perform specific debug.
– Lukariello
2 hours ago
I understand the need for basic and trusted mechanisms for things like safety monitoring. Nonetheless, you might consider getting them adapted to work with IP, which then frees you up on the networking side. I do a lot of telemetry work and my clients have found a lot of benefit from this, even putting serial converters in for RS-485 and RS-232 devices. It certainly doesn't suit everything -- and often introduces security concerns -- but I'd definitely recommend considering it.
– jonathanjo
2 hours ago
I understand the need for basic and trusted mechanisms for things like safety monitoring. Nonetheless, you might consider getting them adapted to work with IP, which then frees you up on the networking side. I do a lot of telemetry work and my clients have found a lot of benefit from this, even putting serial converters in for RS-485 and RS-232 devices. It certainly doesn't suit everything -- and often introduces security concerns -- but I'd definitely recommend considering it.
– jonathanjo
2 hours ago
The point is that the use of serial comm is due to safety aspect strictly regulated by standards which do not allow IP communications. Anyway, my concern is not about serial communications but about eth port connections. That latter kind of connection is only for debug/setup purposes and the point is being able to connect from the monitoring pc to each of the custom device without going near the pole where each device is mounted.
– Lukariello
1 hour ago
The point is that the use of serial comm is due to safety aspect strictly regulated by standards which do not allow IP communications. Anyway, my concern is not about serial communications but about eth port connections. That latter kind of connection is only for debug/setup purposes and the point is being able to connect from the monitoring pc to each of the custom device without going near the pole where each device is mounted.
– Lukariello
1 hour ago
|
show 1 more comment
2 Answers
2
active
oldest
votes
up vote
4
down vote
If your sensors are layer-2 ethernet only, you must have just switches (and no routers) between two communicating devices. So if your devices communicate with the PC, that means they must all plug into the same switch, or a network of switches. One obvious setup is exactly what you describe: have a small switch per sensor group, and link the seven sensor-group switches to a main switch next to the PC, by fibre or cable depending on distance and speed. But it all depends on the physical layout.
If you additionally have layer-3 cameras, they will work fine because internet protocol will sit perfectly well on top of ethernet.
You only need routers if you have different layer-3 networks which need to communicate. A so-called "layer 3 switch" is actually a switch with a router built in to the same box: you don't need one.
add a comment |
up vote
2
down vote
If the devices only communicate at layer-2, then you use a layer-2 switch. A hub (layer-1 device) should work, too, but they are practically extinct, and they have the problem of collisions. Routers work at layer-3, and they strip off the layer-2 frame, so that will not work for layer-2 communications.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "496"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Lukariello is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f55487%2fhow-to-connect-a-special-device-in-a-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
If your sensors are layer-2 ethernet only, you must have just switches (and no routers) between two communicating devices. So if your devices communicate with the PC, that means they must all plug into the same switch, or a network of switches. One obvious setup is exactly what you describe: have a small switch per sensor group, and link the seven sensor-group switches to a main switch next to the PC, by fibre or cable depending on distance and speed. But it all depends on the physical layout.
If you additionally have layer-3 cameras, they will work fine because internet protocol will sit perfectly well on top of ethernet.
You only need routers if you have different layer-3 networks which need to communicate. A so-called "layer 3 switch" is actually a switch with a router built in to the same box: you don't need one.
add a comment |
up vote
4
down vote
If your sensors are layer-2 ethernet only, you must have just switches (and no routers) between two communicating devices. So if your devices communicate with the PC, that means they must all plug into the same switch, or a network of switches. One obvious setup is exactly what you describe: have a small switch per sensor group, and link the seven sensor-group switches to a main switch next to the PC, by fibre or cable depending on distance and speed. But it all depends on the physical layout.
If you additionally have layer-3 cameras, they will work fine because internet protocol will sit perfectly well on top of ethernet.
You only need routers if you have different layer-3 networks which need to communicate. A so-called "layer 3 switch" is actually a switch with a router built in to the same box: you don't need one.
add a comment |
up vote
4
down vote
up vote
4
down vote
If your sensors are layer-2 ethernet only, you must have just switches (and no routers) between two communicating devices. So if your devices communicate with the PC, that means they must all plug into the same switch, or a network of switches. One obvious setup is exactly what you describe: have a small switch per sensor group, and link the seven sensor-group switches to a main switch next to the PC, by fibre or cable depending on distance and speed. But it all depends on the physical layout.
If you additionally have layer-3 cameras, they will work fine because internet protocol will sit perfectly well on top of ethernet.
You only need routers if you have different layer-3 networks which need to communicate. A so-called "layer 3 switch" is actually a switch with a router built in to the same box: you don't need one.
If your sensors are layer-2 ethernet only, you must have just switches (and no routers) between two communicating devices. So if your devices communicate with the PC, that means they must all plug into the same switch, or a network of switches. One obvious setup is exactly what you describe: have a small switch per sensor group, and link the seven sensor-group switches to a main switch next to the PC, by fibre or cable depending on distance and speed. But it all depends on the physical layout.
If you additionally have layer-3 cameras, they will work fine because internet protocol will sit perfectly well on top of ethernet.
You only need routers if you have different layer-3 networks which need to communicate. A so-called "layer 3 switch" is actually a switch with a router built in to the same box: you don't need one.
edited 2 hours ago
answered 2 hours ago
jonathanjo
10k1632
10k1632
add a comment |
add a comment |
up vote
2
down vote
If the devices only communicate at layer-2, then you use a layer-2 switch. A hub (layer-1 device) should work, too, but they are practically extinct, and they have the problem of collisions. Routers work at layer-3, and they strip off the layer-2 frame, so that will not work for layer-2 communications.
add a comment |
up vote
2
down vote
If the devices only communicate at layer-2, then you use a layer-2 switch. A hub (layer-1 device) should work, too, but they are practically extinct, and they have the problem of collisions. Routers work at layer-3, and they strip off the layer-2 frame, so that will not work for layer-2 communications.
add a comment |
up vote
2
down vote
up vote
2
down vote
If the devices only communicate at layer-2, then you use a layer-2 switch. A hub (layer-1 device) should work, too, but they are practically extinct, and they have the problem of collisions. Routers work at layer-3, and they strip off the layer-2 frame, so that will not work for layer-2 communications.
If the devices only communicate at layer-2, then you use a layer-2 switch. A hub (layer-1 device) should work, too, but they are practically extinct, and they have the problem of collisions. Routers work at layer-3, and they strip off the layer-2 frame, so that will not work for layer-2 communications.
edited 2 hours ago
answered 2 hours ago
Ron Maupin♦
61.3k1161110
61.3k1161110
add a comment |
add a comment |
Lukariello is a new contributor. Be nice, and check out our Code of Conduct.
Lukariello is a new contributor. Be nice, and check out our Code of Conduct.
Lukariello is a new contributor. Be nice, and check out our Code of Conduct.
Lukariello is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Network Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f55487%2fhow-to-connect-a-special-device-in-a-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hello Lukariello and welcome to NE. What kind of things are the special devices?
– jonathanjo
2 hours ago
I'm sure you meant RTSP (real time streaming protocol, used by some cameras) not RSTP (rapid spanning tree protocol, used on switches), so I edited as such.
– jonathanjo
2 hours ago
Hi jonathanjo, the special devices are custom made electronics equipments which are able to perform real time environment analysis like specific gas presence in the air. They are “safe” and so communicate via rs 232. Their eth connection is for maintenance and set up purposes and for real time data transmission to perform specific debug.
– Lukariello
2 hours ago
I understand the need for basic and trusted mechanisms for things like safety monitoring. Nonetheless, you might consider getting them adapted to work with IP, which then frees you up on the networking side. I do a lot of telemetry work and my clients have found a lot of benefit from this, even putting serial converters in for RS-485 and RS-232 devices. It certainly doesn't suit everything -- and often introduces security concerns -- but I'd definitely recommend considering it.
– jonathanjo
2 hours ago
The point is that the use of serial comm is due to safety aspect strictly regulated by standards which do not allow IP communications. Anyway, my concern is not about serial communications but about eth port connections. That latter kind of connection is only for debug/setup purposes and the point is being able to connect from the monitoring pc to each of the custom device without going near the pole where each device is mounted.
– Lukariello
1 hour ago