Posible bug in if_msk.ko for pfSense 2.2.4 on Firebox e-core-x

[eNepper]

I may have found a bug in the if_msk.ko posted here https://forum.pfsense.org/index.php?topic=20095.msg460754#msg460754

When the module is loaded the msk interfaces are not working properly. The problem is a real strange on because as fare as I can detect the only thing that aren't working properly are DNS.
if I assign a lan interface to msk(0-4) the computers on that interface aren't able to do dns lookups.
if I assing a wan interface to msk(0-4) the firewall it self aren't able to do any dns lookups.

I have reverted to the original module to see if it was a software or hardware problem, and now I'm able to do dns lookups.

I'm running pfSense 2.2.4 on a firebox e750x bios 8.1 booted from a 60gb hdd.

Are there any way to fix this?

[chpalmer]

Ever get by this?

Nobody else seems to be having this issue so just wondering.

[ccnet]

Hi,

I'm running (trying) Pfsense 2.1.5 on Firebox e1250x and having some trouble with msk interfaces.

I'm running pfSense 2.2.4 on a firebox e750x bios 8.1

Where did you find bios 8.1 ? I only find v7. Thanks.

[Evonder]

I am having the exact problem using the msk module from creama. I use the msk as my LAN connections and am able to ping the LAN address of the firebox but not the other way around. I am also not able to do any DNS lookups.

The sk module works fine and am currently using it.

pfSense 2.2.5 full install
Firebox x5500e
bios 8.1