|
|
Post by michiel on Nov 17, 2015 22:21:46 GMT
Sure, no problem. I was just wondering.
I'm actually looking into the dev manual, to see if I could, at some point, lend a hand. Being able to run SW instances in a virtual environment would greatly improve my (and probably others) ability to test SW, so I'd like to get that working.
|
|
|
|
Post by Lee Sharp on Nov 19, 2015 18:28:49 GMT
It "works" now with fully emulated hardware. The support is for the special virtual hardware that gives the image much better performance.
|
|
|
|
Post by michiel on Nov 20, 2015 22:49:25 GMT
Nice!
|
|
|
|
Post by okibcn on Apr 1, 2017 21:20:25 GMT
I have downloaded smallwall 1.8.4b11.img and installed in an Hyper-V environment under a Windows 10 host. m0n0wall was doing a great job, but I only supported the old legacy network cards limited to 100Mbps. With smallwall 1.8.4b11 things hasn't changed that much. It detects the Microsoft virtual environment but for some reason the virtual network cards are not detected. By the way, the legacy cards work without any problem in smallwall.
The virtual network cards are detected in smallwall as sis0 and sis1 devices, instead of de0 and de1 for the legacy network cards.
Are you having the same issue?
I really like smallwall since it is much better than DD-WRT or openWRT and smaller, much smaller than the huge OPNSense or pfSense. If I only could have the virtual network cards running...
Any idea??
Thanks
|
|
|
|
Post by Lee Sharp on Apr 3, 2017 20:41:07 GMT
It detects based on chipset. And while there are now some drivers for HyperV, they were less then stable on the version of FreeBSD we are using so they are not included. It is better in later versions, but we are not there yet. Are you sure you can not use emulated Intel gigabit nics? VMware, KVM and Xen all support them...
|
|
|
|
Post by okibcn on Apr 4, 2017 2:03:32 GMT
It detects based on chipset. And while there are now some drivers for HyperV, they were less then stable on the version of FreeBSD we are using so they are not included. It is better in later versions, but we are not there yet. Are you sure you can not use emulated Intel gigabit nics? VMware, KVM and Xen all support them...Hyper-V No, there is no gigabit emulated Hyper-V network card available, it only emulates 100Mbps Intel NIC. Windows 10 shares the same Hyper-V technology with Server 2016 and at least in the Creators update of Windows 10 the Hyper-V is unable to emulate a gigabit card. I tried to install the same FreeBSD 8.4 server and integrate the BIS into it and then later port the drivers to smallwall like sami described a few posts before. However, it seems that portsnap for this emulation was deprecated on 3/1/2017. So no way to integrate them any longer. It seems that the only way is to go forward and use at least the FreeBSD 10.1 kernel in future smallwall release to be used as the ideal router for a virtual environment. It works without any problem at full speed with 10.1. Maybe it is too obvious, but what is the problem of moving from 8.4 to 10.1? By the way, thanks for keeping this small gem alive. Regards |
|
|
|
Post by okibcn on Apr 4, 2017 13:16:10 GMT
Well, after a few hours last night I have decided to try to generate a new minikernel based on a fresh FreeBSD release, 11.0 or maybe 12.0 (CURRENT) as a first step and proofof concept. I am somehow proficient with linux and FreeBSD looks like a bit old to me compared to all the tools available for the current linux distributions. So, I will have to remember the old days of vi. It can't be worst than dealing with a VAX. I have found a very interesting work done by Manuel Kasper, more than a decade ago, on how to reduce a FreeBSD distro ( neon1.net/misc/minibsd.html) and I am willing, with some dedication during nights, to adapt it to recent FreeBSD releases. Years ago the whole process was scripted to be easily performed. That work is still available at www.miniBSD.org. After that I will try to follow the SmallWall Developers guide ( smallwall.org/docs/dev/index-single.html). I am not familiar with the structure of SmallWall internals and how it depends on the FreeBDS version. The other problem I foresee will be to identify the changes from FreeBSD 8.4 to current releases affecting the network configuration, daemons, etc... have you identified the problems? What is the current status of SmallWall project? Thanks Lee |
|
|
|
Post by Lee Sharp on Apr 4, 2017 14:40:16 GMT
Wow! Every VM our there has an emulated gigbit nic except for Microsoft... I guess I should not be surprised.  As to your question, I have two reasons. First, up to now there has not been a pressing need. The jump to 8 for m0n0wall was specifically to support all of Intel's new nics on the Atom boards. I was suspecting to not have to move until 10gig got cheap. Second is the complexity. I am VERY conservative when it comes to IT. I want rock solid security and stability. The move to 10 or 11 requires a LOT of changes to the underlying programs that make up smallwall. I know because Andrew White is doing it on t1n1wall! As the bigs shake out, I will follow the path he is blazing. But now that I know about this, I may have a bit more urgency. In the mean time, feel free to check out one of Andrew's beta releases and see if it works for you! |
|
|
|
Post by Lee Sharp on Apr 4, 2017 14:47:21 GMT
Well, after a few hours last night I have decided to try to generate a new minikernel based on a fresh FreeBSD release, 11.0 or maybe 12.0 (CURRENT) as a first step and proofof concept. I am somehow proficient with linux and FreeBSD looks like a bit old to me compared to all the tools available for the current linux distributions. So, I will have to remember the old days of vi. It can't be worst than dealing with a VAX. I have found a very interesting work done by Manuel Kasper, more than a decade ago, on how to reduce a FreeBSD distro ( neon1.net/misc/minibsd.html) and I am willing, with some dedication during nights, to adapt it to recent FreeBSD releases. Years ago the whole process was scripted to be easily performed. That work is still available at www.miniBSD.org. After that I will try to follow the SmallWall Developers guide ( smallwall.org/docs/dev/index-single.html). I am not familiar with the structure of SmallWall internals and how it depends on the FreeBDS version. The other problem I foresee will be to identify the changes from FreeBSD 8.4 to current releases affecting the network configuration, daemons, etc... have you identified the problems? What is the current status of SmallWall project? Thanks Lee Very much alive, but slow, and on purpose. Changes have to be defended, and proven. We are also close with another project, t1n1wall. The big difference between us is the intended audience. SmallWall is for business and needs solid support and stability. A bad version may not be updated for YEARS, and so I am trying VERY hard to make sure there are no bad releases. Also, that makes it easier for vendors to ship product as the images do not need to update all the time. As for the timeline... There are a few things I want to finish up before I make a full release, and 1.8.4 may be the last of the 1.8 line. After that release, moving to 11 will start. And yes, help is welcome! |
|
