Smoothwall won't boot

AirWolf

AirWolf

Honorary Master
Joined
Aug 18, 2006
Messages
24,890
Reaction score
1,696
Location
Port Shepstone, KZN, RSA, EARTH
IMG_20160407_100431.jpg

Problem started this morning.

Normal boot gets stuck on boot process - screen goes blank. Menu item smoothwallBig, gives the errors above.

Is it a harddrive problem?
 
Tested memory with Hiren and it checked out fine.

Another problem was that the cpu was overheating. Put in some thermal gel and it booted fine, those if froze every time after about 5 minutes, even though cpu temp remained in the 50-60 degree range with warning and shutdown set to 70 and 75 degrees respectively.

Anyway, that machine was 10 years old, so got a new machine today.

Old one had 3.0 and install 3.1 on new.

Need to finish it up tomorrow.

I see that the alias IP feature in full firewall control is handle a bit differently in 3.1.

If my red ip is 10.0.9.10 and green is 192.168.0.1, with a server 192.168.0.2, and I want to make the server accessible on the red side via 10.0.9.4; under interfaces should the secondary ip be 10.0.9.4 mapped to 192.168.0.2? And then firewall control rule traffic from red:10.0.9.4, traffic to 192.168.0.2 on tcp protocol?
 
jsheed_sa said:
Bit of a thread hijack but how does Smoothwall compare to PFSense nowdays?
Click to expand...

Last time I used Smoothwall it was a bit limiting for me. Not much you can do from the web interface (compared to PfSense). Makes it great for people who want a simpler solution though.
 
AirWolf said:
Tested memory with Hiren and it checked out fine.

Another problem was that the cpu was overheating. Put in some thermal gel and it booted fine, those if froze every time after about 5 minutes, even though cpu temp remained in the 50-60 degree range with warning and shutdown set to 70 and 75 degrees respectively.

Anyway, that machine was 10 years old, so got a new machine today.

Old one had 3.0 and install 3.1 on new.

Need to finish it up tomorrow.

I see that the alias IP feature in full firewall control is handle a bit differently in 3.1.

If my red ip is 10.0.9.10 and green is 192.168.0.1, with a server 192.168.0.2, and I want to make the server accessible on the red side via 10.0.9.4; under interfaces should the secondary ip be 10.0.9.4 mapped to 192.168.0.2? And then firewall control rule traffic from red:10.0.9.4, traffic to 192.168.0.2 on tcp protocol?
Click to expand...

With above configuration, from red can open the server directory using the red ip 10.0.9.4, but can't get Sage Evolution to connect (the server on green). Get the error:
View attachment 355310

Any ideas?
 
AirWolf said:
If my red ip is 10.0.9.10 and green is 192.168.0.1, with a server 192.168.0.2, and I want to make the server accessible on the red side via 10.0.9.4; under interfaces should the secondary ip be 10.0.9.4 mapped to 192.168.0.2? And then firewall control rule traffic from red:10.0.9.4, traffic to 192.168.0.2 on tcp protocol?
Click to expand...

A-yup. Sounds about right.

Never worked with this kind of configuration before, though.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X