#freeradius

[henrynolastname]

The world's leading RADIUS server. The project includes a GPL AAA server, BSD licensed client and PAM and Apache modules. Full support is available from NetworkRADIUS.

[ryanchapman]

ASA: debugging AnyConnect and radius

Ubuntu 14.04 (Linux 3.13.0-48), freeradius 2.1.12, ASA 9.4.2 (which runs Lua 5.0.2), AnyConnect 4.2

Setting up communications between an ASA and a radius server can be tricky, because it's hard to know what attributes the radius server is sending back and are being applied to a user session. One method is to use wireshark to capture the communications between the ASA and radius server. Another is to enable debugging on the ASA with debug dap trace. An easier way is to just have the attributes printed out on the end-user device when they log in.

The dynamic access policy feature of the ASA will let you input Lua functions to get this information. Open ASDM and go to

Configuration

Remote Access VPN

Network (Client) Access

Dynamic Access Policies

Click Add

Policy Name: debug

Priority: 1 (or whatever works in your environment)

In the Selection Criteria area, click Advanced

Make sure AND is selected. In the Logical Expressions box, enter:

assert(function() function print_table(tbl, prefix) if (type(tbl) == "table") then for k,v in pairs(tbl) do if (type(v) == "table") then print_table(v, prefix .. "." .. k) else CheckAndMsg(true, prefix .. "." .. k .. "=\"" .. v .. "\"", "") end end end end CheckAndMsg(true, "============", "") CheckAndMsg(true, "DEBUG", "") print_table(aaa, "aaa") print_table(endpoint, "endpoint") return true end)()

Click OK to close the Add Dynamic Access Policy window, then click Apply

Now, if you log in to AnyConnect on a device, you'll notice that a dropdown message box appears and shows you the values of the AV pairs.

You might want to be able to toggle the display of the debug message from a freeradius server. That will allow you to turn it on when a user calls in and reports problems and you need to know what settings are being applied to their account.

On the freeradius server, change their user record and add Reply-Message = "debug_print". Note that you could use any attribute you want, but I know that Reply-Message does work.

test Cleartext-Password := "test123" Class = "OU=Test_VPN;", Reply-Message = "debug_print"

Back in ASDM, go to the debug policy you created earlier and change it so that it only fires when Reply-Message = "debug_print"

OK and Apply

[ryanchapman]

Troubleshooting EAP-TLS with freeradius

Ubuntu 14.04 (Linux 3.13.0-53), freeradius 2.1.12, wpa_supplicant 2.4,

I'm in the process of setting up wifi to use one of the more secure authentication methods, EAP-TLS (well, more secure than WPA-PSK or WPA2-PSK). WPA-Enterprise with 802.1x using EAP-TLS uses the same mechanism that protects web sites, TLS.  Anyway, I followed the great instructions Thomas Hruska put together at http://cubicspot.blogspot.com/2013/04/setting-up-wpa2-enterprise-aes-with.html but it wouldn't work.  After figuring out the problem, I set out to document here the troubleshooting steps.

First, I stopped freeradius with service freeradius stop and restarted it with freeradius -X (you can also start it with freeradius -Xx to get even more debugging info).

Attempting authentication with a Windows computer was becoming time-consuming, so I downloaded wpa_supplicant and compiled the eapol_test program, which can simulate a client authentication attempt from the same machine freeradius is running on.

To compile eapol_test:

Download wpa_supplicant

root@freeradius-vagrant:/tmp# wget http://w1.fi/releases/wpa_supplicant-2.4.tar.gz --2015-07-02 16:17:56-- http://w1.fi/releases/wpa_supplicant-2.4.tar.gz Resolving w1.fi (w1.fi)... 212.71.239.96 Connecting to w1.fi (w1.fi)|212.71.239.96|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2525648 (2.4M) [application/x-gzip] Saving to: ‘wpa_supplicant-2.4.tar.gz’ 100%[=======================================================================================================================================>] 2,525,648 419KB/s in 6.3s 2015-07-02 16:18:03 (392 KB/s) - ‘wpa_supplicant-2.4.tar.gz’ saved [2525648/2525648]

Decompress

