Paxton Entry

[CrootUK]

Anyone using Paxton Entry over WAN? 

Notice its determined to use just IPV6 curious how those with a central server manage this?

Cheers

[cwade]

I’m not sure if they’re doing it via some form of SDN (likely given the CCTV monitoring too), or if it’s via IPv6, but I’ve noticed the Gym Group have rolled out the vandal resistant entry panel’s across the majority of their sites as their emergency call points - with quite slick looking Perspex covers to hide all buttons except the doorbell and make it obvious it’s an emergency help point.

 

I know @Paxton are active in this forum, perhaps they can share some suggestions?

[Paxton]

12 hours ago, CrootUK said:

Anyone using Paxton Entry over WAN? 

Notice its determined to use just IPV6 curious how those with a central server manage this?

Cheers

Hi - yes Entry is capable of WAN connection. 
This is made possible using the Entry App or SIP integration.

Happy to discuss if you want more information.

[CrootUK]

So got it mostly working, seems it just runs independentlyof the server.

Curious how the monitors are only ipv6 though no way to enable ipv4?

Only outstanding issue is the live video  viewing doesnt work, does via a intercom call though.. strange.. based online fourms wondering if its somthing to do with IGMP snooping. Shame it isnt just plug and play in “enteprise” setups too.. wish it had the same config ability as Net2

Edited February 4 by CrootUK

[Paxton]

18 hours ago, CrootUK said:

So got it mostly working, seems it just runs independentlyof the server.

Curious how the monitors are only ipv6 though no way to enable ipv4?

Only outstanding issue is the live video  viewing doesnt work, does via a intercom call though.. strange.. based online fourms wondering if its somthing to do with IGMP snooping. Shame it isnt just plug and play in “enteprise” setups too.. wish it had the same config ability as Net2

Hi - when you say plug and play in enterprise setups can you explain please? Also, please explain live video viewing issue.
The Paxton monitors are fixed at IPV6 for simplicity and plug and play reasons.  If you want to go IPV4 we'd suggest SIP or Entry App.
If you would like a list of ports for your network to ensure the Entry solution can communicate as required - here they are with other helpful docs.

As a general tip ensure you are running the latest config version, currently this is http://www.paxton.info/1907

Note: there is a upgrade path to follow should you be on an earlier version. Please call us on 01273 811011 to discuss.

 

App notes:
https://www.paxton-access.com/wp-content/uploads/2019/03/AN1146.pdf

https://www.paxton-access.com/wp-content/uploads/2019/03/AN1132.pdf

https://www.paxton-access.com/wp-content/uploads/2024/08/APN-1203.pdf

AN1127-US.pdf Entry Planning/Install

AN1130.pdf Entry Config App Note.

Config Firewall Ports.

Information

• The following inbound rules will be added to the Windows Firewall during the installation of the Entry Configuration Utility.

• Any additional firewalls installed will need these rules applied manually. 

Entry Configuration Utility 8700
Protocol type: UDP
Local port: 8700
Remote port: All ports

Entry Configuration Utility 8703
Protocol type: UDP
Local port: 8703
Remote port: All ports

• "All ports" refers to the Windows firewall properties dialog box:  

 

[CrootUK]

ipv6 doesnt make it any simplier? they’d be better off on ipv4. Thats not really the problem though its how you using multicast I am assuming rather than configuring the monitors with IPs of the Intercoms its broadcasting looking for “everything” I am assuming our IGMP snooping is preventing this properly working. Which is a valid feature to have enabled. We’ll be trying a IGMP querier during the upcoming half term break, hopefully that helps.

Firewall is all good - not the problem here.

Firmwares are all uptodate.

[Paxton]

14 hours ago, CrootUK said:

ipv6 doesnt make it any simplier? they’d be better off on ipv4. Thats not really the problem though its how you using multicast I am assuming rather than configuring the monitors with IPs of the Intercoms its broadcasting looking for “everything” I am assuming our IGMP snooping is preventing this properly working. Which is a valid feature to have enabled. We’ll be trying a IGMP querier during the upcoming half term break, hopefully that helps.

Firewall is all good - not the problem here.

Firmwares are all uptodate.

Hi good update thanks. IPv6 is simple for installers and other users who may not be as network savvy. You can install Entry in a siloed sense or on a wider network. How these two differ and why is knowledge and competency dependant...please keep us in the loop as you try things we are happy to jump on a call.

[Frodo_Baggins]

On 03/02/2026 at 18:57, CrootUK said:

Anyone using Paxton Entry over WAN? 

Notice its determined to use just IPV6 curious how those with a central server manage this?

Cheers

Set this up recently when we moved our P10 server internal, only the server needs IPv6 so just had ISP enable IPv6 and then setup DHCPv6 on our Fortigate to route (or at least it works for us)

 

Whilst it was easy to setup IPv6 did cause two of our ISP's to have a mini panic 😂

Edited February 6 by Frodo_Baggins

[CrootUK]

Would just be ideal if you could turn ipv4 on it all for the “advancer” installs though saying that hurts my head. 

[Paxton]

1 minute ago, CrootUK said:

Would just be ideal if you could turn ipv4 on it all for the “advancer” installs though saying that hurts my head. 

You can by adopting SIP or using Entry App instead of Paxton Monitors.

[mavhc]

Using IPv6 means it's zero config, as long as they're on the same vlan should work. From there you can enable IPv4 as well and use SIP with manual config

[k-strider]

mavhc i was about to start planning the migration of all our Paxton from our old primary VLAN 10.x.x.x onto their own VLAN 192.168.x.x and i did wonder how the iPv6 gate intercoms and monitors would play.. currently ip4 trafic is routed between VLANs but i was going to prety much over one holiday whole sale move all Net2 Plus controllers intercoms and a monitros (plus windows server maybe - it is domian joined) into the Paxtons VLAN.

 

[CrootUK]

I ended up having to put the monitor/intercoms all on a singular switch, only way it would work on meraki without disabling IGMP snooping. Is what it is. 

[mavhc]

12 hours ago, k-strider said:

mavhc i was about to start planning the migration of all our Paxton from our old primary VLAN 10.x.x.x onto their own VLAN 192.168.x.x and i did wonder how the iPv6 gate intercoms and monitors would play.. currently ip4 trafic is routed between VLANs but i was going to prety much over one holiday whole sale move all Net2 Plus controllers intercoms and a monitros (plus windows server maybe - it is domian joined) into the Paxtons VLAN.

 

Should be fine, vlans are layer 2 so shouldn't care about ipv4 vs ipv6. I just add another virtual network switch to the VM with the Entry Config program on