Topics

Hi, I have a dsl internet connection with a fritzbox modem in bridge mode, so that my opnsense handles the dsl login.
I want to have access to the "modem" gui from my lan interface and found the following manual:
https://www.netgate.com/docs/pfsense/interfaces/accessing-modem-from-inside-firewall.html

The fritzbox has an emergency ip 169.254.1.1/16. So i setup a new opt interface on the same physical interface as my pppoe connection with ip 169.254.1.2/16.
And also switches from automatic outbound nat to hybrid nat (I also tried manual nat, but it doesn´t work either) and created the rule as in the manuel.

I can ping the modem from opnsense, but any connection from my lan is not possible.

Anyone with a working configuration for this and can help me?

Hi,

I am using OPNSense with a FritzBox as a DSL Modem for WAN connection.
I had connected the Fritzbox to WAN-Side on OPNSense and also connected to my internal LAN network, so I was able to login to the Fritzbox to watch the DSL-Status.

But I don´t want the Fritzbox to "see" my internal network and its devices, so I have created an vlan interface on opnsense and switch etc. for the fritzbox.

I am able to ping the Fritzbox from the vlan interface on my opnsense (interface / diagnostics) but i am not able to access it from my lan. A rule for allowing access from lan to everywhere exists.
Also a ping from my lan to the opnsense adress on the vlan-interface works.
I think the FB is blocking access to it from outside its own network.

So I am trying to implement nat or something to fake the ip accessing the fritzbox, so it looks like its coming from fritzbox internal network.

I tried port forwarding on LAN with a fake-ip to the real-ip but no success so far.

Someone got a solution for me ;)

Sorry for bad english ;)

Regards,

Dennis

Hi,

I have upgraded to 17.4 yesterday and have some strange bahavior now.
Upgrade itself was working normal without any errors, exept ids was not strted and I had to reboot.

I use simple nat with 1 wan dsl connection.

After the update it seems like after 15 minutes all _new_ connections going to wan are blocked.

I can ping for e.g. 8.8.8.8 on my pc without any problems, even after 15 minutes when I ping permanently.
But when I try to do simple web surfing after these 15 minutes no connection is possible. Even from the opnsense itself I am not able to ping 8.8.8.8 for e.g.
In the dashboard I can see, that the dsl connection is still up and running. Even the ping from my pc I started directly after rebooting is still working. But any new connections do not work.

When I try to reconnect the wan dsl connectionit will not come up again.

To solve the problems I have to restart the opnsense.

After restart it takes a long time before the dsl connection is up again (20 to 30 tries in log file), but then everything is working again for around 15 minutes.

My hardware is an APU 1 board (realtek cards).

Anyone got an idea what is going wrong?

For me it looks like the firewall is blocking connections after these ~15 minutes, I can´t find any problems in other logs (pppoe, system hardware etc.)

regards,

Dennis

Hi everyone,

I am a long user of pfsense in my home enviroment, but since pf was a little bitchy sometimes when updating and I wanted to try ips I switches over to opnsense 2 weeks ago.
System feels much faster, and most things I was able so setup without problems.

But one feature I am missing is to forward mdns from interface to interface.

I have nothing special here, just a lan network and some vlans for wifi - control, internal wifi and guest wifi.

So my airplay receiver for example is not in the same network as my smartphone. On pf I just installed avahi for that and most of the time it workes without problems, sometimed I had to restart the service when the devices were not able to "see" them anymore ;)

I can´t find avahi in the plugins :( is there a different package avaiable for that or how can I implement forwarding mdns?

Regards

Dennis

Chage: Mark as solved