Hi there, sorry but askimet caught your message and could not reply to it until today (my bad!). If you look around the net I\'m sure you can find a more updated spec file but that does not matter for the installation goal, all that it does is telling the RPM system what to do and where to get files, so no need for a newer version.

Cheer Lethe.

Hi there, first of all check that the following directive in your ssh configuration file is enabled X11Forwarding yes, secondly verify that the xauth package is installed and available on your system. Make sure also that putty saved the X forwarding settings on the Windows machine.

Let me know if this solved the problem, cheer Lethe.

Hi there, you can easily find my email address in the contact page and send me the images via mail, just keep in mind I\'m not able to reply immediatly due to the fact I don\'t have access to the internet for most of the day.

Regarding the Pythong thing I can\'t be sure that is the problem, that was something happened to me in the past but you can easily check that with an rpm -qa | grep python and check the results, if you\'re using something like Yumex (gui front end to yum) just open it and type python\" in the search box and see which version is installed.

Regarding the firewall you have to check Dynamips settings, the ports used by the hypervisor are reported there, bydefault if memory serves it uses Base port 7200, UDP 10000 and 2000 for the console access.

I\'ll be waiting for your follow up, cheer Lethe.

Hmmm werid, one thing to check is that Dynamips is actually starting (you can test this under the settings menu of GNS3 if it is green you\'re good to go). I\'ve mentioned xterm because I read you were running Fedora 12 (not 11 as you wrote) as xterm it\'s not installed by default.

Other things to check are that your firewall is not actually blocking ports used by Dynamips and that you don\'t multiple versions of Python installed, this once happened to me and GNS3 silently refused to start.

By the way have you tried using putty instead of xterm as the terminal application? If the routers and Dynamips are starting normally the problem should lay there.

Lethe.

Hi there Oleg, thanks for your comment I think the problem is that GNS3 by default use xterm as the terminal application for dynamips and that is not installed, you could install it with yum install xterm or simply install putty and configure GNS3 to use that as illustrated on the post. If this still does not solve your problem maybe you did not install all dependencies for GNS3.

Let me know if this solved your problem or not and I'll try to help you further troubleshoot this.

Lethe.

Hi there highwind don't know why but my previous comment disappeared, to be totally honest I've searched this as for what I could see (and for my knowledge) there is not easy way to do this :( In case I should be able to find this I'll post for sure.

Lethe.

Dove dove? Dimmi che sistemo subito, finite le ferie mi posso ridedicare un pò al blog, ero completamente sparito :D

Hi there Cisco, thanks for your words, I totally agree... it's just sometimes you need to stop a moment break down and act as a human... It'll pass I'm sure, even if with all what is going on at the moment (yes even now) it's a bit hard but well this is the fun in life ;)

Thanks a lot for your words I really appreciate them! Come back visit me ^^

Lethe.

Well "yum install clamav" is actually the only procedure to install via the Fedora package manager, this way when you install clamav the rpm database will keep track of the version installed and once ClamAv developer will release a new version of the product someone, usually at the Fedora infrastructure group, will make this version available in rpm format so that your system will warn you of a new version and will let you install it (you should be familiar with this process as it is the way your system is kept up to date).

If you choose to download the the source code version of the package what's different it's simply that you'll be compiling everything by hand instead of letting the system do this for your, keep in mind that if you don't have very particular needs or you're an expert admin/developer usually there is no need for such a level of customization. Keep also in mind that, when a new release of the package (well source code in this case) will be made available you won't be notified for automatic installation but you'll have to download the source again and recompile everything...

There are pros and cons with every of the two methods, and to be honest also different "school" of thought about this, but usually if I can find an RPM version of the needed package I tend to prefer that as it makes easier to keep everything up to date (this is not a big problem when you have only one or two servers, but try to do that for a 100+ servers in datacenter...)

Lethe.

Hmmmm for what I can see from the error it seems you retained the master exim.conf file while adding the files described and not commenting the appropriate lines, drop me a mail and as soon as I can I'll send you a modified copy of the exim configuration file used in this particular configuration so you can copy it and analyze the different fields, it'll take some time as I have to find it again but in case just remember where I put those virtual machines.

Lately I've been working with this setup only with postfix as I prefer it as MTA for its robustness and modularity :) Anyhow I'll post the configuration file as soon as I can.

***EDIT*** During the holidays or next year I'll post an updated series about this just using postfix instead of exim, just to let you know :)
Lethe.