OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of Pedro »
  • Show Posts »
  • Topics
  • 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

Topics - Pedro

Pages: [1]
1
19.7 Legacy Series / Issues communicating between VLANs
« on: September 23, 2019, 04:00:54 pm »
Hi all,

Finally got around to updating to 19.7 (was on 18.7 still...I know, I know...).

Anyway, after the update, I stopped being able to communicate properly between VLANs. From what I can tell, everything seems to be properly configured (it should be because it was working before the upgrade), but since the upgrade, I've stopped being able to communicate between VLANs.

I'm at the stage of pulling my hair out because everything seems ok (from my limited knowledge of this stuff). At this stage, I'm not sure what more to troubleshoot and would appreciate some pointers.

The only thing I can think of that has significantly changed is that now by default, the FW seems to have active the first match option, when before I don't recall it being there.

Could this (and rule order) be somehow messing up communication between VLANs.

2
16.1 Legacy Series / WAN with DHCP loosing internet access.
« on: April 22, 2016, 04:00:59 pm »
Hi all,

I finally managed to convince the higher-ups to implement OPNsense. Initially, all seemed to be working ok in the testing, but now that I've moved into production (setup is slightly different) we occasionally loose internet access. Everything seems to be working ok, but OPNsense shows the gateway as being down and we have no internet. I've yet to find a pattern and usually the only way I get internet access back is by rebooting OPNsense. Even a release/renew of the DHCP lease for WAN doesn't solve the problem.

Being rather new to OPNsense and FreeBSD, I'm at a loss as to what further I can do to troubleshoot this issue and would appreciate any help/guidance in solving this.

Specs
OPNsense 16.1.11_1-i386
FreeBSD 10.2-RELEASE-p14
LibreSSL 2.2.6
WAN using DHCP with gateway monitoring.


3
16.1 Legacy Series / DNS Overides and subdomains
« on: March 16, 2016, 07:12:24 pm »
Hi All,

I'm rather new to opnsense and firewalls in general. I have however been tasked with migrating from an aging Zentyal install to something more secure and focused (we don't need all the bells and whistles Zentyal offers).

I've managed to get things setup and working normally, and now I'm trying to mirror what we currently have, and this is where I've hit a snag.

We currently have a couple realms or domains in Zentyal, something along the lines of:

Code: [Select]
company.lan => 10.10.200.100-200/16
dev.company.lan => 10.10.210.100-200/16

company.lan is a dhcp pool whereas dev.company.lan are statically assigned IPs.

I've created a static lease for vm1.dev.company.lan with 10.10.210.101 and added a host override in DNS Resolver with vm1.dev.company.lan and the ip. However, whenever I try and do a lookup from another machine in company.lan, I get:

vm1.company.lan has address 10.10.210.101 and not vm1.dev.company.lan

I hope this makes sense to some and hopefully you'll be able to help.

Cheers,
P

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