Messages

1

General Discussion / Re: access to WAN gateway webUI

« on: March 11, 2024, 09:30:50 am »

What is the model of your gateway?

It's a Livebox

2

General Discussion / Re: access to WAN gateway webUI

« on: March 11, 2024, 09:29:52 am »

Since the request from PC comes from OPNsense LAN IP (not gateways LAN) the device must allow access from non-LAN IPs. Some devices restrict access to their LAN IPs, maybe there is an option for that.

but for the gateway, the request comes from opnsense which is for the LAN gateway. The gateway (192.168.2.1) sees opnsense in 192.168.2.2 (ip wan for opnsense but ip LAN for the gateway)

3

General Discussion / Re: access to WAN gateway webUI

« on: March 05, 2024, 06:53:24 pm »

Hi,
thank you for your answers. The LAN is already allowed to go out to the WAN.
On the gateway I have nothing other than DHCP and port 443 is open from a LAN address, not from internet address.
I have this route: 192.168.1.10 (PC on lan) -> 192.168.1.1 (opnsense) -> 192.168.2.2 (opnsense WAN ip) -> 192.168.2.1 (Gateway) -> Internet

I can access to internet, no problem there. The problem is that if I stop before, (the gateway) I have no feedback.
The UNBOUND service is enabled. Is there a setting that could prevent me from accessing the gateway interface or anything to do with unbound, only rule in fw?

4

General Discussion / access to WAN gateway webUI

« on: March 04, 2024, 04:50:47 pm »

Hi,
Is it possible to access the WAN gateway web page from the LAN?

If I type from my LAN: https//192.168.2.1, I cannot access it

My LAN: 192.168.1.1/24
Opnsense LAN: 192.168.1.1 (NIC #1)
Opnsense WAN: 192.168.2.2 (NIC #2)
WAN gateway: 192.168.2.1 (NIC #2)

Thanks

5

General Discussion / ntopng login problem

« on: February 26, 2024, 02:16:30 pm »

Hi,
I cannot connect to the ntopng interface: I log in with admin/admin but I get a failed login.
I ran the command redis-cli del ntopng.user.admin.password and restarted the service with no success.
I tried redis-cli set ntopng.prefs.local.auth_enabled 1: same
I tried on another browser: same
I forced the password with redis-cli set ntopng.user.admin.password admin: same

Nothing works. Each time I restarted the ntopng service.
opnsense version: 24.1.2
ntopng plugin version: 1.3
redis plugin version: 1.1_2

I searched the forums a lot but couldn't find a solution...
A little help would be nice
THANKS

6

French - Français / probleme de login ntopng

« on: February 22, 2024, 06:29:12 pm »

Bonjour,
je n'arrive pas à me connecter à l'interface de ntopng: je me logue avec admin/admin mais j'ai un login failed.
J'ai lancer la commande  redis-cli del ntopng.user.admin.password et redémarré le service et sans succès.
J'ai tenté redis-cli set ntopng.prefs.local.auth_enabled 1 : pareil
J'ai essayé sur un autre navigateur: pareil
J'ai forcé le mot de passe avec redis-cli set ntopng.user.admin.password toto : pareil

Rien ne fonctionne. A chaque fois j'ai redémarré le service ntopng.
Version de opnsense : 24.1.2
version du plugin ntopng : 1.3
version du plugin redis : 1.1_2

J'ai pas mal cherché sur les forums mais pas trouvé de solution...
Un petit coup de pouce serait sympa 
Merci

7

General Discussion / Outgoing traffic blocked after few KB...

« on: December 08, 2023, 06:02:05 pm »

Hi,

I'm having a problem with the firewall. It blocks outgoing traffic after a few KB. Example: I send a file to a remote server and it blocks after around 500KB. The connection is timed out. In the direct firewall log view, I have no error (I activated the 'conservative' parameter in 'FW optimization') but in the console I have this message which repeats:

pf : loose state match: TCP out uire: xx.xx.xx.xx:443 192.168.1.32:62382 stack:
- [10=4198815723 high=4198B11214 oin=1B26 modulator=B1 [lo=a high=1B26 uin=l no
dulator=B] R seq=4198B15722 (4198815722) ack=a len=l ackskeu=a dir
=out , ftJd

if I disable fw it works.

So there is definitely a problem with the FW rules.

I installed a new live CD installation without changing any settings except the 'fw optimization' to 'conservative'. And it's the same thing. So the problem is an original setting that I haven't been able to identify.

Can you help me please?

Thank you