I tried the dry-run and this was the result.  Looks like it failed, but I am 
not sure how to fix.

[root@stmartin pf]# curl 
https://github.com/inverse-inc/packetfence/compare/feature/DELL_lldp.diff | 
patch -p1 --dry-run
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3198    0  3198    0     0   6072      0 --:--:-- --:--:-- --:--:--  6068
checking file docs/PacketFence_Network_Devices_Configuration_Guide.asciidoc
Hunk #1 FAILED at 2397.
1 out of 1 hunk FAILED
checking file lib/pf/Switch/Dell/N1500.pm

Peter Truax
Network Administrator
(360) 688-2240
Saint Martin's University
5000 Abbey Way E
Lacey, WA 98503

[cid:[email protected]]

From: Durand fabrice via PacketFence-users 
<[email protected]>
Sent: Wednesday, February 27, 2019 5:29 PM
To: [email protected]
Cc: Durand fabrice <[email protected]>
Subject: [External] Re: [PacketFence-users] VOIP Troubles with Dell Switches

CAUTION: This email is from an outside sender. Do not click on links or open 
attachments unless you recognize the sender and know the content is safe.




Hello Peter,

you can try that 
https://github.com/inverse-inc/packetfence/compare/feature/DELL_lldp.diff

It add a better voip support for the Dell switches.

cd /usr/local/pf

curl https://github.com/inverse-inc/packetfence/compare/feature/DELL_lldp.diff 
| patch -p1 --dry-run

if no errors to apply the patch then:

curl https://github.com/inverse-inc/packetfence/compare/feature/DELL_lldp.diff 
| patch -p1

and restart packetfence.

Regards

Fabrice


Le 19-02-27 à 18 h 19, Truax, Peter via PacketFence-users a écrit :
Hello everyone,

We are having troubles getting Polycom VVX voip phones to work with Dell 
N-Series switches.

Below is an excerpt from the radius.log file.

Feb 27 14:29:41 stmartin auth[2673]: [mac:64:16:7f:88:58:ef] Accepted user:  
and returned VLAN
Feb 27 14:29:41 stmartin auth[2673]: (41024) Login OK: [64167F8858EF] (from 
client 10.10.0.17 port 1 cli 64:16:7f:88:58:ef)

Basically, what we are seeing is that when a phone is connected, it received a 
default vlan ip address. The log above shows that no voice vlan was sent by pf 
to the switch.

We have the Role by VLAN ID set to vlan 80 for voice. (which is our voice vlan).

The switch is configured with the proper voice vlan, and works when configured 
manually. When we try to get pf to control the port, then it fails.

We have gotten Cisco 2960X switches to work successfully with these phones and 
PacketFence.

Just to give more info, below is an excerpt from Packetfence.log:

Feb 27 14:29:41 stmartin packetfence_httpd.aaa: httpd.aaa(1775) INFO: 
[mac:64:16:7f:88:58:ef] handling radius autz request: from switch_ip => 
(10.10.0.17), connection_type => WIRED_MAC_AUTH,switch_mac => 
(f4:8e:38:0a:54:63), mac => [64:16:7f:88:58:ef], port => 1, username => 
"64167F8858EF" (pf::radius::authorize)
Feb 27 14:29:41 stmartin packetfence_httpd.aaa: httpd.aaa(1775) INFO: 
[mac:64:16:7f:88:58:ef] Instantiate profile default 
(pf::Connection::ProfileFactory::_from_profile)
Feb 27 14:29:41 stmartin packetfence_httpd.aaa: httpd.aaa(1775) INFO: 
[mac:64:16:7f:88:58:ef] violation 1300003 force-closed for 64:16:7f:88:58:ef 
(pf::violation::violation_force_close)
Feb 27 14:29:41 stmartin packetfence_httpd.aaa: httpd.aaa(1775) INFO: 
[mac:64:16:7f:88:58:ef] Instantiate profile default 
(pf::Connection::ProfileFactory::_from_profile)

Any ideas on what I can do to get this working?

Regards,

Peter Truax
Network Administrator
Saint Martin's University
5000 Abbey Way E
Lacey, WA 98503

[cid:[email protected]]





_______________________________________________

PacketFence-users mailing list

[email protected]<mailto:[email protected]>

https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to