It would also help if you could go to the filter logs and search for the WAN Gateway IP and click "x" to reveal which rule blocks your traffic. Something is different about your setup that is being rejected by our firewall/filter setup.

if I curl from the system I normally use to access modem and internet, I get the page back.if i http the modem, I get the name of the page at the top, but no page, ie blank, however I can see the modem pages source in the debug panes, and there are no errors detected.i have also tried this on other systems, which when using other software (no not pfSense), its worked perfectly.i did try pfSense in the past, and wasted lots of time following the instructions re accessing modem, adding interfaces, to no avail.

There is no evidence in the filter log of any access to the modem from the various systems.Connection directly to the modem, no problem.

Proxy and IDS are currently disabled.

Confused

Aimee

PS just tried to access the modem on the iPad, eventually, I get the page, but just text, and hyperlinks.

The modem pages are displayed, eventually, ie after minutes not seconds.The logs show nothing that appears to relate to this issue (wan-lan igmp, lan to wan 5353)The modem is straight connection via ethernet, 100 mbs.The hardware employed is the same.The opnSense setup is straight out of the box.Access to the internet is fine.The problem occurs with pfSense also.The problem does not occur with Sophos UTM9, or an Asus RTN16. (Both linux based)Proxy is not being used.The modem is an adsl from Sky Broadband, model SR102.

It is most likely one of the lines in /tmp/rules.debug (pf itself), but it's hard to do this without having a setup to test. Disabling pf will make WAN inaccessible to LAN, editing by hand would be finding the needle in the hay stack.

Can you packet capture the access for us as seen on the OPNsense box (WAN and LAN separately)?