PacketFence - BTS - PacketFence |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001571 | PacketFence | captive portal | public | 2012-10-18 12:04 | 2015-02-13 15:35 |
|
| Reporter | sadai | |
| Assigned To | fgaudreault | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | 3.5.1 | |
| Target Version | investigate | Fixed in Version | | |
| fixed in git revision | |
| fixed in mtn revision | |
|
| Summary | 0001571: iptables not getting updated after login / self-registration until dhcp renew / reconnect |
| Description | Setup: Debian 6.0.6, packetfence 3.5.1, all latest patches, pfdhcplistener patch from another bug report, inline mode, controller based wireless network
I'm trying to get the activation of network access working after registering via the captive portal. But it keeps me getting the "Sorry" page, until I request a new ip via "ipconfig /renew" on a windows system. On all other systems I reconnect to the wireless network and it works but thats no solution you can offer to customers.
I attached 2 files with settings from "iptables-save > <file>" directly after registration (when it loads the "Sorry" page) and after the dhcp renew / wireless reconnect. You can see for example by issuing a vimdiff of these two files, that the mac address is added afterwards.
Please also have a look at the file packetfence.log
Thanks in advance. |
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  iptables.tar.gz (2,034) 2012-10-18 12:04
https://www.packetfence.org/bugs/file_download.php?file_id=167&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2012-10-18 12:04 | sadai | New Issue | |
| 2012-10-18 12:04 | sadai | File Added: iptables.tar.gz | |
| 2012-10-18 13:35 | fgaudreault | Note Added: 0003119 | |
| 2012-10-19 03:28 | sadai | Note Added: 0003120 | |
| 2012-10-19 08:42 | fgaudreault | Note Added: 0003121 | |
| 2012-10-19 10:55 | fgaudreault | Assigned To | => fgaudreault |
| 2012-10-19 10:55 | fgaudreault | Status | new => assigned |
| 2012-10-19 10:55 | fgaudreault | Target Version | => investigate |
| 2012-10-26 16:20 | fgaudreault | Note Added: 0003250 | |
| 2012-11-13 11:36 | sadai | Note Added: 0003277 | |
| 2015-02-13 15:35 | lmunro | Note Added: 0003735 | |
| 2015-02-13 15:35 | lmunro | Status | assigned => closed |
|
Notes |
|
|
(0003119)
|
|
fgaudreault
|
|
2012-10-18 13:35
|
|
|
Are you using the ipset feature? |
|
|
|
(0003120)
|
|
sadai
|
|
2012-10-19 03:28
|
|
|
|
|
(0003121)
|
|
fgaudreault
|
|
2012-10-19 08:42
|
|
|
There is a patch available to add the feature, but I would suggest you wait a bit more for the 3.6 release (should be available next week). |
|
|
|
(0003250)
|
|
fgaudreault
|
|
2012-10-26 16:20
|
|
|
3.6 is out now. Can you try and let me know the result? |
|
|
|
(0003277)
|
|
sadai
|
|
2012-11-13 11:36
|
|
Sorry for the delay, it works better now.
Sometimes I still have to reconnect, but the
network detection and redirection doesn't work
at all.
There is also a new issue, the client gets
unregistered after about 10 minutes whether
there is no such timeout configured.
I have started a discussion on the mailing list
"no redirection after authentication on captive portal" |
|
|
|
(0003735)
|
|
lmunro
|
|
2015-02-13 15:35
|
|
|