Hi Luca,

In routed mode the PF is effectively ‘Out-of-band’ so you would not need to add 
local routes on the PF server
for your remote subnets since your PF will be using it’s default gateway to 
reach devices on them.

The IPTABLES should be automatically configured to allow the remote subnets to 
hit the captive portal (on your Registration interface)
on HTTP/HTTPS and also access the MGMT IP address for DNS (which is how the 
captive-portal works).

Remember that PF uses MAC addresses only for identifying NODES and in a routed 
environment your PF server will never see the
MAC address of the user’s device(s) unless you have set up that either:-

Your PF server is the DHCP server for your remote subnets (Can produce a big 
load on the PF server on big networks running over slow
WAN links).

or

Your PF server (MGMT interface) is configured as an IP-HELPER for your remote 
subnets/VLANS – This will NOT work for DHCP-ACK
as the DHCP ACK is a unicast packet and not a broadcast packet (so ip-helper 
will not forward to the PF server).

or (Easiest in my opinion)

You use the UDP-Reflector on your production DHCP server to send all the DHCP 
packets to the PF server (MGMT interface)- This can lead
to a bloated NODES database as you will get a NODE for every device on your 
network that uses the DHCP server. The reflector is quite
easy to set up (now comes with a configuration tool) and gives your PF server 
all the information it needs.

If at least one of these 3 DHCP methods is not in place then the PF server will 
never insert your client devices into its NODE database and
you will get the dreaded ‘Your device is not found in the database…” message 
all the time.

Your PF server can then control the remote switches using dynamic VLAN 
assignment or downloadable ACLs to control
network access depending on the role allocated to the client device.

HTH

Andrew




Andrew Torry

Senior Infrastructure Engineer



Tel: 01326 370760

Email: [email protected]




[cid:[email protected]]
        [Falmouth Exeter Plus]                  
[cid:[email protected]]


        [Twitter] <https://twitter.com/falmouthexeter>          [Facebook] 
<https://www.facebook.com/falmouthexeter>            [Instagram] 
<https://www.instagram.com/falmouthexeterplus/>             [YouTube] 
<https://www.youtube.com/channel/UC5-Jq4vTOhWgYoJJDYrZHWw>

[cid:[email protected]]


[Falmouth University]

Falmouth Exeter Plus is an exempt charity established by Falmouth University 
and the University of Exeter to deliver their shared Higher Education services 
in Cornwall.
From: luca comes [mailto:[email protected]]
Sent: 12 May 2017 14:47
To: [email protected]
Subject: [PacketFence-users] PF 7 routed mode


Hi all,

I'm delivering my new PF to test wired 802.1x on my network. I need to work 
with routed network because PF is in our datacenter and I need to control 
subnets on remote sites. So I've created a local registration/isolation vlan 
directly attached to the server and I configured new vlans on the sites. I then 
configured PF to know that he is working in routed mode adding the necessary on 
conf/networks.conf as said in the admin giude. What I don't understand is if I 
need to add remote networks on the routing table of the server because at the 
moment the registration/isolation interfaces are not reachable and if I take a 
look to the routing table:


[root@pfnac01 ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         172.27.17.231   0.0.0.0         UG    0      0        0 ens160
10.255.10.0     0.0.0.0         255.255.255.0   U     0      0        0 
ens192.2441
10.255.20.0     0.0.0.0         255.255.255.0   U     0      0        0 
ens192.2445
10.255.30.0     0.0.0.0         255.255.255.0   U     0      0        0 
ens192.2446
169.254.0.0     0.0.0.0         255.255.255.252 U     0      0        0 DM-b
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 ens160
169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 ens192
169.254.0.0     0.0.0.0         255.255.0.0     U     1004   0        0 
ens192.2441
169.254.0.0     0.0.0.0         255.255.0.0     U     1005   0        0 
ens192.2445
169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 
ens192.2446
172.27.17.0     0.0.0.0         255.255.255.0   U     0      0        0 ens160



Where 10.255.10.0 is my regular network, 10.255.20.0 is my local registration, 
10.255.30.0 is my local isolation and 172.27.17.0 is the management. I can't 
see my remote networks 10.149.105.0 (remote registration) and 10.148.105.0 
(remote isolation).



Any help is appreciated



Thanks



Luca





Inviato da Outlook<http://aka.ms/weboutlook>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to