OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of patrick7 »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Messages - patrick7

Pages: [1]
1
19.7 Legacy Series / [SOLVED] Problems after upgrade
« on: July 17, 2019, 10:35:29 pm »
Since the upgade to 19.7 I get the following error above the firewall rule table (which is broken sometimes btw):

Warning: Invalid argument supplied for foreach() in /usr/local/opnsense/mvc/app/library/OPNsense/Firewall/Plugin.php on line 134

How to fix? ;-)

2
19.1 Legacy Series / Re: IPv6 Dual WAN / Policy Based Routing issue
« on: April 16, 2019, 11:16:44 pm »
I opened a github issue: https://github.com/opnsense/core/issues/3424

3
19.1 Legacy Series / Re: IPv6 Dual WAN / Policy Based Routing issue
« on: April 14, 2019, 10:03:50 pm »
Seems to be the same issue as described here https://forum.opnsense.org/index.php?topic=10846.msg49512#msg49512

4
General Discussion / Re: IPv6 policy routing not working
« on: April 14, 2019, 09:38:35 pm »
no ideas? :-(

5
General Discussion / IPv6 policy routing not working
« on: January 01, 2019, 08:57:47 pm »
I'm trying to set up policy routing with a he.net tunnelbroker.
The rule is matching, but the traffic is still sent to the default gateway, not to the next hop specified in the firewall rule.

Code: [Select]
pfctl -sr | grep gif0
pass in log quick on igb2_vlan104 route-to (gif0 2001:db8::1) inet6 from (igb2_vlan104:network) to ! <LocalNetworks> flags S/SA keep state label "USER_RULE: LANSALT -> Internet"

It works for IPv4 with similar config.

Is there a bug?

6
General Discussion / Re: nginx listen ip
« on: October 17, 2018, 01:11:52 pm »
You are right, there are other ways.
But still it should be possible to bind nginx to a single IP. e.g. replace the listen port with just "listen". If someone enters 443, it listens on all IPs, port 443, if you enter 1.2.3.4:443, it listens on IP 1.2.3.4, port 443.
I don't like to bind services to all IPs even if I only need the service on one IP.  For all other services I use that's possible...

7
General Discussion / Re: nginx listen ip
« on: October 16, 2018, 06:58:57 pm »
Will try, but even if it's possible to serve the webinterface, there should be a possibility to tell nginx to listen on which ip's.
Use case multiple servers, dedicated IP per website, ...... (endless list)

8
General Discussion / Re: nginx listen ip
« on: October 16, 2018, 08:11:55 am »
I see several usecases.
One is that the webinterface already listens on the same ports :-)

9
General Discussion / nginx listen ip
« on: October 15, 2018, 10:38:06 am »
Hi

Is there a possibility to tell a nginx server to listen on which IP?

Regards
Patrick

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2