News
:
This forum is now permanently frozen.
m0n0wall Forum
>
m0n0wall Support (English)
>
General Questions
Topic: Captive Portal - WWW connection doesn't work
Pages: [
1
]
Topic: Captive Portal - WWW connection doesn't work (Read 1692 times)
Captive Portal - WWW connection doesn't work
« on: October 06, 2008, 20:41:27 »
rsojer
Posts: 2
Hello,
I'm using m0n0wall 1.3b14 with LAN, static WAN and a WLAN network. I've configured the whole wall I think correctly and I've activated the captive portal. When I try to connect to a website the portal site appears correctly and even the login with username/password or voucher seems to be working. But then no website appears and the browser seems to run in a timeout after a time and a IE error page appears that no connection is available.
I checked the logfiles and the connections. the internet connection seems to be ok because from the console of the server I'm able to ping everything by IP and name. Internet from the LAN interface is working too. A log entry of the WLAN interface appears e.g.
Source IP: 192.168.100.199 (WLAN-client)
Source Port: 8245
Destination IP: 66.249.93.104 (google.at)
Destination Port: 80
Action: allowed
Everything seems to be ok - BUT the site doesn't appear at the client...
Can anybody help me with this issue?
Kind Regards,
rsojer
Re: Captive Portal - WWW connection doesn't work
« Reply #1 on: November 03, 2008, 17:38:45 »
ocr14a
Posts: 15
I'm having this same problem (I think).
i.e.
http://forums.untangle.com/showthread.php?t=5653
Did you get it resolved?
steven
Re: Captive Portal - WWW connection doesn't work
« Reply #2 on: November 03, 2008, 22:03:53 »
ocr14a
Posts: 15
um, well...maybe not.....I'm not using Captive Portal at all.
Sorry, I didn't know that was one of the avaialble options before (somehow, I guess I thought it was just a reference to the fact that web browsing wasn't working).
Oops.
Re: Captive Portal - WWW connection doesn't work
« Reply #3 on: November 04, 2008, 08:03:25 »
rsojer
Posts: 2
I solved my problem now - well, I did a workaround. I had the option "Enable per-user bandwidth restriction" activated within the captive portal and after I unchecked/deactivate this option erverything was working well...
Best regards,
Reinhard
Pages: [
1
]