Changes between Version 29 and Version 30 of FAQ
- Timestamp:
- 10/31/07 18:16:50 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQ
v29 v30 29 29 == Q: What are the main differences between it and !NoCat ? == 30 30 A: On the client side, it's smaller, has far fewer dependencies, and runs well on embedded devices. 31 On the auth server side, it's more customizable, and is geared towards capitalizing the infrastructure for the purposes of building portals and communities. 31 On the auth server side, it's more customizable, and is geared towards capitalizing the infrastructure for the purposes of building portals and communities. On the practical side, NoCat opens a pop-up window after the user gets authenticated, to keep alive the connection. Wifidog, doesn't. 32 32 33 33 == Q: How does it work ? == … … 41 41 A: The client runs on any Linux machine that has a working netfilter+iptables installation. The auth server runs on any PHP-enabled web server. 42 42 43 == Q: Can I install and run WifiDog auth server and WifiDog gateway on the same Linux box ? == 44 A: Yes. 45 43 46 == Q: Does my system have to have a wireless card to use wifidog or just a wireless router? == 44 47 A: You don't need a wireless card directly in the machine running the gateway (client). But every wireless (or wired) clients the gateway is to manage must be bridged at layer 2 to the ethernet interface wifidog is configured to gate (GatewayInterface). In practice, it means that the wireless router must be used as a pure access point by connecting a LAN port (NOT the WAN port) to the interface on the machine running the gateway. 48 49 == Q: Do I need to use wireless access points or can I use wireless routers with WifiDog ? == 50 A: Some wireless routers do nat, which replaces the client's MAC address with the one from the wireless router. If this is the case, WifiDog's authentication will not work, as it relies on MAC addresses to allow/disallow access. 45 51 46 52 == Q: Can I write my own client ? ==