PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001688 | PacketFence | captive portal | public | 2013-08-14 12:17 | 2014-04-03 14:01 |
| Reporter | KimHagen | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0001688: Captive portal access to common/network-access-detection.gif use lan ip. | ||||
| Description | In the Captive portal option to enter an ip for access to common/network-access-detection.gif it states that you can use your LAN ip here. This is however fire-walled (in inline mode). | ||||
| Steps To Reproduce | |||||
| Additional Information | I made a patch to iptables.pm so it works. is it safe to put this patch? --- /usr/src/iptables.pm 2013-08-14 18:01:53.000000000 +0200 +++ /usr/local/pf/lib/pf/iptables.pm 2013-08-14 18:02:26.256478576 +0200 @@ -187,6 +187,7 @@ $rules .= "-A INPUT --in-interface $dev -d $ip --jump $FW_FILTER_INPUT_INT_INLINE\n"; $rules .= "-A INPUT --in-interface $dev -d 255.255.255.255 --jump $FW_FILTER_INPUT_INT_INLINE\n"; $rules .= "-A INPUT --in-interface $dev -d $mgmt_ip --protocol tcp --match tcp --dport 443 --jump ACCEPT\n"; + $rules .= "-A INPUT --in-interface $dev -d $mgmt_ip --protocol tcp --match tcp --dport 80 --jump ACCEPT\n"; $rules .= "-A FORWARD --in-interface $dev --jump $FW_FILTER_FORWARD_INT_INLINE\n"; # nothing? something is wrong regards, Kim | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2013-08-14 12:17 | KimHagen | New Issue | |||
| There are no notes attached to this issue. |