Menu

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.

Show posts Menu

Messages - jw64

#1
How can we know Zenarmore is ready for a new release so we can upgrade safely?
#2

Hi, when I click "Check for updates" button in WebUI, I found a segmentation fault error. I can reproduce the error by running the "pkg update" command manually. Any suggestion on how to look for source of problems and fix these? Thanks.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.7.11_2 (amd64) at Tue Jan 14 21:56:42 EST 2025
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 861 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ... done
Processing entries: ....... done
SunnyValley repository update completed. 66 packages processed.
All repositories are up to date.
Child process pid=86255 terminated abnormally: Segmentation fault
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (10 candidates): .......... done
Processing candidates (10 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
#3
24.7, 24.10 Legacy Series / cannot find wol service
January 02, 2025, 05:56:33 AM
Hi, I am on the latest version of OPNsense 24.8.11_2. However, I cannot find os-wol in the UI System->Firmware->Plugins. I tried to install wol from command line but got a segmentation fault. Following is the screen output of my Opnsense update operation and pkg install output. Any suggestion what should I do? Thanks in advance.

Jim


***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 24.7.11_2 (amd64) at Wed Jan  1 23:50:02 EST 2025
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 861 packages processed.
Updating SunnyValley repository catalogue...
Waiting for another process to update repository SunnyValley
All repositories are up to date.
Child process pid=67745 terminated abnormally: Segmentation fault
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking for upgrades (11 candidates): .......... done
Processing candidates (11 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

root #  pkg install wol
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
   wol: 0.7.1_5 [OPNsense]

Number of packages to be installed: 1

24 KiB to be downloaded.

Proceed with this action? [y/N]: y
[1/1] Fetching wol-0.7.1_5.pkg: 100%   24 KiB  24.9kB/s    00:01   
Checking integrity... done (0 conflicting)
[1/1] Installing wol-0.7.1_5...
[1/1] Extracting wol-0.7.1_5: 100%
Child process pid=4995 terminated abnormally: Segmentation fault
#4
I am trying to set up a vlan in my opnsense box.

Following the instruction in https://www.zenarmor.com/docs/network-security-tutorials/how-to-configure-vlan-on-opnsense, I created a VLAN1 using a physical lan port LAN1 as its parent.  The LAN1 port static address is 192.168.3.1, and VLAN1 is 192.168.100.1. The VLAN1 interface is assigned to a logical interface and enabled. Both have DHCP enabled in their respective subnets. For testing purpose, I created firewall rules to allow VLAN1 to reach any network. I have a laptop physically linked to the LAN1 port via ethernet cable.  When I put the laptop in the LAN1 subset (by using a static IP address 192.168.3.10), it works normally.  However, when I change the laptop to the VLAN1 subset (by using a static IP address 192.168.100.10), it cannot reach internet, and no other devices in my home net can reach that laptop.  Any clue how to debug and correct the problem? Thanks.

Jim
#5
Thank for the information. I was using single PC for configuring and testing the firewall box.
I think my problems are solved now.
#6
I think I found the issue. When I was testing if I can reach the ETH1 subnet from ETH2, I moved the network cable from ETH1 to ETH2, and tried to reach the web portal 192.168.1.1. That doesn't work.  However, if I connect another machine to ETH1, then I can reach 192.168.1.1 from ETH2 as expected.

So it looks that I may not have problem in the network setup. The issue is that I could not reach web portal 192.168.1.1 when ETH1 is not connected to an active machine. Is this normal? Is there any configuration change that can make the web portal 192.168.1.1 alway available?
#7
File wall rules for ETH4 (ETH5 is similar). ETH1 has one additional anti-lockout rule in the automatically generated rules.
#8
@netnut. Thanks for your reply. Please see my firewall rules in the attached images and let me know what other configuration information should be examed.
#9
Hi,

I am running an opnsense machine with 6 ports. My setup is as the following:
    ETH0: WAN
    ETH1: LAN, 192.168.1.x/24
    ETH2: LAN, 192.168.2.x/24
    ETH3: LAN, 192.168.3.x/24
    ETH4: LAN, 192.168.4.x/24, this is for IoT devices
    ETH5: LAN, 192.168.5.x/24, this is for guest access
Each of the LAN subnets ETH1-ETH5 has its own gateway (192.168.x.1) and corresponding DHCP range.

I want ETH4 and ETH5 can access internet but not other subsets. I set up these two as guest nets using instructions in https://docs.opnsense.org/manual/how-tos/guestnet.html. These worked as expected.

I want ETH1/ETH2/ETH3 can access internet and all other subnets, so I created firewall rules to allow any IP traffic from these subnets to any destination. While traffic can reach internet, it doesn't work to reach nodes in other subnets, e.g., a node in ETH2 cannot reach any node in ETH1. How to change setup to fix this problem? I know I can create a bridge for ETH1/ETH2/ETH3 but I read that bridging in opnsense is not efficient and not suitable for heavy traffics so I'd like to get away from bridge if possible.

Thanks.