HD Freesco install

Support section for FREESCO v0.4.x

Re: HD Freesco install

Postby Speedy Lan » Fri Aug 05, 2011 5:39 am

Hi all,

I just got freesco working on a VirtualBox VM. :)
After a few failures, I was able to connect the virtual freesco to the outside world and download the EXT2-install package.
The reasons why I could not connect from the start were, I think, the following:
I had made an image from the floppy that has the same settings as my real running freesco box, and because of that, the internal networks on the virtual freesco were the same as on my real network.
Therefore it could not connect to outside and also not to my real local network. (Is this correct thinking? )

After that I tried to set the VirtualBox first NIC to be setup as Bridged, but that too, did not do the trick, and then I went back to set it up as NAT and changed the virtual local networks to ranges different from my real local network.
And lo and behold! I could reach the package-repository and download the EXT2-0.4.3-lewis.pkg and after that run it and setup my virtual disk for the virtual freesco to be installed on.
So, I am happy now :)
A little step forward in my understanding and testing of freesco.

One little question I have and that is why is there a EXT2-0.4.4-lewis.pkg already on the packages server?
Are we expecting a new new update to 0.4.4 soon, perhaps? :)


Some info's on my current setup:
Freesco 0.4.3 running on a old PC
W7-64 running VirtualBox 4.0.1r-73009
VirtualBox running freesco 0.4.3 setup as a linux 2.2 and with a 2GB HD and a floppy
first Virtual NIC is NAT, the 2nd and 3rd are Internal
The virtual internal networks are on a different range as my real local network.
Low lag, High bandwidth 8-)
User avatar
Speedy Lan
Junior Member
 
Posts: 28
Joined: Mon Jan 20, 2003 6:25 am
Location: Zwolle, The Netherlands (Holland)

Re: HD Freesco install

Postby Lightning » Fri Aug 05, 2011 6:39 pm

One little question I have and that is why is there a EXT2-0.4.4-lewis.pkg already on the packages server?
Are we expecting a new new update to 0.4.4 soon, perhaps? :)
Hehe that would be an accurate conclusion to some degree. As soon as I start working on the 'next' version of FREESCO I create an ext2 package for it. That way anyone who is testing it can test the entire system including the ext2 package because usually changes to the system also result in changes to the only official package. However in this case the release 0.4.4 is not to far into the future.
The reasons why I could not connect from the start were, I think, the following:
I had made an image from the floppy that has the same settings as my real running freesco box, and because of that, the internal networks on the virtual freesco were the same as on my real network.
Therefore it could not connect to outside and also not to my real local network. (Is this correct thinking? )
Yes and no. In reality the external network can be connected in either NAT or bridged and all that changes is the IP address and the view from the outside looking back. Personally I prefer to use 'bridged' because then FREESCO gets an IP address of it's own on your local network and emulates a normal machine much closer than adding another NAT process.
Also because of using the exact configuration of your main router is what caused the real problem. This is because your virtual machine would have tried to make an external connection to a subnet that was identical to what it was trying to use as an internal subnet and with a NAT firewall enabled that won't work at all.
You will find for almost all configurations whether testing or playing it is much better to always start with an unconfigured disk image and spend a few minutes configuring it.
Which in the release the file freesco.043 is actually just a disk image and can have the extension '.img' added to the end of it to make it work for virtual machines.
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12080
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: HD Freesco install

Postby Speedy Lan » Sat Aug 06, 2011 1:08 am

Lightning wrote: Hehe that would be an accurate conclusion to some degree. As soon as I start working on the 'next' version of FREESCO I create an ext2 package for it. That way anyone who is testing it can test the entire system including the ext2 package because usually changes to the system also result in changes to the only official package. However in this case the release 0.4.4 is not to far into the future.

That is good news! :D

In reality the external network can be connected in either NAT or bridged and all that changes is the IP address and the view from the outside looking back. Personally I prefer to use 'bridged' because then FREESCO gets an IP address of it's own on your local network and emulates a normal machine much closer than adding another NAT process.

Yes, I found that out too, and I have made it bridged now.
It is nice to have it as a virtual machine, since now I can test all the 'outside' things of freesco without any risks, since they are still inside my own local network.
I also made a new virtual box that runs XP and connects to the virtual freesco's 1st internal network. Just like for real. :wink:

Thanks for the reply and all the work on the new version.

Cheers!
Low lag, High bandwidth 8-)
User avatar
Speedy Lan
Junior Member
 
Posts: 28
Joined: Mon Jan 20, 2003 6:25 am
Location: Zwolle, The Netherlands (Holland)

Re: HD Freesco install

Postby Lightning » Sat Aug 06, 2011 2:26 pm

