Hello Kitty Online Indonesia

Hello Kitty Online segera hadir di Indonesia

Hello Kitty Online adalah Free to Play MMORPG yang dikembangkan oleh Sanrio Digital dan Typhoon Games, dimana pemain akan menjadi bagian dalam dunia Sanrio dan berinteraksi dengan Hello Kitty and Friends. Ditampikan dengan grafik ciri khas Hello Kitty yang sudah digemari fans dari seluruh dunia, ditambahkan dengan gameplay yang bervariasi melebihi MMORPG standar pada umumnya.

Dalam Hello Kitty Online pemain tidak hanya bertarung melawan monster, namun terdapat banyak aktifitas lucu dan unik lainnya seperti bertani, memiliki dan mendekorasi rumah, mempelajari skill memasak, menjahit, bahkan membuat furniture sendiri. Tersedia juga berbagai mini games yang bisa dimainkan bersama pemain lain.

Saat ini Hello Kitty Online US masih dalam tahap Closed Beta yang tertutup untuk sebagian anggota dan bersiap untuk Open Beta pada 2009, yang artinya Hello Kitty Online Indonesia akan menjadi game yang benar-benar baru/anyar dimana kita biasanya ditawarkan game online yang sudah cukup lama dirilis di luar negeri sebelumnya.  (gameqq.net)

Informasi lebih lanjut pada situsnya di: http://hellokittyonline.co.id/

Tiga Hacker Beken di dunia

Dunia hacker sudah dikenal sejak adanya komputer, dan mereka mulai lebih meraja-lela sejak adanya internet. Nah kalau kamu penasaran siapa saja Hacker yang paling beken di dunia, artikel ini akan bisa menjawabnya. 1. Kevin Mitnick (lahir 6 Agustus 1963) Kevin dikenal karena aksi hackernya yang cukup menghebohkan Amerika, dan merupakan “the most wanted computer criminal in United States history”. Kisah hidupnya sempat di-filmkan sebanyak 2 kali di Hollywood, dengan judul ‘Takedown’ dan ‘Freedom Downtime’. Kevin memulai aksi hackernya pertama kali terhadap sistem transportasi di Los Angeles. Setelah berhasil menjebol sistem ‘punchcard’ (pembacaan kartu langganan bus), dia bisa memakai bus kemana saja secara gratis. Aksi berikutnya Kevin adalah menjebol sistem telepon, dimana dia bisa menggunakan layanan telepon jarak jauh dengan gratis. Setelah mengenal komputer, Kevin sempat melakukan hacking pada: - DEC (Digital Equipment Corporation) system - IBM Mini Komputer di ‘Computer Learning Center Los Angeles’ - Hacking sistem Motorola, NEC, Nokia, Sun Microsystems dan Fujitsu Siemens - Mengelabui FBI Kevin akhirnya bisa tertangkap dan menjalani hukuman penjara 5 tahun. Dirinya baru dibebaskan pada tahun 2000. Setelah bebas, dia tidak diperbolehkan memakai perangkat telekomunikasi dan telepon hingga tahun 2003. Setelah Kevin menggugat haknya di pengadilan, akhirnya dirinya diperbolehkan menggunakan alat komunikasi dan komputer. Saat ini Kevin bekerja sebagai seorang konsultan sekuriti komputer. 2. Adrian Lamo (lahir 1981) Adrian adalah seorang jurnalis dan seorang hacker berpredikat ‘abu-abu’ (bisa baik, bisa jahat), terutama dikenal dalam hacking serangkaian jaringan komputer yang mempunyai tinggi keamanan tinggi. Dirinya mulai dikenal orang setelah berhasil menjebol sistem komputer ‘The New York Times’ pada tahun 2002 dan ‘Microsoft’. Dia juga dikenal dapat mengidentifikasi kekurangan dalam keamanan jaringan komputer dari perusahaan yang termasuk dalam daftar ‘Fortune 500 companies’ dan kemudian memberitahu mereka kelemahan dan celah yang dia ditemukan. Kasus ini sempat diteliti oleh FBI selama 15 bulan, setelah New York Times melaporkan adanya sistem mereka yang dijebol. Akhirnya diketahui pada tahun 2003 bahwa penyebabnya adalah Adrian. Adrian sempat bersembunyi beberapa hari, dan akhirnya menyerahkan diri ke FBI pada tahun 2004. Adrian akhirnya harus menjalani hukuman ‘tahanan rumah’ oleh orang tuanya, dan 2 tahun masa percobaan dengan denda sekitar $65,000. Adrian juga diyakini berusaha menjebol sistem komputer Yahoo!, Sun Microsystem, Bank of America, dan CitiGroup, dengan memanfaatkan celah keamanan yang ada. 3. Jonathan James (lahir 12 Desember 1983) James adalah orang Amerika Serikat termuda yang dijatuhi hukuman atas kejahatan dunia cyber. Saat baru umur 16 tahun dia dikirim ke penjara karena  menjebol situs departemen pertahanan Amerika. Dirinya mengakui melakukan hacking adalah sebuah tantangan dan merupakan salah satu kesenangan tersendiri. NASA juga kena getah buah dari keisengannya, James berhasil mencuri (download) software NASA yang diperkirakan bernilai $1.7 juta dollar AS pada tahun 1999. NASA harus dipaksa untuk mematikan server dan sistemnya akibat dari perbuatan si James selama tiga minggu. Dan setelah itu NASA harus mengelaurkan biaya sekiatar $41,000 untuk membetulkan sistemnya yang dijebol. 6 bulan setelah James menjebol NASA, dia diciduk di rumahnya oleh polisi setempat pada jam 6 pagi. Dia menjalani hukuman penjara 6 bulan karena masih di bawah umur, dan hukuman percobaan ‘tahanan rumah’ hingga umurnya mencapai 21 tahun. James tidak diperbolehkan untuk berinterkasi dengan komputer selama itu. James meninggal dunia pada tanggal 18 Mei 2008, tidak ada informasi apa yang menyebabkan kematiannya. Penulis: Erwin Sumber: Wikipedia – Wahyoe.WordPress – Connel24.Blogspot

