03.11.2012 Views

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

Medium Access Control (MAC) and Physical Layer (PHY) - CISE

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4-June-07 P1901_PRO_016_r0<br />

12.2.7.6 Working with RADIUS Authentication<br />

When RADIUS authentication is active, the repeater or HE sends an <strong>Access</strong>-Request message to the RADIUS<br />

server, which checks if the <strong>MAC</strong> address corresponds to one that was accepted <strong>and</strong>, in that case, it responds with an<br />

<strong>Access</strong>-Accept message containing the profile number. Otherwise, the server replies with a RADIUS <strong>Access</strong>-<br />

Reject message <strong>and</strong> the authentication fails. If the authentication fails the slave will not join the BPL network.<br />

Once authentication is achieved, the slave is authorized <strong>and</strong> a QoS <strong>and</strong> VLAN/OVLAN configuration takes place<br />

between the master <strong>and</strong> slave. The master uses the profile number to get these parameters. The slave uses the<br />

parameters inside the downloaded auto-configuration file. The slave node downloads the file during its autoconfiguration<br />

process, after the RADIUS request on the master-side has been successful.<br />

12.2.7.7 Working without RADIUS Authentication<br />

If there is no RADIUS authentication, two ways of operation are possible.<br />

The first one is ‘NO AUTHENTICATION’. The master will configure a default QoS <strong>and</strong> VLAN/OVLAN<br />

configuration (the invited profile) for the slave.<br />

The other one is the use of an ‘AUTHORIZATION LIST’. With ‘ACCESSP_AUTHLIST_x’, up to 128 different<br />

users can be added with their related profiles. The user is searched for in that list, <strong>and</strong> if an entry matches with the<br />

new user, the QoS <strong>and</strong> VLAN/OVLAN configuration related to that entry is used for the new user. Otherwise, the<br />

user is rejected.<br />

12.2.8 DHCP Support<br />

12.2.8.1 DHCP Client<br />

The IEEE P1901 nodes perform a DHCP request with extended custom options. So not only the basic IP<br />

configuration (IP address, netmask <strong>and</strong> gateway) is requested, but the client also requests three custom options in<br />

order to obtain the auto-configuration file:<br />

• tftp-server-name: String with the IP address of the TFTP server.<br />

• extensions-path-name: String with the path <strong>and</strong> file name of the auto-configuration file inside the TFTP<br />

server.<br />

• PTTP-code: 32 bits integer that represents the PTTP behaviour:<br />

o 0: Boot without VLANs <strong>and</strong> skip PTTP.<br />

o 1: Keep on requesting PTTP (does nothing).<br />

o [2-4095]: Boot with Management VLAN = PTTP-code. Skip PTTP.<br />

Submission page 375 UPA-OPERA

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!