I know I saw some big pictures of the frontpanel some time ago on the empeg site. Does anyone have one of these lying around ?
I need them for empegApplet...
BTW, I wrote some code in the ir driver to let other processes generate IR-codes. I'm gonna install the kernel this evening, so I hope this works

Frank van Gestel

We can supply graphics in any resolution up to 3000 x 4000 (although 40Mb TIFFs may be a little large for your application). If you can't find what you need on our web site(s) let me know and I'll have something tailored for your application.

Rob

SOmething with a width of 1024 would do fine,. I ripped th empeg picture from the developer-site for now ( I hope Verement doesn't mind ), but I need more detail for proper scaling.

BTW my new kernel works, compiled extra's :
firewalling
IP Aliasing - multiple IP-adresses
IRLpt - printing over infrared

The IR-hack didn't work (yet), have to recompile...

Frank van Gestel

Aaaaroooooo????

Okay, maybe I am a little dense (DON'T EVEN TRY POSTING ON THAT) ... But why a firewall in my empeg ? And for that matter the other two as well

Cheers,
Hans


Mk2 - Blue - 080000431

I just thought that firewalling would be the most obvious thing to include in the kernel while we are waiting for a way to secure the way emplode works over ethernet.
With this I can completely block all unwanted networktraffic to the player.
I work at a large site (+/- 3500 IP-adresses) and a WAN connection to over 100.000 which can all connect to my tiny empeg. Some dude from the other side of the world could download empload from the web and start trashing my empeg player once they find out which IP it's got ( fairly simple, I added an alias called 'empeg' in DNS).

I've had hackers in my home system installing some client program that was meant to flood-ping a server when it received a network-packet on a specific port. They installed a whole bunch of those programs on several machines around the world. Once they send one packet to those machines, they all begin to broadcast network-packets as fast as they can, rendering the target-machine completely isolated. They never knew who hit them as traces lead back to the hacked systems.



Frank van Gestel

Hmm, sounds like a little overkill but I guess it is one way of getting the job done for now. Personally a hosts.allow + hosts.deny type of idea sounds more workable for people not so familiar with firewalling. Of course a simple uid+pw solution built into an authentication system for ethernet is most likely the way top go.

Cheers,
Hans


Mk2 - Blue - 080000431

hosts.allow and hosts.deny will only work if tcpd is installed. tcpd will only run properly under inetd. It's not a solution to run player under inetd.

Firewall-code in the kernel doesn't have much impact on the functionality and performance of the unit. Fortunately the linux kernel-programmers do not do things the M$ way

Frank van Gestel

I know that ... I said a host.allow + host.deny type of thing ... I was thinking more of something like it that you could update in the config.ini file. You know, some really basic IPnumber stuff i.e. 192.169.*

Cheers,
Hans


Mk2 - Blue - 080000431

Personally, I think I'd have put a firewall between the empeg and the rest of the network, rather than on the empeg itself, but to each his own, I suppose.


Roger - not necessarily speaking for empeg

unfortunately I cannot influence the network-infrastructure at work. ( working as a contractor at Philips )

Frank van Gestel