Messages

1

24.1 Legacy Series / Re: Port Forwarding IP Cameras

« on: April 09, 2024, 05:26:32 pm »

anyone have any step by step process of what to do after plugging in the camera to igc2?  i think i go to interfaces and add igc2 for the camera and assign it the static ip that i want the camera to have.  i dont use vlans so i think from there i would then just set up the port forwarding, right?

2

24.1 Legacy Series / Re: Port Forwarding IP Cameras

« on: April 09, 2024, 05:24:08 pm »

hi there i will tell you what i do to port forward my camera so you go to firewall then nat then port forwarding then new rule  in the interface selecte your wan interface protocole is tcp/udp or choose just udp i do booth in the destination your wan adresse in destination port choose ur poort for exemple from 3030 to 3030 the destination ip is your local camera ip 192.168.1.5 for exemple the source port is 3030 name the roule and click ok dont forget to open 3030 in your modem or source of internet and this is the easyway


for more secure and advanced way you need to nat your local ip and use a virtual ip and also to point your local port to an ssl port but this need more work

hi mouad, thanks i'll give this a try this evening if i have some energy left after work.  really appreciate it

3

24.1 Legacy Series / Re: Port Forwarding IP Cameras

« on: April 08, 2024, 05:07:41 pm »

59 views and no love? really hoping this is easy for someone out there...thx

4

24.1 Legacy Series / Port Forwarding IP Cameras

« on: April 08, 2024, 03:15:47 am »

call me a dumdum if you must...really having trouble following documentation re: port forwarding.  in my instance i have an ip camera connected to igc2 port of the router.  coming from ddwrt and now fully realizing i dont know what the hell im doing i suppose...could really use some help with the 1-1 translation between ddwrt way and opnsense way of doing things.

in ddwrt i'd go to nat/qos>port fowarding, application was "camera", protocol was "both" because although my cell phone connecting via https, i couldn't connect https when trying to access within the network when home...never figured that one out years ago and gave up...anyway...source net blank, port from "30010, ip address 192.168.1.5, port to "443", and enabled was selected...bam just always worked.

i cant decipher where each of these settings above go into the opnsense>nat>port fowarding???

also sad to say im not sure of this, but i think i need to assign the ports to an interface and im afraid of messing that up too.  remember they are only plugged in and that's it.

i know i know...i could use vlan or openvpn to avoid all this but i don't want my cell phone being a part of the network even temporarily to check the ip camera feeds. thx

5

24.1 Legacy Series / Re: Recurring Crash/Restart Randomly *franco*

« on: April 07, 2024, 09:01:45 pm »

None of these messages have anything todo with the dashboard, dhclient not being able to obtain an address is one, the other ones relate to unbound (many from rc.bootup, which indicates either a reboot loop or something weird).

Maybe unbound couldn't start and tries to unmount the /var/unbound/lib directory anyway? But hard to tell with the data offered.

Best regards,

Ad

hi ad, thanks for taking a look.  what's weird is that my recurring crash reboot issues seem to happen when on the dashboard.  its still happening even now as i have the dashboard up while rummaging the wider internet like ya do.

i think dhclient might be fine to ignore here since i think its only saying that "hey im exiting because the device said it is rebooting now" and then after the reboot maybe my isp isn't responding with gateway as fast as the server would like.

as for unbound errors...im a bit miffed since i dont even use it...its not enabled on the unbound config and of course doesnt show under the services dashboard widget.

what other data can i provide that might be helpful for you?

6

24.1 Legacy Series / Re: Schedule a specific local time within Cron

« on: April 07, 2024, 08:53:19 pm »

https://crontab.guru/

thank chem, i never would've found that.  much appreciated

7

24.1 Legacy Series / Re: Schedule a specific local time within Cron

« on: April 07, 2024, 08:49:49 pm »

Reading your post again ... the crontab entries specify a point in time, not an interval! You do not enter "every 24 hours" - you enter "at the hour 1"!

OMG! You completely misunderstood how that tool works.

Hope to have made it clear 

gah!  that makes much more sense...sory it really didnt seem explained well in the documentation.  really appreciate it Patrick!

8

24.1 Legacy Series / Re: Schedule a specific local time within Cron

« on: April 07, 2024, 07:19:15 pm »

hi patrick, well i want to have my ids/ips rules and dnsbl rules update and restart at 1am for example.  i cant find a way to do that within the interface since the "hours" field wont even accept 24 as i'm currently thinking that the only way to have tried to do this was to wait until 1am tonight and then configure cron and hit save...just at a loss really

9

24.1 Legacy Series / Schedule a specific local time within Cron [solved]

« on: April 07, 2024, 06:32:14 pm »

is there some way to schedule cron jobs every night at 1am local for example?

10

24.1 Legacy Series / Updating DNSCrypt-Proxy's DNSBL Rules

« on: April 07, 2024, 06:28:11 pm »

