Messages

For traceability, the previously mentioned pull request[1] has been closed in favour of: https://github.com/opnsense/core/issues/5297


[1]: https://github.com/opnsense/core/pull/4774

Thanks both for replying and getting this topic some momentum again.
For me it is quite a thingy since I am glad I got it working now, but only one last step is required to completely solve it for me. I understand that there is some discussion required where to best fit the button and/or some other topics - but until then, OPNsense does not work (sufficiently) for me...

Maybe approaching from another course, to at least fix it 'on my machine': is there a possibility for me to persist the promisc mode, so that after a reboot, my internet actually works again .. without having to figure out what I needed to do to get it going again? And for now I am totally fine if that would mean that I cannot change my VLAN/NIC config(s).

Hope to hear from you!
Mikki

Hello Maurice,

Can I be of help to get the pull request more in shape to get it merged?

Thanks in advance,
Mikki

Hello Maurice,

I would say that to allow to set promiscuous mode manually would be best, since it might introduce unexpected behaviour if it is set automatically, as Ad also stated.
I am not entirely sure how this exactly works, but thanks to a friend of mine, we were able to figure out that setting promiscuous actually fixed it. Strangely enough this worked somewhat easier when I had pfSense installed. So I am not entirely sure how the OPNsense code base differs from pfSense on this particular topic.

If more feedback, investigation or further case description from my side is helpful, please let me know!

Thanks for your effort in helping me!
Mikki

Hello Maurice,

Bit later than expected, however I do have feedback :-)
After some searching where to find your patch and where to apply it to, I was able to do so, but it did not yet give me the expected result. After some more trying, rebooting, failing, digging, Googling and so on, I found out that I seem to be required to set `promisc` on the vlan interface too.

So, in fact, your patch works perfectly for the MAC-address change; however I am now still a bit stuck for the promisc part. Is there already a way I could follow to make that work, too?

Thanks for your effort so far, and hope to hear from you!
Mikki

Hello Maurice,

Thanks for your reply and your effort!
Since I work from home, and I require an OK from my userbase (aka my wife), I will try to apply the patch on my machine as soon as possible; preferably before end of this weekend.

Would you maybe also be able to point me to some documentation or anything related to the possibility to 'permanently' configure interface-related stuff (e.g. promisc mode) on OS-level, rather than from the UI? Permanently meaning, in a file, that is not overwritten before or after a reboot or upgrade :) Some sort of include file...?

I hope to quickly get feedback for you!
Mikki

Hello elcocoloco,

If I do that in the UI or on console, depending on which I set first, will get an IP and the other won't. That is how this ISP works(/seem to work)... The original modem/router does exactly the same: it has 1 physical NIC for internet, but it has 2 MAC addresses, one for internet and one for IPTV.

-sorry for the bump-

[both]

Hi all,

I am dumping my question here, since it seems to be the right location... I suppose. I have tried searching this forum for my question, but could not find it. So if there is any similar question - please let me know!

First my setup: I got OPNsense (21.1) on a dedicated machine with one on-board ethernet interface and I got a PCI-card with 4 ethernet ports: Broadcom Inc NetXtreme BCM5719 Gigabit Ethernet PCIe. (according to `pciconf -l -v`).

I got glass fiber from Telfort (daughter organization of the Dutch ISP KPN), via a fiber to ethernet-unit in one of the ports of the Broadcom. For getting both IPTV and Internet working, I need to setup two VLANs (34 for internet and 4 for IPTV) on this physical network interface. Both require a DHCP-client to get their IP address. So far, so good.
However, using the simple setup as described above, resulted in getting an IP for IPTV but not for internet. Search results on this topic lead me to the solution that both VLAN interfaces require to have a different MAC address. The original modem/router showed that the IPTV-connection (VLAN) has a MAC address which is a +1 of the internet-connection (VLAN). Here comes my problem. When I do that using the WebUI (interfaces -> IPTV -> field MAC address), I notice that both VLANs get the new MAC address - where I expected that only the changed interface would have an updated MAC address. Can someone explain me why this occurs and if this is OPNsense-expected behaviour?

I was able to fix this problem, in my situation, by going to the shell of OPNsense and running ifconfig bge0_vlan4 ether 00:00:00:00:01 (fake MAC address here...) This forces the interface to use the provided MAC address; which I expect when setting this on the WebUI. However - then the following problem is that after a reboot, these settings are lost - since I just executed them on command line. So another question from that perspective for me is: How would I be able to persist these changes?

I hope my situation and questions are clear (enough) for being able to follow my thoughts and challenges.
Thanks for reading and I hope one can share its thoughts with me :-)

~Mikki