Messages

Most probably my ISP has hacked my router. (Dont' argue this). 

LOL, no, just no, your isp didnt hack nothing.
And then to say we cant argue that, are you kidding me? If nothing is opened to wan side, not even your ISP can hack the opnsense box.

The setup is not so important here, just wanted to hear if others have the issue!

//Ase

Then the problem isnt important to anyone either, you cannot ask for help and then not share details.

You are trying alot of stuff without actually having any basis for doing so.

1. find out how the game's master servers query's the game servers.
2. see if anything is missing in the firewall needed for the master server to query the gameserver.


You've probably setup the firewall wrong, as many of us did when we first started using Opnsense, rules are to be seen FROM the firewall.
Show the rules you have in place now please.

Either way you SHOULD see the query coming in on the firewall, being blocked or passed, so check the live log.

If you dont see any of them reaching the firewall theres something else wrong network wise.

Does your OPNsense web GUI listen on port 443 by any chance?

Check out System: Settings: Administration >  TCP port.

This is 100% it, i moved gui to 449 to accomodate 443 forwarding

I cant even get it to work when using vmxnet, so i think the 10gb card has a bad firmware, or, is just broken

What do you mean by "when using vmxnet"? Is this a virtualised installation? Have you tried booting OPNsense or FreeBSD 13 on bare metal with this card present?

PCIe passthrough is not guaranteed to work in all hardware configurations, even ESXi is particularly picky.

Yes its virtualised with pcie passtrough, ill try a bare metal run with opnsense this weekend.

heb je upnp service aanstaan? zo ja uitzetten.

Will this restructure improve speeds (work around 1core issue)

for some reason i cant install the kernel?

Not Found ] Failed, no signature found.

24.7_10

do i need to be in the beta channel?

I cant even get it to work when using vmxnet, so i think the 10gb card has a bad firmware, or, is just broken

if I were you, I'd verify that firmware on the card is as it should be by booting it onto a vanilla freebsd of the same OPN version and on a linux one.
Cases like these can be down to corrupted or wrong firmware like a bad crssflash. Booting to other OS can help verify in a non-destructive way.

Thats actually helpful, im going to try this this weekend, thnx

Hi, did you find a solution? I have the same exact output from dmesg on opnsense.

I havent tested yet cause my uplink is only 500mbit, but im going to go to 8gb Fiber next week so im going to reinveestigate coming week

if I were you, I'd verify that firmware on the card is as it should be by booting it onto a vanilla freebsd of the same OPN version and on a linux one.
Cases like these can be down to corrupted or wrong firmware like a bad crssflash. Booting to other OS can help verify in a non-destructive way.

Thats actually helpful, im going to try this this weekend, thnx

Noone that has a clue?

Anyone have an idea how to get this to work?
Opnsense recognizes the nic's but they get a 00:00:00:00:00 mac address, and are unusable in OpnSense.

Code Select Expand


bxe0: ERROR: Invalid SHMEM Validity signature: 0x0000008
bxe0: ERROR: Invalid phy config in NVRAM (PHY1=0x0000008 PHY2=0x0000008)
bxe0: Uknown media
bxe0: IFMEDIA flags: 20
bxe0: using defaults for TSO: 65518/35/2048
bxeo: ERROR FW failed to respond!
bxe0: ERROR MCP response failure, aborting
bxe0: ERROR Failed to unload previous driver! time_counter 10 rc -1



And even more...