root@freeradius-vagrant:/tmp# tar zxvf wpa_supplicant-2.4.tar.gz wpa_supplicant-2.4/ wpa_supplicant-2.4/wpa_supplicant/ wpa_supplicant-2.4/wpa_supplicant/wpas_glue.c [...] wpa_supplicant-2.4/wpa_supplicant/eapol_test.c [...]

Change to the wpa_supplicant directory where eapol_test.c lives

root@freeradius-vagrant:/tmp# cd wpa_supplicant-2.4/wpa_supplicant/

Copy the default config to .config, which is where make(1) expects it to be

root@freeradius-vagrant:/tmp/wpa_supplicant-2.4/wpa_supplicant# cp defconfig .config

Compile eapol_test

root@freeradius-vagrant:/tmp/wpa_supplicant-2.4/wpa_supplicant# make eapol_test CC config.c CC notify.c [...] CC ../src/utils/ip_addr.c LD eapol_test

Copy eapol_test to root's home directory

root@freeradius-vagrant:/tmp/wpa_supplicant-2.4/wpa_supplicant# cp eapol_test ~

Now that you have the eapol_test binary compiled, you need a config file to feed to it. Following Thomas' directory scheme (see above for his tutorial), we'll put it in /var/certs/freeradius/

root@freeradius-vagrant:/tmp/wpa_supplicant-2.4/wpa_supplicant# cd /var/certs/freeradius/ root@freeradius-vagrant:/var/certs/freeradius# USER_NAME=`grep emailAddress client.cnf | grep '@' | sed 's/.*=//;s/^ *//'`; PASSWORD_CLIENT=`grep output_password client.cnf | sed 's/.*=//;s/^ *//'`; cat <eapol_test-eaptls.conf > network={ > ssid="DoesNotMatterForThisTest" > key_mgmt=WPA-EAP > eap-TLS > identity="${USER_NAME}" > ca_cert="/var/certs/freeradius/ca.pem" > client_cert="/var/certs/freeradius/${USER_NAME}.pem" > private_key="/var/certs/freeradius/client.key" > private_key_passwd="${PASSWORD_CLIENT}" > eapol_flags=3 > } > EOF

In a different terminal, start up freeradius with

freeradius -X

Attempt an authentication

root@freeradius-vagrant:/var/certs/freeradius# ~/eapol_test -a10.0.2.15 -p1812 -sSEKRET -ceapol_test-eaptls.conf -r0 Reading configuration file 'eapol_test-eaptls.conf' Line: 1 - start of a new network block ssid - hexdump_ascii(len=24): 44 6f 65 73 4e 6f 74 4d 61 74 74 65 72 46 6f 72 DoesNotMatterFor 54 68 69 73 54 65 73 74 ThisTest key_mgmt: 0x1 [...] EAP: deinitialize previously used EAP method (13, TLS) at EAP deinit ENGINE: engine deinit MPPE keys OK: 0 mismatch: 1 FAILURE

So we got a FAILURE. Back in the freeradius window, I see that the cert could not be verified