Antivirus & Games

Penggunaan Antivirus Menurunkan Performa PC Untuk Bermain Game
Kebanyakan gamer tidak menyukai antivirus, konon membuat performa komputer sedikit melambat karena aplikasi antivirus. Gamer memilih mematikan antivirus mereka, agar tidak menurunkan performa PC. Extremetech memperlihatkan perbedaan antara performa beberapa game dengan software antivirus. Antivirus yang diuji termasuk Grisoft, BitDefender (the GameDefender edition), Kaspersky, dan Symantec’s Norton Antivirus (Gaming Edition). Lalu antivirus apa yang disarankan. AVG Free edition memiliki kemampuan lebih baik tetapi bukan yang terbaik. Selain gratis, software antivirus dari AVG tidak lebih jelek dibandingkan software Antivirus lain. Pilihan kedua adalah BitDefender atau NortonAV. Tetapi langkah awal dengan mematikan antivirus sebelum bermain game, tetap menjadi yang terbaik. Karena performa game tidak akan berkurang dibandingkan mengaktifkan software antivirus pada PC.

Tuntut Speedy…!!! (dari forum tetangga)

Telkom Speedy…
Disini dalam kapasitasnya sebagai penyedia jasa layanan internet
berkecepatan tinggi (Broadband), sangatlah jelas telah melanggar UU Perlindungan Konsumen
No. 8 Tahun 1999 Pasal 4 yang menyangkut hak konsumen .
(link UU No 8 : http://www.mediakonsumen.com/istimewa-05.htm)
Singkatnya pelanggaran Telkom Speedy sudah seharusnya mendapat tindakan dari Pemerintah namun tidak ada satupun pihak terkait (Pemerintah yang berwenang)
turun tangan dan terkesan didiamkan saja. Pelanggaran Telkom Speedy sangat merugikan
pihak konsumen dan dampaknya luar biasa mengganggu produktivitas kerja ataupun saat rileks (surfing, streaming video,dll) yang sudah merupakan tuntutan dijaman teknologi.

Beberapa pelanggaran pihak manajemen Telkom Speedy :

- Telkom Speedy Bertanggung jawap sepenuhnya atas keadaan Overload
(Kelebihan pengguna) sehingga menyebabkan kelambatan akses secara luas.
(Dan ini memang disengaja sebab konsekuensi atas kelebihan beban
sudah bisa diketahui pihak Telkom Speedy sebelumnya namun tetap mengambil User terus-menerus tanpa dibarengi kesiapan Infrastruktur yang memadai).
- kecurangan – kecurangan (Pembohongan Publik) :

a. Bandwith 1 mbps hilang entah kemana (kalau karena masalah jaringan/central itu sudah basi!!! hampir setiap harinya itu -itu saja alasannya. ) Pihak Telkom Speedy harus bersedia
Untuk menjawab JUJUR masalah ini dan bertanggung jawab!.
b. Iklan yang menjebak dengan slogan “Speed that you can trust” ?
“Streaming, Game Online dan download tanpa batas” tapi pada kenyataannya tidak seperti itu.
(Kalau bukan pembohongan publik lalu apa namanya?) Tidak ada pertanggung jawaban pihak penyedia jasa.
c. Manajemen Telkom Speedy dengan sengaja telah melanggar UU perlindungan Konsumen
No.8 Tahun 1999 Pasal 17 secara partial yang berbunyi:

Pasal 17
1. Pelaku usaha periklanan dilarang memproduksi iklan yang:
a. mengelabui konsumen mengenai kualitas, kuantitas, bahan,
kegunaan dan harga barang dan/atau tarif jasa serta ketepatan waktu Penerimaan barang dan/atau jasa;
c. memuat informasi yang keliru, salah, atau tidak tepat mengenai barang dan/atau jasa;
f. melanggar etika dan/atau ketentuan peraturan perundang-undangan mengenai periklanan.
2. Pelaku usaha periklanan dilarang melanjutkan peredaran iklan yang telah melanggar ketentuan pada ayat 1.

Anehnya masalah yang sudah begitu pelik dan menyangkut hak banyak orang seperti ini masih saja dibiarkan oleh petinggi – petinggi yang terkait (Tidak ada gunanya Pemerintah mengurusi korupsi masa lalu tapi membiarkan hal itu terus terjadi dimasa kini. Ibarat gali lubang tutup lubang).
Timbul pertanyaan…apa Bapak Preseiden yang terhormat sudah mengetahui masalah ini dan apa bila masalah ini sudah diketahui beliu, kira – kira apa
tindakan yang akan beliu ambil….
Mungkin para capres harus mengakomodir isu perbaikan kualitas layanan internet supaya figur mereka lebih populis… lol

Untangle (Network Router ++ ) , bisa Load balancing

Product Overview

Untangle delivers an integrated family of applications that simplify and consolidate the network and security products that businesses need at the network gateway.

• Pre-configured to work right away
• Downloadable for rapid deployment
• Integrated with a common GUI, logging & reporting
• Designed to run on generic Intel/AMD hardware

Open Source & Free		Commercial Add-ons
Web Filter Spam Blocker Spyware Blocker Protocol Control Virus Blocker Phish Blocker IPS Attack Blocker	Firewall OpenVPN Untangle Reports Routing & QoS	Live Support AD Connector Policy Manager Branding Manager eSoft Web Filter Kaspersky Virus Blocker PC Remote Remote Access Portal

Open Source (and Free)

The Untangle Server and 12 of the applications that run on it are open source and free under the GNU General Public License v2 (GPLv2). Untangle’s platform provides the GUI, logging, reporting and “virtual-pipelining” technology to make all of the apps run together smoothly. Signatures updates and software upgrades, which install automatically, are also included.

Commercial Add-ons

These are designed for networks with advanced needs. Commercial add-ons include live support, advanced management features and applications for additional security and remote access.

Deployment Options

Untangle has 3 network deployment options:

Router:  Dedicated server that performs routing & firewall services

Transparent Bridge:  Dedicated server that drops seamlessly behind existing routers & firewalls

Re-Router™:  Adds network-wide protection while running on an existing desktop  (runs on Windows)

Supported Platforms

Untangle runs as a bare-metal install, on Windows XP, VMware, Ubuntu & Debian

Hardware Requirements

Untangle runs on generic Intel/AMD hardware.  A Pentium III processor, 2 NICs and 512MB of RAM is the min spec for smaller networks and multi-core chips with extra RAM really make Untangle sing for larger networks. More specific sizing guidance and links to the community hardware compatibility list can be found on the Hardware Requirements wiki.

3rd Party Connectors

Active Directory:  Integrate with existing AD deployments

Kaseya:  Monitor & receive Untangle alerts

Level Platforms:  Monitor & receive Untangle alerts

N-Able:  Monitor & receive Untangle alerts

AntiVirus buat USB / Flashdisk

USB Virus Scan

Info: Website – Download1 – Download2

USB Virus Scan is an antivirus software installed in computer to block threats spreading through removable drives. USB Virus Scan provides 100% protection for computer against any malicious programs trying to attack via USB storage.

USB Virus Scan uses innovative proactive technology to block any threats via USB storage. There are relatively few products available in shops or on the Internet which offer even close to 100% protection against any malicious programs via USB drive. USB Virus Scan is the world’s best antivirus software to block threats via USB drive.

USB Virus Scan has been specifically designed to perform effectively regardless of the user’s level of computer expertise. Just install and forget it. It is the best USB virus protection software in the world .

Pfsense Makin Balancing aje….

Screenshootnya : disini

Versions

There are three pfSense platforms, multiple release versions, and development/testing snapshots available. The following describes the available platforms and versions.

Platforms

Three platforms are available.

Live CD with Installer

The Live CD platform allows you to run directly from the CD without installing to a hard drive or Compact Flash card. The configuration can be saved on a floppy disk or USB flash drive. Some features are not compatible with the live CD platform. In most circumstances, this should only be used as an evaluation of the software with your particular hardware.

Hard drive installation

The live CD includes an installer option to install pfSense to the hard drive on your system. This is the preferred means of running pfSense. The entire hard drive must be overwritten, dual booting with another OS is not supported.

Embedded

The embedded version is specifically tailored for use with any hardware using Compact Flash rather than a hard drive. CF cards can only handle a limited number of writes, so the embedded version runs read only from CF, with read/write file systems as RAM disks. Packages are not supported on embedded versions.

Stable Version

1.2 release

This is the recommended release for all installations. It is widely tested and deployed, and the only release that will receive bug fix releases and any necessary security fix releases in the future.

Features

pfSense includes most all the features in expensive commercial firewalls, and more in many cases. The following is a list of features currently available in the pfSense 1.2 release. All of these things are possible in the web interface, without touching anything at the command line.

In addition to features, this page also includes all limitations of the system of which we are aware. From our experience and the contributed experiences of thousands of our users, we understand very well what the software can and cannot do. Every software package has limitations. Where we differ from most is we clearly communicate them. We also welcome people to contribute to help eliminate these limitations. Many of the listed limitations are common to numerous open source and commercial firewalls. 1.2 limitations already fixed in the code that will become the next major release will be noted.

Firewall

• Filtering by source and destination IP, IP protocol, source and destination port for TCP and UDP traffic
• Able to limit simultaneous connections on a per-rule basis
• pfSense utilizes p0f, an advanced passive OS/network fingerprinting utility to allow you to filter by the Operating System initiating the connection. Want to allow FreeBSD and Linux machines to the Internet, but block Windows machines? pfSense can do so (amongst many other possibilities) by passively detecting the Operating System in use.
• Option to log or not log traffic matching each rule.
• Highly flexible policy routing possible by selecting gateway on a per-rule basis (for load balancing, failover, multiple WAN, etc.)
• Aliases allow grouping and naming of IPs, networks and ports. This helps keep your firewall ruleset clean and easy to understand, especially in environments with multiple public IPs and numerous servers.
• Transparent layer 2 firewalling capable – can bridge interfaces and filter traffic between them, even allowing for an IP-less firewall (though you probably want an IP for management purposes).
• Packet normalization – Description from the pf scrub documentation – “‘Scrubbing’ is the normalization of packets so there are no ambiguities in interpretation by the ultimate destination of the packet. The scrub directive also reassembles fragmented packets, protecting some operating systems from some forms of attack, and drops TCP packets that have invalid flag combinations.”
  • Enabled in pfSense by default
  • Can disable if necessary. This option causes problems for some NFS implementations, but is safe and should be left enabled on most installations.
• Disable filter – you can turn off the firewall filter entirely if you wish to turn pfSense into a pure router.

State Table

The firewall’s state table maintains information on your open network connections. pfSense is a stateful firewall, by default all rules are stateful.

Most firewalls lack the ability to finely control your state table. pfSense has numerous features allowing granular control of your state table, thanks to the abilities of OpenBSD’s pf.

• Adjustable state table size – there are multiple production pfSense installations using several hundred thousand states. The default state table size is 10,000, but it can be increased on the fly to your desired size. Each state takes approximately 1 KB of RAM, so keep in mind memory usage when sizing your state table. Do not set it arbitrarily high.
• On a per-rule basis:
  • Limit simultaneous client connections
  • Limit states per host
  • Limit new connections per second
  • Define state timeout
  • Define state type
• State types – pfSense offers multiple options for state handling.
  • Keep state – Works with all protocols. Default for all rules.
  • Modulate state – Works only with TCP. pfSense will generate strong Initial Sequence Numbers (ISNs) on behalf of the host.
  • Synproxy state – Proxies incoming TCP connections to help protect servers from spoofed TCP SYN floods. This option includes the functionality of keep state and modulate state combined.
  • None – Do not keep any state entries for this traffic. This is very rarely desirable, but is available because it can be useful under some limited circumstances.
• State table optimization options – pf offers four options for state table optimization.
  • Normal – the default algorithm
  • High latency – Useful for high latency links, such as satellite connections. Expires idle connections later than normal.
  • Aggressive – Expires idle connections more quickly. More efficient use of hardware resources, but can drop legitimate connections.
  • Conservative – Tries to avoid dropping legitimate connections at the expense of increased memory usage and CPU utilization.

Network Address Translation (NAT)

• Port forwards including ranges and the use of multiple public IPs
• 1:1 NAT for individual IPs or entire subnets.
• Outbound NAT
  • Default settings NAT all outbound traffic to the WAN IP. In multiple WAN scenarios, the default settings NAT outbound traffic to the IP of the WAN interface being used.
  • Advanced Outbound NAT allows this default behavior to be disabled, and enables the creation of very flexible NAT (or no NAT) rules.
• NAT Reflection – in some configurations, NAT reflection is possible so services can be accessed by public IP from internal networks.

NAT Limitations

• PPTP and GRE Limitation – The state tracking code in pf for the GRE protocol can only track a single session per public IP per external server. This means if you use PPTP VPN connections, only one internal machine can connect simultaneously to a PPTP server on the Internet. A thousand machines can connect simultaneously to a thousand different PPTP servers, but only one simultaneously to a single server. The only available work around is to use multiple public IPs on your firewall, one per client, or to use multiple public IPs on the external PPTP server. This is not a problem with other types of VPN connections. A solution for this is currently under development.
• SIP Limitation – By default, all TCP and UDP traffic other than SIP and IPsec gets the source port rewritten. More information on this can be found in the static port documentation. Because this source port rewriting is how pf tracks which internal IP made the connection to the given external server, and most all SIP traffic uses the same source port, only one SIP device can connect simultaneously to a single server on the Internet. Unless your SIP devices can operate with source port rewriting (most can’t), you cannot use multiple phones with a single outside server without using a dedicated public IP per device. The sipproxd package now provides a solution for this problem in pfSense 1.2.1 and newer.
• NAT Reflection limitations – NAT reflection can only be used with port ranges less than 500 ports and cannot be used with 1:1 NAT hosts.

Redundancy

CARP from OpenBSD allows for hardware failover. Two or more firewalls can be configured as a failover group. If one interface fails on the primary or the primary goes offline entirely, the secondary becomes active. pfSense also includes configuration synchronization capabilities, so you make your configuration changes on the primary and they automatically synchronize to the secondary firewall.

pfsync ensures the firewall’s state table is replicated to all failover configured firewalls. This means your existing connections will be maintained in the case of failure, which is important to prevent network disruptions.

Limitations

• Only works with static public IPs, does not work with DHCP, PPPoE, PPTP, or BigPond type WANs (will be resolved in a future release)
• Requires a minimum of three public IP addresses (will be resolved in a future release)
• Backup firewalls are idle (active-passive failover), no active-active clustering is possible at this time.
• Failover is not instantaneous, it takes about 5 seconds to switch a backup host to master. During this time no traffic will be passed, but existing states will maintain connectivity after failover is completed. This 5 second outage during a failure isn’t even noticeable in most environments.

Load Balancing

Outbound Load Balancing

Outbound load balancing is used with multiple WAN connections to provide load balancing and failover capabilities. Traffic is directed to the desired gateway or load balancing pool on a per-firewall rule basis.

Inbound Load Balancing

Inbound load balancing is used to distribute load between multiple servers. This is commonly used with web servers, mail servers, and others. Servers that fail to respond to ping requests or TCP port connections are removed from the pool.

Limitations

• Equally distributes load between all available servers – unable to unequally distribute load between servers at this time.
• Only checks if the server responds to pings or TCP port connections. Cannot check if the server is returning valid content.

VPN

pfSense offers three options for VPN connectivity, IPsec, OpenVPN, and PPTP.

IPsec

IPsec allows connectivity with any device supporting standard IPsec. This is most commonly used for site to site connectivity to other pfSense installations, other open source firewalls (m0n0wall, etc.), and most all commercial firewall solutions (Cisco, Juniper, etc.). It can also be used for mobile client connectivity.

Limitations

• NAT-T is not supported, which means mobile clients behind NAT are not supported. This limits pfSense’s usefulness with mobile IPsec clients. OpenVPN or PPTP is a better solution.
• Only one end of an IPsec tunnel can have a dynamic IP address.
• Some of the more advanced capabilities of ipsec-tools are not yet supported, including DPD, XAuth, NAT-T, and others.

OpenVPN

OpenVPN is a flexible, powerful SSL VPN solution supporting a wide range of client operating systems. See the OpenVPN website for details on its abilities.

Limitations

• Not all of the capabilities of OpenVPN are supported yet. Support for virtually all of OpenVPN’s capabilities will be included in the next release.
• Filtering of OpenVPN traffic is not yet possible. Support for this is in 2.0.

PPTP Server

PPTP is a popular VPN option because nearly every OS has a built in PPTP client, including every Windows release since Windows 95 OSR2. See this Wikipedia article for more information on the PPTP protocol.

The pfSense PPTP Server can use a local user database, or a RADIUS server for authentication. RADIUS accounting is also supported. Firewall rules on the PPTP interface control traffic initiated by PPTP clients.

Limitations

• Because of limitations in pf NAT, when the PPTP Server is enabled, PPTP clients cannot use the same public IP for outbound PPTP connections. This means if you have only one public IP, and use the PPTP Server, PPTP clients inside your network will not work. The work around is to use a second public IP with Advanced Outbound NAT for your internal clients. See also the PPTP limitation under NAT on this page.

PPPoE Server

pfSense offers a PPPoE server. For more information on the PPPoE protocol, see this Wikipedia entry. A local user database can be used for authentication, and RADIUS authentication with optional accounting is also supported.

Reporting and Monitoring

RRD Graphs

The RRD graphs in pfSense maintain historical information on the following.

• CPU utilization
• Total throughput
• Firewall states
• Individual throughput for all interfaces
• Packets per second rates for all interfaces
• WAN interface gateway(s) ping response times
• Traffic shaper queues on systems with traffic shaping enable

Real Time Information

Historical information is important, but sometimes it’s more important to see real time information.

SVG graphs are available that show real time throughput for each interface.

For traffic shaper users, the Status -> Queues screen provides a real time display of queue usage using AJAX updated gauges.

The front page includes AJAX gauges for display of real time CPU, memory, swap and disk usage, and state table size.

Dynamic DNS

A Dynamic DNS client is included to allow you to register your public IP with a number of dynamic DNS service providers.

• DynDNS
• DHS
• DyNS
• easyDNS
• No-IP
• ODS.org
• ZoneEdit

A client is also available for RFC 2136 dynamic DNS updates, for use with DNS servers like BIND which support this means of updating.

Limitations

• Only works on primary WAN interface – multi-WAN support is available in 2.0.
• Can only update one account with a single provider. 2.0 enables the use of unlimited accounts.
• Only works when pfSense has the public IP assigned to one of its interfaces. If you have a modem that obtains your public IP and gives pfSense a private IP, the private IP will be registered with the provider. In 2.0, there is an option to determine your actual public IP and correctly register it.

Captive Portal

Captive portal allows you to force authentication, or redirection to a click through page for network access. This is commonly used on hot spot networks, but is also widely used in corporate networks for an additional layer of security on wireless or Internet access. For more information on captive portal technology in general, see the Wikipedia article on the topic. The following is a list of features in the pfSense Captive Portal.

• Maximum concurrent connections – Limit the number of connections to the portal itself per client IP. This feature prevents a denial of service from client PCs sending network traffic repeatedly without authenticating or clicking through the splash page.
• Idle timeout – Disconnect clients who are idle for more than the defined number of minutes.
• Hard timeout – Force a disconnect of all clients after the defined number of minutes.
• Logon pop up window – Option to pop up a window with a log off button.
• URL Redirection – after authenticating or clicking through the captive portal, users can be forcefully redirected to the defined URL.
• MAC filtering – by default, pfSense filters using MAC addresses. If you have a subnet behind a router on a captive portal enabled interface, every machine behind the router will be authorized after one user is authorized. MAC filtering can be disabled for these scenarios.
• Authentication options – There are three authentication options available.
  • No authentication – This means the user just clicks through your portal page without entering credentials.
  • Local user manager – A local user database can be configured and used for authentication.
  • RADIUS authentication – This is the preferred authentication method for corporate environments and ISPs. It can be used to authenticate from Microsoft Active Directory and numerous other RADIUS servers.
• RADIUS capabilities
  • Forced re-authentication
  • Able to send Accounting updates
  • RADIUS MAC authentication allows captive portal to authenticate to a RADIUS server using the client’s MAC address as the user name and password.
  • Allows configuration of redundant RADIUS servers.
• HTTP or HTTPS – The portal page can be configured to use either HTTP or HTTPS.
• Pass-through MAC and IP addresses – MAC and IP addresses can be white listed to bypass the portal. Any machines with NAT port forwards will need to be bypassed so the reply traffic does not hit the portal. You may wish to exclude some machines for other reasons.
• File Manager – This allows you to upload images for use in your portal pages.

Limitations

• Can only run on one interface simultaneously.
• “Reverse” portal, i.e. capturing traffic originating from the Internet and entering your network, is not possible.
• Only entire IP and MAC addresses can be excluded from the portal, not individual protocols and ports.
• Currently not compatible with multi-WAN rules. We hope this will be resolved in 2.0.

DHCP Server and Relay

pfSense includes both DHCP Server and Relay functionality

And More…

This is by no means a conclusive list. It will be expanded as time permits.

… Try it… Good LoadBalancing Firewall Router… Open Source for us.

Koneksi Speedy di Warnet Tetangga….

Ini membuktikan bahwa tulisan2 saya sebelumnya tidak mengada2/ dibuat2.