just noticed a setting within cron's dropdown for "Download DNSCrypt-Proxy DNSBL and restart".  that indicates that these blocklists dont update unless the service is restarted.  is that entirely accurate to say?

11

24.1 Legacy Series / Recurring Crash/Restart Randomly *franco*

« on: April 07, 2024, 02:43:57 am »

running latest 24.1.5_3 with suricata ids/ips enabled and dnscrypt-proxy only. cpu usually about 10-15% and temp usually about 48-55c...storage is wide open since this is a new installation.  i seem to only have this happening when im on the dashboard with the traffic graphs up for in/out.  is there a memory leak for that widget maybe (wild guess)?

Code: [Select]

2024-04-06T20:18:31-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T20:18:30-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T20:18:26-04:00 Critical dhclient exiting.
2024-04-06T20:18:26-04:00 Error dhclient connection closed
2024-04-06T20:17:42-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T20:17:35-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T20:17:35-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:58:38-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:58:37-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:58:33-04:00 Critical dhclient exiting.
2024-04-06T19:58:33-04:00 Error dhclient connection closed
2024-04-06T19:57:43-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:57:42-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:57:42-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:24:30-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:24:29-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:24:24-04:00 Critical dhclient exiting.
2024-04-06T19:24:24-04:00 Error dhclient connection closed
2024-04-06T19:23:34-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:23:33-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T19:23:33-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T18:51:59-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T18:51:59-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T18:51:52-04:00 Critical dhclient exiting.
2024-04-06T18:51:52-04:00 Error dhclient connection closed
2024-04-06T18:51:02-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T18:51:01-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T18:51:01-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T18:50:12-04:00 Critical dhclient exiting.
2024-04-06T18:50:12-04:00 Error dhclient connection closed
2024-04-06T17:12:03-04:00 Error opnsense /usr/local/sbin/pluginctl: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T17:12:03-04:00 Error opnsense /usr/local/sbin/pluginctl: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:42:45-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:41:38-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:41:38-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:41:34-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:41:33-04:00 Error opnsense /usr/local/etc/rc.linkup: ROUTING: not a valid wan interface gateway address: 'missing'
2024-04-06T15:41:33-04:00 Critical dhclient exiting.
2024-04-06T15:41:33-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/dhclient -c '/var/etc/dhclient_wan.conf' -p '/var/run/dhclient.igc1.pid' 'igc1'' returned exit code '11', the output was 'dhclient 58293 - - dhclient-script: Reason PREINIT on igc1 executing DHCPREQUEST on igc1 to 255.255.255.255 port 67 DHCPREQUEST on igc1 to 255.255.255.255 port 67 DHCPNAK from 192.168.100.1 DHCPDISCOVER on igc1 to 255.255.255.255 port 67 interval 2 DHCPOFFER from 192.168.100.1 igc1 link state up -> down DHCPREQUEST on igc1 to 255.255.255.255 port 67 DHCPREQUEST on igc1 to 255.255.255.255 port 67 igc1 link state down -> up DHCPDISCOVER on igc1 to 255.255.255.255 port 67 interval 2 DHCPDISCOVER on igc1 to 255.255.255.255 port 67 interval 2 DHCPOFFER from 192.168.100.1'
2024-04-06T15:41:33-04:00 Error dhclient connection closed
2024-04-06T15:41:22-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '77560''(pid:/var/run/dhclient.igc1.pid) returned exit code '1', the output was 'kill: 77560: No such process'
2024-04-06T15:40:34-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:40:34-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:40:34-04:00 Error opnsense /usr/local/etc/rc.bootup: ROUTING: not a valid wan interface gateway address: 'missing'
2024-04-06T15:40:34-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/dhclient -c '/var/etc/dhclient_wan.conf' -p '/var/run/dhclient.igc1.pid' 'igc1'' returned exit code '1', the output was 'igc1: no link .............. giving up'
2024-04-06T15:30:10-04:00 Critical dhclient exiting.
2024-04-06T15:30:10-04:00 Error dhclient connection closed
2024-04-06T15:20:33-04:00 Error opnsense /usr/local/etc/rc.linkup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:20:32-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:20:27-04:00 Critical dhclient exiting.
2024-04-06T15:20:27-04:00 Error dhclient connection closed
2024-04-06T15:19:37-04:00 Error opnsense /usr/local/etc/rc.newwanip: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:19:36-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:19:36-04:00 Error opnsense /usr/local/etc/rc.bootup: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
2024-04-06T15:18:47-04:00 Critical dhclient exiting.
2024-04-06T15:18:47-04:00 Error dhclient connection closed
2024-04-06T15:16:14-04:00 Error config /system_advanced_admin.php: The command '/sbin/umount '/var/unbound/lib'' returned exit code '1', the output was 'umount: /var/unbound/lib: not a file system root directory'
hope this crash when viewing the traffic graphs and this unbound error is fixed soon as its a known problem around the forums...i dont even use it since i use dnscrypt-proxy.