rlm_eap_tls: Certificate CN ([email protected]) fails external verification! [tls] chain-depth=0, [tls] error=0 [tls] --> User-Name = [email protected] [tls] --> BUF-Name = [email protected] [tls] --> subject = /C=US/ST=Montana/O=XXXXX, Inc./[email protected]/[email protected] [tls] --> issuer = /C=US/ST=Montana/L=XXXXX/O=XXXXX, Inc./[email protected]/CN=XXXXX Wifi Certificate Authority [tls] --> verify return:0 [tls] >>> TLS 1.0 Alert [length 0002], fatal certificate_unknown TLS Alert write:fatal:certificate unknown TLS_accept: error in SSLv3 read client certificate B rlm_eap: SSL error error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned SSL: SSL_read failed in a system call (-1), TLS session fails. TLS receive handshake failed during operation [tls] eaptls_process returned 4 [eap] Handler failed in EAP/tls [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject # Executing group from file /etc/freeradius/sites-enabled/ruckusAP1 +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> [email protected] attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 8 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 8 Sending Access-Reject of id 8 to 10.0.2.15 port 34071 EAP-Message = 0x04080004 Message-Authenticator = 0x00000000000000000000000000000000

I wonder why. My certs are in /etc/freeradius

root@freeradius-vagrant:/etc/freeradius/certs# ls -l total 4 lrwxrwxrwx 1 root freerad 28 Jun 24 20:08 ca.pem -> /var/certs/freeradius/ca.pem -rw-r--r-- 1 root freerad 245 Jun 22 22:15 dh lrwxrwxrwx 1 root freerad 32 Jun 24 20:08 server.key -> /var/certs/freeradius/server.key lrwxrwxrwx 1 root freerad 32 Jun 24 20:08 server.pem -> /var/certs/freeradius/server.pem

and they can be read by the freerad user (the user the freeradius daemon is running as)

root@freeradius-vagrant:/etc/freeradius/certs# ls -l /var/certs/freeradius/ca.pem /var/certs/freeradius/server.key /var/certs/freeradius/server.pem -rw-r----- 1 root ssl-cert 2419 Jun 24 23:25 /var/certs/freeradius/ca.pem -rw-r----- 1 root ssl-cert 3394 Jun 24 23:26 /var/certs/freeradius/server.key -rw-r----- 1 root ssl-cert 5878 Jun 24 23:26 /var/certs/freeradius/server.pem

The freerad user is a member of the ssl-cert group, so it can read the certs directory files ok

root@freeradius-vagrant:/etc/freeradius/certs# groups freerad freerad : freerad shadow ssl-cert

Next step is to travel down the rabbit hole of why freeradius cannot verify the client certificate. I do know that freeradius relies on the openssl package to do cert verification, so maybe it is executing openssl. If it is, then strace will catch the command freeradius is running.

root@freeradius-vagrant:/etc/freeradius/certs# strace -eexecve -ttvfo /tmp/tt -s 1024 freeradius -X FreeRADIUS Version 2.1.12, for host x86_64-pc-linux-gnu, built on Feb 24 2014 at 14:57:57 Copyright (C) 1999-2009 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License v2. Starting - reading configuration files ... [...]

and execute eapol_test again

root@freeradius-vagrant:/var/certs/freeradius# ~/eapol_test -a10.0.2.15 -p1812 -sSEKRET -ceapol_test-eaptls.conf -r0 Reading configuration file 'eapol_test-eaptls.conf' Line: 1 - start of a new network block ssid - hexdump_ascii(len=24): 44 6f 65 73 4e 6f 74 4d 61 74 74 65 72 46 6f 72 DoesNotMatterFor 54 68 69 73 54 65 73 74 ThisTest key_mgmt: 0x1 [...] EAP: deinitialize previously used EAP method (13, TLS) at EAP deinit ENGINE: engine deinit MPPE keys OK: 0 mismatch: 1 FAILURE

Excellent, another failure

Back in the window where freeradius and strace are running, looking at the file /tmp/tt where strace wrote all execve(2) system call invocations, I see that it did in fact execute openssl to verify the client cert.

[...] Waking up in 1.0 seconds. Cleaning up request 8 ID 8 with timestamp +64 Ready to process requests. ^C root@freeradius-vagrant:/etc/freeradius/certs# cat /tmp/tt 11101 21:18:50.164298 execve("/usr/sbin/freeradius", ["freeradius", "-X"], ["XDG_SESSION_ID=7", "SHELL=/bin/bash", "TERM=xterm-256color", "USER=root", "LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*"..., "MAIL=/var/mail/root", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "PWD=/etc/freeradius/certs", "LANG=en_US.UTF-8", "SHLVL=1", "HOME=/root", "LOGNAME=root", "LESSOPEN=| /usr/bin/lesspipe %s", "XDG_RUNTIME_DIR=/run/user/1000", "LESSCLOSE=/usr/bin/lesspipe %s %s", "_=/usr/bin/strace", "OLDPWD=/etc/freeradius"]) = 0 11122 21:19:54.483582 execve("/usr/bin/openssl", ["/usr/bin/openssl", "verify", "-CApath", "/etc/freeradius/certs", "/var/tmp/radiusd/freeradius.client.XXnZcbyR"], ["USER_NAME=\"[email protected]\"", "NAS_IP_ADDRESS=127.0.0.1", "CALLING_STATION_ID=\"02-00-00-00-00-01\"", "FRAMED_MTU=1400", "NAS_PORT_TYPE=Wireless-802.11", "CONNECT_INFO=\"CONNECT 11Mbps 802.11b\"", "EAP_MESSAGE=0x020804420d002da2bc70b9dabd6e808364e70cce8f29bca839f5f3f8fa79ce502fccef2fa978810e659ad88b4ef09c854c505afba4ad58d46bb84868cbdc720899b49e4ce7cba798fa33fdd30691b4d076f6899b52a40bb2f887b82ddff9bbb0dc774ff3e04b5565d0340a626df5bf48cc4cddb06d551826199248d6e32f091b1f51d9878e83b49809c0e3524df0a7159e17fe7b0131fee3a1af74d81f8b655fcd275612ae2517835c6c408f14b0d849f33e1efdc3db483a832818a10eb783cb204bda90a7d7349ae660daaec59f78b1713028dc4a6e47e3c01eb43757b82d1fbfe90cec33dc0ba3f0936986b4cb1c9e3b939c64976634c3577a5b6c71", "EAP_MESSAGE=0x71265f3525c485df48f7816eb18dbf6f9a85561413c37283b3bb0dea51f8654122ee549c0a3f6fbbf5916cae5f9055bc19669da55005f21b827bf99dcfc5effbe38890a6f80231759786993a9e33288bcdb6d2838964d77513bd66eb303dafaa0ccbecf501f11f3b9e40d42b37b3e6c67ca154a5f9a129e72fd381e24e46d52cfedc970fbc9b28031b850eecf8ceca78c0eaf4bbae72c6b037e86f8e1150b2f799d0f587d029812d046e0b61b1d4d2726ee66dc31603010046100000424104acd3f28e5f69bdc07945db523a44066d74aa73648e448631f0eb67c11d6b5fc42f2e42f2fbfa9ee0d993f843bb2b756de1f8dfede848b6485834659d69ab", "EAP_MESSAGE=0x4c6e16030102060f0002020200d05242c896fd7ac6a483cde001e4ab4ba1de4e7d7340d618ba3b9e57419fc9b9d4d76cf9a7855bb81821b8469ec50e3c06475f71652c10e0f790d3f112236fbf82c14c2a4a4eeb8c7889bc517eff3768478a6099ea4c81a1133945a45afb6d3c031f034899edc9e93403a580ef8028cc5d2052559c747eb60d831a590c26e9ea748a89835f50de617ea8dfce6e9cd23fdfdcb9949bf1facfa907b1e11e06230e3a0fdf5230ddcfdc1962d394bfa373c6aab10e9e8e10574cec7c6fc5ca1f42cb4f8df2ce92cbfad6e2e10413795d5c2231dad82c30f485a641073e2267e5edfdae45ba62b923a19d2f0d7cf7641bdba1", "EAP_MESSAGE=0x883ed91d6b2e271940f9793025052b2270742cd0cdda10ff3d371af52dc7fd9e7f7259310fa9cb000f1dcc453413e2c203d5f26d50d002c88a3886f61128b214e7c9458af2b719fd37f07b91a09a407b4c72311a12d974cdd93b15675ac681d3c89981151cc6a4c6a4477a8e9dea42b388df96870980405f3af7ea73cfaa8cbf537941f8517e134cbb74dbf4e7658456f23f92a29440142b419c61b8a6be1a0e018a35f1924bd7a4763b476d3e9d9e2a6946ad6fc6f0dad9fb76b2ce305ccfbf3db1f22b19541d96148e46327f4790ad797673148c99d09d7e2e74cb6b3638c469e4950e75f3e26e721f9e17781c06c577be5a9ff68aee5ca66bdd7452", "EAP_MESSAGE=0x677a2de333d1ed17017156a3ad712576535db214030100010116030100302f898135f257599f9fdb3acc07d390f14d03057670c64c1a3faec01fa15cf11ba5b5642b20646e065d7d8b56ce7b7d9d", "STATE=0x91dd759796d5782502cfcac1e7c999b0", "MESSAGE_AUTHENTICATOR=0x6c6da037ca70fffeb5c047426910ce4f", "EAP_TYPE=EAP-TLS", "TLS_CLIENT_CERT_FILENAME=\"/var/tmp/radiusd/freeradius.client.XXnZcbyR\""]) = 0 11122 21:19:54.487938 +++ exited with 2 +++ 11101 21:19:54.488045 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=11122, si_status=2, si_utime=0, si_stime=0} --- 11101 21:21:39.983570 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL, si_value={int=2, ptr=0x2}} --- 11101 21:21:39.984023 +++ killed by SIGINT +++

Now I can do the exact same thing freeradius did, by asking openssl to verify my client cert. Let's see what it says

root@freeradius-vagrant:/var/certs/freeradius# USER_NAME=`grep emailAddress client.cnf | grep '@' | sed 's/.*=//;s/^ *//'`; /usr/bin/openssl verify -CApath /etc/freeradius/certs ${USER_NAME}.pem [email protected]: C = US, ST = Montana, O = "XXXXXX, Inc.", CN = [email protected], emailAddress = [email protected] error 20 at 0 depth lookup:unable to get local issuer certificate

Searching Google for openssl unable to get local issuer certificate returns the page https://www.openssl.org/docs/apps/verify.html. That page is simply the man page for openssl verify, and the -CApath option tells me the problem and the solution:

-CApath directory A directory of trusted certificates. The certificates should have names of the form: hash.0 or have symbolic links to them of this form ("hash" is the hashed certificate subject name: see the -hash option of the x509 utility). Under Unix the c_rehash script will automatically create symbolic links to a directory of certificates.

It can't really be that simple. Let's try running c_rehash in /etc/freeradius/certs

root@freeradius-vagrant:/etc/freeradius/certs# c_rehash . Doing . server.pem => 6eacae23.0 server.pem => d01a9214.0 ca.pem => 433869d5.0 ca.pem => c34814f6.0 root@freeradius-vagrant:/etc/freeradius/certs# cd /var/certs/freeradius/ root@freeradius-vagrant:/var/certs/freeradius# USER_NAME=`grep emailAddress client.cnf | grep '@' | sed 's/.*=//;s/^ *//'`; /usr/bin/openssl verify -CApath /etc/freeradius/certs ${USER_NAME}.pem [email protected]: OK

Woohoo! That seems to be it. Let's try a eapol_test again just to make sure

root@freeradius-vagrant:/var/certs/freeradius# ~/eapol_test -a10.0.2.15 -p1812 -sSEKRET -ceapol_test-eaptls.conf -r0 Reading configuration file 'eapol_test-eaptls.conf' Line: 1 - start of a new network block ssid - hexdump_ascii(len=24): 44 6f 65 73 4e 6f 74 4d 61 74 74 65 72 46 6f 72 DoesNotMatterFor 54 68 69 73 54 65 73 74 ThisTest key_mgmt: 0x1 [...] EAPOL: SUPP_PAE entering state AUTHENTICATED EAPOL: SUPP_BE entering state RECEIVE EAPOL: SUPP_BE entering state SUCCESS EAPOL: SUPP_BE entering state IDLE eapol_sm_cb: result=1 EAPOL: Successfully fetched key (len=32) PMK from EAPOL - hexdump(len=32): 74 07 88 20 6e e5 a9 9c 21 33 d7 eb e3 3a 0b c2 f6 7a f7 98 a5 ff 3b fb 9d 4f 8b 49 ee 13 c6 93 No EAP-Key-Name received from server EAP: deinitialize previously used EAP method (13, TLS) at EAP deinit ENGINE: engine deinit MPPE keys OK: 1 mismatch: 0 SUCCESS

Yep, it works now.

[kurusetra]

Single Sign On dengan Mikrotik RouterOS

Single Sign On dengan Mikrotik RouterOS

Topologi Single Sign On (SSO) dengan Mikrotik RouterOS

  <!-- H5 { margin-top: 0.42cm; margin-bottom: 0.21cm; page-break-after: avoid; }H5.western { font-family: "Arial",sans-serif; font-size: 11pt; }H5.cjk { font-family: "Droid Sans Fallback"; font-size: 11pt; }H5.ctl { font-family: "Lohit Hindi"; font-size: 11pt; }P { margin-bottom: 0.21cm; }A:link { } -->

Artikel Kali ini kita membahas cara membangun Single Sign On dengan Mikrotik. Single Sign On merupakan cara untuk mengelola username dan password secara terpusat menggunakan Mikrotik. Username / Login dan Password Server PPTP, Server OVPN dan Hotspot Login dikelola oleh Server Radius Mikrotik RouterBoard.

Keunggulan dari authentifikasi terpusat atau single sign on, pengguna pptp, ovpn atau hotspot bisa berpindah lokasi ke perangkat lain hanya dengan satu username / login dan password. Tidak perlu lagi melakukan authentifikasi ulang.

Administrator jaringan cukup mengelola username dan password melalui Server Radius Mikrotik RouterOS. Kemudian perangkat Mikrotik RouterBoard kita integrasikan dengan Server Radius. Sehingga saat client pptp, ovpn dan hotspot memasukan login dan password, perangkat Mikrotik RouterBoard akan memeriksa validitas login dan password ke Server Radius Mikrotik. Apabila Valid atau sah akses ke pptp, ovpn dan hotspot di izinkan.

Kita bahas konfigurasi Integrasi Mikrotik RouterBoard ke Server Radius secara garis besar saja.

Konfigurasi Server Radius Mikrotik RouterOS

Berdasarkan topologi gambar di atas kita definisikan Alamat IP

Server Radius : 192.168.56.10

PPTP Server : 192.168.56.20

OVPN Server : 192.168.56.30

Hotspot Login : 192.168.56.40

PPTP Server, OVPN Server dan Hotspot Login kita integrasikan ke Server Radius.

Pertama Kita daftarkan alamat IP PPTP Server, OVPN Server dan Hotspot Login ke Server Radius

kita buka konfigurasi Server Radius di Mikrotik RouterOS

http://192.168.56.10/userman

Login : admin

Password : kosongkan

Kemudian klik Routers

Konfigurasi NAS atau Routers PPTP, OVPN & Hotspot Mikrotik RouterBoard

Daftar Alamat IP Perangkat Mikrotik RouterBoard

  <!-- P { margin-bottom: 0.21cm; }A:link { } -->

Buat Profile Radius

Pembuatan Profile Radius Mikrotik

  <!-- P { margin-bottom: 0.21cm; }A:link { } -->

Daftarkan User Radius sesuai dengan profile Radius yang akan di gunakan

  Registrasi User Radius Mikrotik

  <!-- H5 { margin-top: 0.42cm; margin-bottom: 0.21cm; page-break-after: avoid; }H5.western { font-family: "Arial",sans-serif; font-size: 11pt; }H5.cjk { font-family: "Droid Sans Fallback"; font-size: 11pt; }H5.ctl { font-family: "Lohit Hindi"; font-size: 11pt; }P { margin-bottom: 0.21cm; }A:link { } -->

Integrasi PPTP & OVPN Server dengan Server Radius

Pada Mikrotik RouterBoard

PPTP Server : 192.168.56.20

OVPN Server : 192.168.56.30

Kita aktifkan Authentifikasi Radius di PPP -> Secrets -> Klik PPP Authentication & Accounting

Aktifkan authentifikasi Radius pada PPP

  <!-- P { margin-bottom: 0.21cm; }A:link { } -->

Kemudian kita Integrasikan dengan Server Radius

Integrasikan Server PPTP & OVPN Dengan Server Radius

  <!-- H5 { margin-top: 0.42cm; margin-bottom: 0.21cm; page-break-after: avoid; }H5.western { font-family: "Arial",sans-serif; font-size: 11pt; }H5.cjk { font-family: "Droid Sans Fallback"; font-size: 11pt; }H5.ctl { font-family: "Lohit Hindi"; font-size: 11pt; }P { margin-bottom: 0.21cm; }A:link { } -->

Integrasi Hotspot dengan Server Radius

Pada Mikrotik RouterBoard

Hotspot Login : 192.168.56.40

Kemudian klik IP -> Hotspot -> Server Profiles dan edit profile hotspot -> RADIUS

centang Use Radius

Aktifkan authentifikasi Radius Pada Hotspot

<!-- P { margin-bottom: 0.21cm; }A:link { } -->

Kemudian Klik Radius -> +

Integrasi Hotspot dengan Server Radius

  Single Sign On dengan Mikrotik RouterOS was originally published on Kurusetra Computer

[kurusetra]

Membangun Provider Internet Hotspot dengan Mikrotik

<!-- P { margin-bottom: 0.21cm; } -->

Membangun Provider Internet Hotspot dengan Mikrotik

Provider Layanan Internet Hotspot dengan Mikrotik berbeda Lokasi atau Geografis

  <!-- P { margin-bottom: 0.21cm; } -->

Artikel kali ini membahas Konsep Membangun Provider Layanan Koneksi Internet Hotspot menggunakan Mikrotik berbeda kota,desa, wilayah atau geografis. Pengelolaan User dan Voucher Internet di lakukan secara terpusat menggunakan Server Radius Hotspot Mikrotik RouterOS, Server Radius Hotspot berada di kantor pusat provider internet hotspot.

Pengguna / User hotspot berada di lokasi yang berbeda. Setiap pengguna / user hotspot di layani oleh setiap POP / BTS hotspot berbasis mikrotik, yang koneksi internetnya melalui Modem ADSL Speedy atau Modem GSM/CDMA Mobile Internet (XL, Axis, Simpati, Tri, Smartfren).

Server OpenVPN yang terpasang pada VPS Ubuntu sebagai jalur koneksi authentifikasi radius Peer to Peer dari POP / BTS Hotspot ke Server Radius Hotspot.

Saat pertama kali user browsing ke website maka ditanyakan login kemudian memasukan username / voucher beserta password. Setelah POP / BTS Hotspot melakukan validasi ke Server Radius Hotspot Mikrotik RouterOS melalui jalur OpenVPN. Apabila valid atau sah maka koneksi ke internet diperbolehkan.

Pada Mikrotik POP / BTS Hotspot kita memasukan alamat IP VPN Server Radius Hotspot Mikrotik RouterOS.

Anggap saja IP VPN Server Radius Hotspot Mikrotik: 10.8.10.100

Server Radius Hotspot dan POP / BTS Hotspot Mikrotik berfungsi sebagai OVPN Client

Di Mikrotik POP / BTS Hotspot Ponorogo dan Takeran

Konfigurasi POP / BTS HotSpot Mikrotik ke IP VPN Server Radius Mikrotik

Membangun Provider Internet Hotspot dengan Mikrotik was originally published on Kurusetra Computer

[kurusetra]

Integrasi Mikrotik Hotspot dengan FreeRadius YFi

<!-- P { margin-bottom: 0.21cm; } -->

Integrasi Mikrotik Hotspot dengan FreeRadius YFi

<!-- P { margin-bottom: 0.21cm; } -->

Tutorial ini membahas integrasi router Mikrotik Hotspot dengan FreeRadius YFi, yang cara instalasinya telah kita bahas di YFi Hotspot Manager. Setelah kita konfigurasi mikrotik hotspot mampu mengenali user yang terdapat pada YFi Hotspot Manager. Sehingga pengguna hotspot bisa login menggunakan user YFi. Mikrotik kita integrasikan langsung dengan FreeRadius, dengan authentifikasi HTTP-PAP.

Berikut ini langkah mudah konfigurasi mikrotik menggunakan winbox.

Kita buat permanent user terlebih dahulu di YFi Hotspot manager

<!-- P { margin-bottom: 0.21cm; } -->

Kita test FreeRadius secara lokal di server hotspot

<!-- P { margin-bottom: 0.21cm; } -->

Kemudian kita konfigurasi Mikrotik Hotspot

Sekarang Kita konfigurasi profilenya

Kemudian kita konfigurasi agar mikrotik terintegrasi dengan FreeRadius YFi

Login ke hotspot melalui klien

Page status mikrotik hotspot

Integrasi Mikrotik Hotspot dengan FreeRadius YFi was originally published on Kurusetra Computer

[kurusetra]

DD-WRT Chillispot & FreeRadius YFi

DD-WRT Chillispot & FreeRadius YFi

<!-- P { margin-bottom: 0.21cm; }A:link { } -->

Kali ini kita akan bahas integrasi Chillispot DD-WRT dengan FreeRadius dan YFi hotspot manager. Firmware DD-WRT harus terpasang pada perangkat Router Linksys WRT54G Series ataupun perangkat wireless yang di dukung. Chillispot harus terpasang pada server linux dengan protokol HTTPS Apache2 sebagai web server. DD-WRT hanya meneruskan request page hotspotlogin.cgi dari perangkat ke Apache2 web server. Secara default user yang sudah terhubung ke wireless akan mendapatkan IP 192.168.182.xxx dari Chillispot DD-WRT. Saat browsing ke situs misalkan detik.com maka akan diarahkan ke halaman login Chillispot server Ubuntu. Pengguna tinggal memasukan user dan password yang sudah didaftarkan pada YFi Hotspot Manager.

Konfigurasi Chillispot di Server Ubuntu

a2enmod ssl a2ensite default-ssl service apache2 restart apt-get install chillispot update-rc.d -f freeradius remove vim /usr/lib/cgi-bin/hotspotlogin.cgi $uamsecret = "testing123"; $userpassword=1;

Konfigurasi LAN

Setup -> Basic Setup

<!-- P { margin-bottom: 0.21cm; }A:link { } -->

Disable Firewall DD-WRT

Security -> Firewall

<!-- P { margin-bottom: 0.21cm; }A:link { } -->

Konfigurasi Chillispot DD-WRT

<!-- P { margin-bottom: 0.21cm; }A:link { } -->

Redirect URL: https://192.168.56.2/cgi-bin/hotspotlogin.cgi

<!-- P { margin-bottom: 0.21cm; }A:link { } -->

NAT Interface Bridge DD-WRT

Administration -> Commands

Login User Chillispot

Status Page Login Chillispot

    DD-WRT Chillispot & FreeRadius YFi was originally published on Kurusetra Computer

[kurusetra]

VPN PPTP Server FreeRadius Ubuntu

<!-- P { margin-bottom: 0.21cm; }A:link { } -->

VPN PPTP Server FreeRadius Ubuntu

Pada tutorial kali ini kita bahas integrasi Server VPN PPTP dengan FreeRadius, manajemen user dan password dikelola oleh YFi Hotspot Manager, tutorialnya bisa dilihat .. klik sini. Server menggunakan Ubuntu 12.04 LTS Precise Pangolin. User dan password yang digunakan untuk login ke Server VPN PPTP sudah terdaftar pada YFi Hotspot Manager, user : budi@ri, password:1234. Integrasi Server VPN PPTP dengan FreeRadius memberikan kemampuan kita untuk mengelola ratusan sampai ribuan user VPN, yang bisa diakses selama ada koneksi internet.

    Instalasi PPTP Server dan Radius Plugin

apt-get install ppp pptpd radiusclient1

  Konfigurasi PPTP Server

vim /etc/pptpd.conf option /etc/ppp/pptpd-options logwtmp localip 192.168.100.1 remoteip 192.168.100.234-238,192.168.100.245 vim /etc/ppp/pptpd-options name pptpd require-pap refuse-chap refuse-mschap refuse-mschap-v2 ms-dns 8.8.8.8 ms-dns 8.8.4.4 proxyarp # Debian: do not replace the default route nodefaultroute lock nobsdcomp plugin radius.so plugin radattr.so

    Konfigurasi Radius Client

vim /etc/radiusclient/radiusclient.conf auth_order radius,local login_tries 4 login_timeout 60 nologin /etc/nologin issue /etc/radiusclient/issue authserver localhost acctserver localhost servers /etc/radiusclient/servers dictionary /etc/radiusclient/dictionary login_radius /usr/sbin/login.radius seqfile /var/run/radius.seq mapfile /etc/radiusclient/port-id-map default_realm radius_timeout 10 radius_retries 3 login_local /bin/login vim /etc/radiusclient/servers 127.0.0.1 testing123

  Restart PPTP Server

service pptpd restart

  Konfigurasi Client PPTP MS Windows XP

    VPN PPTP Server FreeRadius Ubuntu was originally published on Kurusetra Computer