Messages

Hi there, I need a bit of help configuring VLAN with Dlink 1510 managed switches

I have 2 OpnSense boxes configured in HA.
The Boxes have 4 lan ports
The ports are configured as follows:

LAN1->VLAN10 (Access Mode)

LAN2->VLAN20 (Trunk)
LAN2->VLAN21 (Trunk)

LAN3->VLAN30 (Trunk)
LAN3->VLAN31 (Trunk)

LAN4->VLAN40 (Access Mode)

Opnsense and the switches are working fine until the traffic is originated from PC connected to the switches, but when I try to access an internal network PC, opening a port with port mapping, the packets from the OPN Sense are not reaching the internal PC.

Routes and al settings are fine, I can actually reach an internal VOIP phone, configured as voice VLAN, but when I try to access a PC, the packets seems to be dropped somewhere between the OpnSense and the switch.

I did many test, and nailed the issue to one of these 2 cases:

a) opnsense is not setting the VLAN tag in the forwarded packets
b) if opnsense is properly setting the VLAN tag BUT the DLink switch is not respecting the VLAN port rules

To pinpoint this issue I need a way to inspect the packets that have leaving the opnsense towards the switch and see if they have the VLAn tag (or if they don't have it).

Is there any way to see these packets using the opnsense diagnostic tools?
Can someone point me to the proper tool?

Thanks in advance!

Hi there,
I have a Dell T110 server, which doesn't supports wake on lan, but has a separate interface (a BMC) that can be managed with ipmitool.

Since I need to start the server from crontab (daily usage) and from GUI (weekend, if needed), I did a "quack" patch to extend the wol plugin. I'm still a newbie so I'm not able to go deep inside the GUI and other opnsense customizations, and I write this post hoping that someone could integrate ipmi inside the wol plugin.

Here are the instructions:

• install ipmitool: pgk install ipmitool
• copy the files into the /root/bin folder (create it if needed)
• overwrite the original /usr/local/opnsense/service/conf/actions.d/actions_wol.conf with the attached one
• reload the services (issuing command service configd restart)

That's all.

Now when the wol command will be issued from the GUI, it will invoke our script, that, in turn, will call ipmitool if needed and wol otherwise.

Oh, and since the conf file has a description, the command will now be available also in crontab!

Regards and thanks again for opnsense,
larzeni

Dear All,
I'm a linux seasoned veteran, but a opnsense/bsd newbie, so I beg your pardon for my question.

I'd like to install opnsense (OPNsense-19.1-OpenSSL-vga-amd64.img.bz2) on an ARMORTEC J1900 Bay Trail mini PC (3 LAN, 1 WIFI).

After many attempts, I was unable to install opnsense directly on this machine, so I placed a hard disk on another pc, installed there, and then restored the hard disk in the mini pc. Hooray, now it boots ;D

... well, at boot the system hanged on the infamous "Booting" prompt, but I managed to overcome the issue using the "kern.vty=sc" parameter.

So far, so good: the system show all network interfaces, and I could connect and manage it using LAN/Web interface.

At this point, I would like to set up the wifi, but evenif the iwn interface shows in the GUI, I was not able to make it work.

My guess is that, since I installed the system on another PC, maybe the installer did not setup the firmware for the wifi card; or, it could not be provided by opnsense for the intel license issues.

Anyway, I googled around and found that the firwmare are readily available in BSD, the can be downloaded from

http://firmware.openbsd.org/firmware/6.4/iwn-firmware-5.11p1.tgz

and that I should use fw_update to download and install in the mini PC.

Now the problems:

1) I didn't find the fw_update command in opnsense.
2) I tried pkg search fw_update, but I was not able to find in the repository so I cannot install this command
3) I downloaded the firmware package and tried to install with pgk add, but it complains that there is no manifest.
4) I understand that the "reccommended" setup of opnsense is to avoid internal wifi, but since it is already there and that it is supported from bsd, I guess it should work... ;)

So, my questions are:

a) Did I broke the wifi autodetection with my installation procedure?
b) Do I need this firmware to make the wifi work, or not?
c) Should I install fw_update and, if yes, where can I find it?
d) should I install the firmware manually? How can I do this? Where should firmware files be placed? I spotted /boot/firmware and /usr/share/firmware... should I use one of them or another location?

Your faithfully :'(,
lazeni