Walt Baldwin
2016-11-28 04:51:27 UTC
bump...
-------- Forwarded Message --------
Subject: TP-Link Switch Support
Date: Sat, 26 Nov 2016 20:00:43 -0500
From: ***@lydian.org
To: packetfence-***@lists.sourceforge.net
I'm attempting to get a TP-Link 3210 and 5428 working with PacketFence.
I have created my switch object and have successfully configured a
switch in PacketFence.
Nov 26 19:37:37 pfcmd.pl(19617) DEBUG: creating new pf::Switch::TPLink::TL_SG3210 object (pf::SwitchFactory::instantiate)
However, parseTrap() doesn't seem to be getting called. (nor do any of
the new class methods)
I also don't see any output in packetfence.log nor snmptrapd.log.
I have confirmed that the pf box is receiving the traps.
tcpdump -i enp5s0f0 -nnev -s0 udp port 162
tcpdump: listening on enp5s0f0, link-type EN10MB (Ethernet), capture size 65535 byte
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(168) R=5053 .1.3.6.1.2.1.1.3.0=7745881 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.11863.1.1.5.2.3.4.1 .1.3.6.1.4.1.11863.1.1.5.2.3.2.2.1.3.184.39.235.49.69.89.102=8 .1.3.6.1.4.1.11863="The port 8 learns a dynamic address b8:27:eb:31:45:59, vid 102." } }
19:43:47.171926 f4:f2:6d:61:7d:0c > 00:25:90:c7:3c:e4, ethertype IPv4 (0x0800), length 190: (tos 0x0, ttl 64, id 26741, offset 0, flags [none], proto UDP (17), length 176)
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(132) R=5054 .1.3.6.1.2.1.1.3.0=7760595 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.6.3.1.1.5.3 .1.3.6.1.2.1.2.2.1.1.3=3 .1.3.6.1.2.1.2.2.1.7.3=1 .1.3.6.1.2.1.2.2.1.8.3=2 .1.3.6.1.4.1.11863="Port3 linkDown" } }
19:43:51.578752 f4:f2:6d:61:7d:0c > 00:25:90:c7:3c:e4, ethertype IPv4 (0x0800), length 188: (tos 0x0, ttl 64, id 26742, offset 0, flags [none], proto UDP (17), length 174)
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(130) R=5055 .1.3.6.1.2.1.1.3.0=7761036 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.6.3.1.1.5.4 .1.3.6.1.2.1.2.2.1.1.3=3 .1.3.6.1.2.1.2.2.1.7.3=1 .1.3.6.1.2.1.2.2.1.8.3=1 .1.3.6.1.4.1.11863="Port3 linkUp" } }
19:44:07.932334 f4:f2:6d:61:7d:0c > 00:25:90:c7:3c:e4, ethertype IPv4 (0x0800), length 227: (tos 0x0, ttl 64, id 26743, offset 0, flags [none], proto UDP (17), length 213)
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(169) R=5056 .1.3.6.1.2.1.1.3.0=7762671 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.11863.1.1.5.2.3.4.1 .1.3.6.1.4.1.11863.1.1.5.2.3.2.2.1.3.172.207.92.67.199.19.102=8 .1.3.6.1.4.1.11863="The port 8 learns a dynamic address ac:cf:5c:43:c7:13, vid 102." } }
Adding to the mystery, PacketFence is discovering the new macs on the
switch as they are listed in the nodes page on the web interface.
Any push in the right direction would be appreciated.
Thanks
-------- Forwarded Message --------
Subject: TP-Link Switch Support
Date: Sat, 26 Nov 2016 20:00:43 -0500
From: ***@lydian.org
To: packetfence-***@lists.sourceforge.net
I'm attempting to get a TP-Link 3210 and 5428 working with PacketFence.
I have created my switch object and have successfully configured a
switch in PacketFence.
Nov 26 19:37:37 pfcmd.pl(19617) DEBUG: creating new pf::Switch::TPLink::TL_SG3210 object (pf::SwitchFactory::instantiate)
However, parseTrap() doesn't seem to be getting called. (nor do any of
the new class methods)
I also don't see any output in packetfence.log nor snmptrapd.log.
I have confirmed that the pf box is receiving the traps.
tcpdump -i enp5s0f0 -nnev -s0 udp port 162
tcpdump: listening on enp5s0f0, link-type EN10MB (Ethernet), capture size 65535 byte
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(168) R=5053 .1.3.6.1.2.1.1.3.0=7745881 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.11863.1.1.5.2.3.4.1 .1.3.6.1.4.1.11863.1.1.5.2.3.2.2.1.3.184.39.235.49.69.89.102=8 .1.3.6.1.4.1.11863="The port 8 learns a dynamic address b8:27:eb:31:45:59, vid 102." } }
19:43:47.171926 f4:f2:6d:61:7d:0c > 00:25:90:c7:3c:e4, ethertype IPv4 (0x0800), length 190: (tos 0x0, ttl 64, id 26741, offset 0, flags [none], proto UDP (17), length 176)
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(132) R=5054 .1.3.6.1.2.1.1.3.0=7760595 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.6.3.1.1.5.3 .1.3.6.1.2.1.2.2.1.1.3=3 .1.3.6.1.2.1.2.2.1.7.3=1 .1.3.6.1.2.1.2.2.1.8.3=2 .1.3.6.1.4.1.11863="Port3 linkDown" } }
19:43:51.578752 f4:f2:6d:61:7d:0c > 00:25:90:c7:3c:e4, ethertype IPv4 (0x0800), length 188: (tos 0x0, ttl 64, id 26742, offset 0, flags [none], proto UDP (17), length 174)
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(130) R=5055 .1.3.6.1.2.1.1.3.0=7761036 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.6.3.1.1.5.4 .1.3.6.1.2.1.2.2.1.1.3=3 .1.3.6.1.2.1.2.2.1.7.3=1 .1.3.6.1.2.1.2.2.1.8.3=1 .1.3.6.1.4.1.11863="Port3 linkUp" } }
19:44:07.932334 f4:f2:6d:61:7d:0c > 00:25:90:c7:3c:e4, ethertype IPv4 (0x0800), length 227: (tos 0x0, ttl 64, id 26743, offset 0, flags [none], proto UDP (17), length 213)
192.168.14.249.161 > 192.168.14.60.162: { SNMPv2c C=admin { V2Trap(169) R=5056 .1.3.6.1.2.1.1.3.0=7762671 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.11863.1.1.5.2.3.4.1 .1.3.6.1.4.1.11863.1.1.5.2.3.2.2.1.3.172.207.92.67.199.19.102=8 .1.3.6.1.4.1.11863="The port 8 learns a dynamic address ac:cf:5c:43:c7:13, vid 102." } }
Adding to the mystery, PacketFence is discovering the new macs on the
switch as they are listed in the nodes page on the web interface.
Any push in the right direction would be appreciated.
Thanks