I like the MiamiDX-GUI . It gives a quick overview
and at the same time let you easily configure the stack.
Perhaps a user/expert-modus where "dangerous" settings are
hidden from normal users.

I hope this TCP-Stack will be stable and ultra fast.
Concerning the GUI I would say something similar to MiamiDX for a start could be used.
Will PPPoE be supported ?

Concerning the GUI I would say something similar to MiamiDX for a start could be used.

Hmm, I want to avoid such complicated GUI.

Will PPPoE be supported?

Not in the 'bounty' release. After that everything will be possible: as ezTCP is planned to be opensourced, someone can add PPPoE, or even I can do it if it is openly documented standard (but well I do not have a place to test it...).

I think the GUI should be simple and easy to use. That is the number one thing I would say. MiamiDX is a mess. i dont even use the GUI any more since I set it all up.

I share Robin's opinion, the GUI should be simple, in the style of MiamiDx, with an additional expert mode.

Though it might be too much asked for the bounty release, what about a wizard? A step-by-step setup manager for the common user. With such a wizard present, a more complex/complicated gui (maybe like miamidx?) shouldn't be a problem or even be welcomed by more advanced users.

Regarding the GUI - I see a danger in making it too simple. It seems that people have various opinions about the MiamiDX GUI (I personally think it's quite logical and self-explainatory), but say that you were to redesign the MiamiDX GUI - how would you redo it so that it will become more "simple" (whatever that is) without loosing the ability to control every aspect of the network setup?

That said, if Krashan feels that a GUI á la MiamiDX would be too complex and drain too much effort from the main project, then I would have no problem with a "simple" one (again: whatever that is) or even no GUI at all. Perhaps a powerful GUI could become a different bounty then?

I think a GUI is very importent.
But First we need ezTCP, without GUI but with a XML Configfile. Krashan could release ezTCP with some Configfiles with DHCP and static IP.
And then an ezTCP Gui bounty could be started with a setup Wizard, and a GUI with an "Advanced User Mode" switch.

Doesn't the current bounty demand a GUI?..

For program usage I would like a very simple gui. Rather like Genesis than Miami.

IMHO the preferences do not need a gui which addresses all possible options as long as editing a configfile will not be too cryptic. A good documentation should be enough. Remember that MOS is not a n00b system.

I guess that if it is called "EZ" it should be easy for everyone setting it up and control it.
It does not prevent the use of an editable config file.