On Wed, Mar 25, 2015 at 11:07 PM, David Lang <[email protected]> wrote: > On Wed, 25 Mar 2015, Milan P. Stanic wrote: > > On Wed, 2015-03-25 at 13:51, David Lang wrote: >> >>> On Wed, 25 Mar 2015, Milan P. Stanic wrote: >>> >>>> On Wed, 2015-03-25 at 20:21, Luca Bertoncello wrote: >>>> >>>>> "Karl O. Pinc" <[email protected]> schrieb: >>>>> >>>>>> It seems I mis-understood. You seem to be looking for >>>>>> the MAC addresses of the devices into which the OpenWRT >>>>>> device is plugged. >>>>>> >>>>> Well, I try again to explain... >>>>> I need to know the MAC-Address of the device connected to the ports of >>>>> the >>>>> OpenWRT-Switch and their port. >>>>> >>>> >>>> If you have ip compiled with neigh (neighbour) support compiled you can >>>> see mac addresses of devices connected to interfaces. >>>> >>>> Try something like this: ip neigh show dev eth0.1@eth0 >>>> >>>> Of course, I'm not sure if I understand your question, sorry. >>>> >>> >>> That will show you information about interfaces directly on the kernel, >>> but >>> will it show you information about things connecting to the switch? And >>> will >>> it show you what port on the switch they are connected to? or will it >>> treat >>> everything on the switch as being on one interface. >>> >> >> I think you are right. >> But maybe there is utility (extended swconfig?) which can access the >> switch to show it's data locally if the switch supports this. >> > > That's exactly what is being asked for. I don't think it's currently > available, but would love to learn that I'm wrong. > > With some of the new equipment that's becoming available that can run > OpenWRT this sort of thing will be more useful. And that's what the other > thread was about.
Well, I refer to robocfg because it's available for my asus wl500g and from this post the author promised it would be possible to read the MAC [address] table of the switch but looking at the those available I don't see such options, only configuration options https://forum.openwrt.org/viewtopic.php?pid=13249 ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Usage: robocfg <op> ... <op> Operations are as below: show switch <enable|disable> port <port_number> [state <enabled|rx_disabled|tx_disabled|disabled>] [stp none|disable|block|listen|learn|forward] [tag <vlan_tag>] [media auto|10HD|10FD|100HD|100FD] [mdi-x auto|on|off] vlan <vlan_number> [ports <ports_list>] vlans <enable|disable|reset> ports_list should be one argument, space separated, quoted if needed, port number could be followed by 't' to leave packet vlan tagged (CPU port default) or by 'u' to untag packet (other ports default) before bringing it to the port, '*' is ignored Samples: 1) ASUS WL-500g Deluxe stock config (eth0 is WAN, eth0.1 is LAN): robocfg switch disable vlans enable reset vlan 0 ports "0 5u" vlan 1 ports "1 2 3 4 5t" port 0 state enabled stp none switch enable 2) WRT54g, WL-500g Deluxe OpenWRT config (vlan0 is LAN, vlan1 is WAN): robocfg switch disable vlans enable reset vlan 0 ports "1 2 3 4 5t" vlan 1 ports "0 5t" port 0 state enabled stp none switch enable ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Alex
_______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