As a teaser, here is what is in v0.4.4 and to be released in the near future
############################## Changes in v0.4.4 ##############################

Repaired a bug in the smtpclient -A attach option that required and extra
argument to the flag that did not need any arguments.

Repaired a logging bug in the dyndns script that caused the name "dyndns" not
to be displayed.

Repaired a firewall problem that allowed access to servers on PPP Internet
connections when the server was set in secure mode. This bug was introduced
in 0.4.3 in the firewall only mode option.

Repaired a bug in the mv2hd command that caused other language definitions for
control characters not to work.

Repaired a bug in the rc_net script that used the wrong 'restart' command when
another language was in use other than English.

Repaired the 'pkg' command so that when downloading files or installing kernels
"Installation aborted" is not displayed on exit.

Repaired a bug in the live.cfg creation scripting that would sometimes loose
some of the data in the file due to more than one instance trying to write to
the file at the same time.

Repaired a bug in the 'pkg' command kernel installer so that the '.map' file
is also installed using the correct URL. Also some changes and repairs to the
kernel installer section of the 'pkg' command.

Changed the kernel to use a 'full cone NAT'. This change required enabling the
'loose UDP masquerading' option in the kernel source. Without this option
enabled, the firewall is a 'port restricted NAT' and inhibits some particular
applications from wanting to run behind FREESCO.

Changed the 'killall' command so it is now more compliant with the killall
command found in other OS's. This means the signal used to kill the process can
precede the binary name to be killed as it is in other OS's or it can follow the
binary name as it has been in FREESCO since it's inception.

Added full system support for virtual interfaces. This also includes DHCP for
virtual networks and interfaces so that more than one subnet can be supported
on a single interface. This means that eth1, eth1:0 and eth1:1 will all act as
separate interfaces even though they are one physical interface and a single
network can be divided into multiple subnets.

Added a system test at boot time so the system can automatically adjust the
configuration language from any previous language to the currently installed
default language.

Added a new language section into the setup to make converting the system to
a different language an easy operation.

Added the ability to change the smtp port into the individual mail client
configuration files.

Added gzip to compress files

Added tar create to make tarballs of files and directories.

Added wput as an FTP client suitable for uploading backup files and directories
for network backups. Which is a planned new feature on a future release of
FREESCO.

Added a new auto patching mechanism. This mechanism checks for system patches
every two weeks and auto installs them if enabled. This new feature does not
check for updates at every boot and requires two weeks of uptime before it will
activate when enabled. This feature is intended for systems that are setup and
then left unattended for long periods of time.

Added boot CD support into the system. Also added a new ISO image of FREESCO to
make creating a boot-able CD easier. This version has all available PCI drivers
installed on the disk to make the initial CD boot a running system with
minimal services running. It is also possible to re-master this image to be a
live system capable of running in any mode by copying the running /etc directory
to the CD.

Added DHCP static IP and IP range support for virtual interfaces and networks.

Added wol v0.2.0 to the base system binaries. This allows for all wake-on-lan
enabled computers to be started remotely.

Added a control panel 'wol' section that displays all internal machines
connected using DHCP and allows the user to wake any of them up remotely with
two clicks of a mouse button.

Added IP address monitoring capabilities into the netmon binary. Using this new
feature allows current bandwidth usage and tracking any any internal IP address.
The resulting information can be seen on screen 6 and in the control panel
under the 'network' function. To add or remove IP addresses in 'netmon' just
use 'netmon -e' to edit the configuration file.

Added clearing of bandwidth usage for the netmon binary. Using the new 'netmon'
binary all that is required is to use 'netmon -r' to reset all of the data
fields for bandwidth usage.

Added an option into the RAS (Remote Access Server) to enable a no
authentication login. This option allows hardware such as ReplayTV and
Showstopper to dial into FREESCO for program listing updates.

Changed the netmon binary to correctly calculate the receive data for virtual
interfaces. Thanks to 'justdave' for the new code and countless hours of work.
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12080
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: HD Freesco install

Postby justdave » Sat Aug 06, 2011 8:33 pm

Gosh, you sure have been busy.
justdave
Junior Advanced Member
 
Posts: 124
Joined: Sat Dec 22, 2001 2:00 am
Location: san jose Ca USA

Re: HD Freesco install

Postby Speedy Lan » Sun Aug 07, 2011 3:06 am

What a list!

Perhaps I should post this as a new topic.
which I did here:
viewtopic.php?f=15&t=17542
Low lag, High bandwidth 8-)
User avatar
Speedy Lan
Junior Member
 
Posts: 28
Joined: Mon Jan 20, 2003 6:25 am
Location: Zwolle, The Netherlands (Holland)

Previous

Return to FREESCO Support for v0.4.x

Who is online

Users browsing this forum: No registered users and 7 guests

cron