Wireless Rear port port #10446
Replies: 4 comments 2 replies
-
Frontport/Rearport are for electrically-connected cable pass-through ports only. Your wireless unit needs two interfaces: a wireless interface, and an ethernet interface. I believe that you can model the cross-connection by setting the "bridge" attribute on each interface to point to the other one, and that traces should work through this - but I haven't tested it. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Yes. Cable "144 and #139 would be Coax RF cable. So in the IDU you have the node processer with modem. |
Beta Was this translation helpful? Give feedback.
-
One downside with this, is that the Bridge part is not visible when looking at the "Connection" |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Today only Interfaces can be of type Wireless. Rear port can not be a wireless port.
But I would like to se that you can have a physicals Front Port connected to a Wireless Rear port.
That way you would be able to trace a dedicated path between two devices that are connected with a wireless link.
[Physical port A (Front port) ]DeviceA[wireless in/out] (Rear port) - - - - - (Rear port)[wireless in/out]DeviceB[Physical port B] (_Front port)
So a front port (physical port) which is connected to the Wireless interface.
I see this as the way to model a device "Wireless Outdoor unit" with 2 modules in it. (radio + antenna).
The module "radio" would have the front port and the other module (antenna) would have the rear port (a wireless interface)
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions