Configuring NoDogSplash
Posted: Wed Jan 22, 2014 3:55 am
I have a TL-WDR4300v1 running Gargoyle 1.5.11 which Ill call R2. This router is set up as a Client+AP using another router R1 (WRT54GS dd-wrt) as the gateway.
[Gateway R1] 192.168.1.1 -->192.168.1.6 [Client+AP R2] 192.168.2.1 --> Lan 192.168.2.0/24
I installed nodogsplash with no problems. But the only way I can access the splash page is by going directly to 192.168.2.1. If I do this I can authenticate just fine and continue onto other sites.
If I instead try to directly go to, say http://www.google.com, the splash page never comes up and the page just hangs. I understand that the page will hang because I am not authenticated.
If I try to ping http://www.google.com before I am authenticated the request times out as expected. If I then try to ping http://www.google.com after I authenticate the request comes back as Destination Port Unreachable as opposed to simply timing out.
I have tried manually configuring nodosplash to use br-lan (192.168.4.1) as the GatewayInterface and br-wan(192.168.1.6) as the ExternalInterface as defined in nodogsplash.conf. (http://wiki.openwrt.org/doc/howto/wirel ... odogsplash)
I have also tried configuring the GatewayAddress as both 192.168.2.1 and 192.168.1.6 with no change in outcome.
NoDogSplash uses a web server to listen to the GatewayAddress on port 2050 for http GET requests. Looking at debug logs it seems to me that when I go to any other IP besides 192.168.2.1 this web server cannot see the traffic, it is bypassing the GatewayAddress.
I dont know if the problem is in how gargoyle does NAT or a conflict between iptables in nodogspalsh and gargoyle or what.
I have done a lot or searching and trying other solutions and now Im stumped.
Thanks for any help.
[Gateway R1] 192.168.1.1 -->192.168.1.6 [Client+AP R2] 192.168.2.1 --> Lan 192.168.2.0/24
I installed nodogsplash with no problems. But the only way I can access the splash page is by going directly to 192.168.2.1. If I do this I can authenticate just fine and continue onto other sites.
If I instead try to directly go to, say http://www.google.com, the splash page never comes up and the page just hangs. I understand that the page will hang because I am not authenticated.
If I try to ping http://www.google.com before I am authenticated the request times out as expected. If I then try to ping http://www.google.com after I authenticate the request comes back as Destination Port Unreachable as opposed to simply timing out.
I have tried manually configuring nodosplash to use br-lan (192.168.4.1) as the GatewayInterface and br-wan(192.168.1.6) as the ExternalInterface as defined in nodogsplash.conf. (http://wiki.openwrt.org/doc/howto/wirel ... odogsplash)
I have also tried configuring the GatewayAddress as both 192.168.2.1 and 192.168.1.6 with no change in outcome.
NoDogSplash uses a web server to listen to the GatewayAddress on port 2050 for http GET requests. Looking at debug logs it seems to me that when I go to any other IP besides 192.168.2.1 this web server cannot see the traffic, it is bypassing the GatewayAddress.
I dont know if the problem is in how gargoyle does NAT or a conflict between iptables in nodogspalsh and gargoyle or what.
I have done a lot or searching and trying other solutions and now Im stumped.
Thanks for any help.