Topics

1

General Discussion / Connect my NVR device to noip endpoint

« on: September 20, 2024, 09:23:29 pm »

Hi all,
Warning! Non-expert here!

BTW I am using 24.7_1

I think I have configured the Noip end correctly.  It reflects my WAN ISP DHCP address so I like to believe it is right. 
Not sure how to test it?
Also, I am experimenting, so I am using a free account.   If this works, I will get a paid for account.

The way I see it, is that the DNS endpoint provided by Noip could be accessed by http//:XXXX.ddns.net. I do not have a cert yet, so it would be HTTP://   [Note: I would be using a proper domain reg. and add to noip, as per the service provided]

To get to the device (NVR) I need to define the mapping from the the the firewall to the device - thus a connection is made between the device and the firewall, and then it should be automatic to connect to the endpoint. 
The result being that I will be able to, via a browser, connect to the device and log in.

Assuming the device is on 192.168.40.1 (and OPNSense is 192.168.1.1) I am looking for advice as to where to provide the routing.   I am going to assume a firewall rule?

In the LAN pool?
Bidirectional I figure, as the device needs to validate itself ti the DDNS and secondly, allow for when I attempt to connect via http//:XXXX.ddns.net

Any guidance appreciated.

I found https://www.youtube.com/watch?v=i546YF91dHk to be somewhat useful but incomplete for 24.7_1

I found this guide (https://www.cctvcameraworld.com/port-forwarding-for-dvr-and-nvr/) and have enabled ports 80, 554, 37777 and 37778 but it still does not come through.
I have asked NVR manufacturer support for port recommendations to confirm these.

2

24.1 Legacy Series / Re: Leveraging the 24.1.3 release [ Closed ]

« on: March 12, 2024, 05:08:27 pm »

Hi,
Warning: Noobie here

I have been a recent Ubiquiti user re router and UniFi. 
The EdgeRouter has become redundant, and I have moved to OPNSense on a Mac Mini.  Works great and seems stable.  I also attach the UniFi onto the network, and it is transparent and works, first time! 

However, I want to implement vlans/QoS/etc. and my current Netgear smartswitch is NOT suitable (it is to be fair rather old).

The replacement must have at least 8 port of 1Gb or higher. Not fussed re POE as I have been using injectors.

Looking for suggestions please - other than ridiculous overprice switches from "some" vendors.
Any folks with experiences?

3

24.1 Legacy Series / VLAN issues where MACs are not sticky [ SOLVED ]

« on: March 09, 2024, 10:25:43 pm »

Hi,
Warning: Noobie here and learning.

I have 24.1.3_1 running, and it is petty good    (Been a learning curve!)

I have a simple arrangement of ISP---- > OPNSense -----> netgear GS108T smart switch-----> with 1x Macminis and 1 PC

At the moment, everything is running as 192.168.1.x space
I have defined a number of VLANS.
Now I have taken the PC and assigned it a 192.168.20.x IP in the DHCP definition for the VLAN (i.e. moved PC to VLAN USERS)
I have included that the Firewall has a rule that allows access to the internet from the VLAN

Problem is, the PC cannot connect to the internet via the VLAN; (when the IP is 192.168.20.x) and defers back to an IP 192.168.1.y (I can manually force the IP to 192.168.20.x

So, can somebody confirm that I have to create VLAN definition in switch to enable PC to "bind" to VLAN or not? So that the PC can access the internet)

The corollary is that if I only had a simple switch (and not a smart switch) then I cannot have VLANs.

Is this correct?

4

24.1 Legacy Series / DNSmasq DNS vs Unbound DNS [ Solved ]

« on: March 07, 2024, 04:41:33 pm »

Hi,

noobie on networks here.
v24.1.3_1
Domestic deployment, macmini ---- > switch ------ > opnsense (PC with 1 buitin nic and 1 pci nic)  --- > ISP modem ---- > www
The docs are confusing wrt whether the dnsmasq DNS  vs. Unbound DNS.   
I take it that only one is to be configured.  Can someone confirm this please?

I figure both are not needed as both seem to want to use port 53 and a conflict arises. I change one to port 853 but I see no effect.

Advice please?

5

24.1 Legacy Series / OPNsense 24.1.2_1 very slow on simple config [ Solved - Updated]

« on: March 01, 2024, 03:37:50 pm »

Hi,
noob here.  I have had to do much reading and watch y/t as I am not an infra person.

I have managed to configure OPNsense 24.1.2_1 and it is up and running

I am running it in bare metal being:
Macmini i5 (2012)
8MB RAM
540 SSD
std eth port
and have additional eth adapter port dongle hanging off DP1.2

The config is such that:
the std eth port is my WAN
the DP1.2 eth is the LAN   (Enabled DHCP Range 192.168.1.1 – 192.168.1.250)
no separate MGT port (although I have a USB eth adapter – this will be later)

I have defined a VLAN01 (Range 192.168.10.10 – 192.168.1.100) for untrusted and allowed DHCP on this i/f

I have defined all the MAC addresses of all the devices on the LAN (including eth port 192.168.1.1) So “Deny unknown clients”

I can get clients to plug in and access the Web no problem   BUT…..
I have 1Gb Virgin connection and when I test it I only get max 5Mb/3Mb. 

Obviously, I have a connection but slow!

Any advice to get this to speed?

6

Hardware and Performance / Installing proxmox and opnsense on MacMini 2012 (Project) - problems

« on: May 19, 2023, 06:20:13 pm »

Hi all,
I have been trying to get proxmox and OPNSense to work together on a mac mini 2012.  Seeking some advice.

My Virgin Media 1G router is set in bridge mode and it auto sets to 192.168.100.1 (I cannot change this at all)

I can define the virtual bridges etc for the 2 ethernet ports I have connected virbr0 (WAN 192.168.100.1) and virbr1 (LAN - 192.168.100.2).

I read somewhere that I may have to have 3 eth ports (1 for management) and  2 covering WAN and LAN routes for OPNSense.

When I config the ip addresses virbr 0/1 for WAN and LAN routes for OPNSense I cannot get back via port 192.168.100.2 (even though the reboot of Proxmox states 192.168.100.2:8006

Any ideas?
Maybe a no go?

Maybe I can you assign 2x ip addresses to the LAN eth?
I want this to be my virtual router (with DHCP etc) and get rid of my old router