From dd1f137ad3226c21bdce0b585bddf157a42cb62a Mon Sep 17 00:00:00 2001 From: Matias Barcenas Date: Sun, 13 Aug 2017 13:24:24 -0500 Subject: [PATCH] Added guide link --- Using-a-custom-prota.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Using-a-custom-prota.md b/Using-a-custom-prota.md index 5b9e097..3b032fd 100644 --- a/Using-a-custom-prota.md +++ b/Using-a-custom-prota.md @@ -46,7 +46,7 @@ You'll find the router's login page in the site's directory, named after your ga ![](http://imgur.com/gAmfohN.png)
## Adding fluxion support -If you're up to the task, you can make the page work with fluxion yourself by following this guide (coming up). Otherwise, you can share your web page and we'll eventually get to making it functional ourselves. +If you're up to the [simple] task, you can make the portal pages work with fluxion yourself by following [Making portals work with Fluxion](https://github.com/FluxionNetwork/fluxion/wiki/Making-a-portal-work-with-fluxion). Alternatively, you can share your web page and we'll eventually get to making it functional ourselves. ## Add it to fluxion A Portal must be stored in its own independent directory, containing all its pages and assets. A portal directory must follow the naming scheme "Brand_Language.portal" to be properly detected by fluxion. Once prepared, the portal can be moved to "fluxion/attacks/Captive Portal/sites/" for fluxion to use. \ No newline at end of file