I don't believe that the ADSL will work without it but I could be wrong.

Does this Cisco router plug directly into the ADSL telephone wire, or is there a separate ADSL modem?

If the former, then you could be right. If the latter, there is a good possibility that any router will work if it's configured right.

Last time I saw this, I was at work last month. I promptly called our IM guys, who then sent out an e-mail saying "Don't $#@$ forget to patch your lab servers!".

I just got another one today, and checking my wormattack logs on my Linux server here, it did make a comeback in the past few days. All on a mostly closed network.

The phone line goes directly into it so I think I have to have this router. Got it when ADSL was installed. It's a shame that we can't somehow use programs like ZoneAlarm to protect the empeg from attacks too. Oh well, I need another gaget.

If you're talking about, say a BEFSR41, I got mine for $50 but that was after a $50 rebate. This was over a year ago. Great router, effortless to configure and hasn't failed me once.

I know I asked this already, but is there any reason you're not just changing your kHTTPd port to avoid these hacks? If your HTTP daemon isn't running on 80, you won't get hit by these viruses. This is much simpler than buying hardware, and it's free...

You mentioned having to change to URL to the empeg after changing the port. How would that work?

Well 80 is the default port so normally you don't need to specify it. If you change the default port on your Empeg, you'll just have to go

http://192.168.0.0:8080/

If your port is 8080. A few extra characters to type or bookmark.

The other thing to keep in mind is that Internet Explorer requires the http:// if the port changes. Ensure to manually type it out if you decide to change the web port in hijack.

Thanks for explaining it to me. I will do that and see how well it works. I'll also look into the cost of a Net Gear firewall. Either way I will put it under some protection.

Keep in mind that I'm recommending the firewall box not for the empeg, but for any actual computers on the network. As I said, if your local network is open to the internet, the empeg is the least of your worries.

Anyone with a broadband always-on connection should, at an absolute minimum, be hiding behind a NAT layer. That's just my generalized advice. Products like ZoneAlarm are nice, but they're not the whole solution.

One other note: if you still want your friends to download from the empeg, and it's behind the firewall, you will need to do some configuration tricks to get it to work for them. Either create a DMZ (usually used for web servers on firewalled networks, which, actually, that's what the empeg is doing in this capacity), or by doing port forwarding or something like that. This hopefully will be covered in the manual for the firewall.

If you really want a netgear, I've got a RT311 that I wouldn't mind selling. I stopped using it because it seemed to stop sending DNS queries through my cable modem after a while.. As Cable modems are tempermental things, I really don't know if it's the router, or just the fact that cable modems like to change your IP in funny ways, and it can't handle it.. *shrug*

I would personally suggest getting a LinkSys.. The Netgear uses a menu driven (through serial/telnet) interface that umm.. leaves a lot to be desired.. Linksys has a nice, easy to use web interface that provides functionality that you actually can use..

They both support PPPoE connections, so ADSL support is no problem..

Ahh, but that character interface can be a godsend for remote configurations. Not that that's probably an issue here.

Then again, I'd still advocate using a cheap Intel box running OpenBSD or something. I've never been impressed with the limited functions available in those black box (blue?) solutions.

Yeah, and Laura's already demonstrated a proficiency in using a serial cable and terminal software with a remote peripheral...

Then again, I'd still advocate using a cheap Intel box running OpenBSD or something. I've never been impressed with the limited functions available in those black box (blue?) solutions.

Plus you never know how a dedicated box will affect you until you have one. My "server" started it's life as a Windows NT file server. From there, I added a caller ID program, Distributed.net proxy. Then I decided it was silly for my roomate and I to pay for 2 more IPs (on top of the 3 we had) when we were getting laptops, so I formatted it and played with that weird OS called Linux. It started as a simple sharing box, then added a web server, Windows file sharing via samba, then mail, DNS caching, and a pop server that pulled many accounts.

Years later, it now does: Internet sharing, DHCP, DNS caching + backup for a domain, mail gathering for many accounts including some hotmail ones, IMAP mail with an awesome front end, NFS file sharing, Windows file sharing, Battle.Net server, (from time to time) a Half Life or UT server, web proxy to speed up the connection a bit, advanced PHP web serving, roaming profiles for Windows, LDAP address book, distributed.net proxy and stats, and an empeg web cam. All from hardware I have no use for otherwise. (And I'm sure I missed a few functions there). While it has taken quite a bit of time, it has been much more rewarding, as it's the sole reason I know Linux as well as I do.

I tried changing the port in config.ini this morning. I can't reach the player using the port # but I can still get to it not using it. So that solution didn't seem to work.

Eh? Not sure why. Are you sure you typed in the whole URL? Like, if khttpd_port (which must be in the [hijack] section of config.ini) is set to 8080, the URL would look like:

http://xxx.xxx.xxx.xxx:8080/

The http:// part is required... If you did all that and it's still not working, I'm stumped, because it works for me.

Check your config.ini edits and make sure that they're all in the right places based on Loren's Hijack FAQ. Also make sure your config.ini isn't oversized from having too many Favorite Visuals entries.

It works because in one other Thread, I ask for this cos I had Displayserver installed and conflictiing with Mark Hijack Webserver.

I trid just now to change the port in my config.ini and that rocks as well as port 80.

I tried with khttpd_port=81


Included screen capture with port 81 setup

(Dont tell me for bad conformity network address, cos it's my job's adress class)

I tried it again with port 81 and this time it does work. Before I tried with 90, 8080, 9090, and 4040. I'm not sure why the 81 works but I'm happy with that.

Thanks again for the help. Now I can rest a little easier.

I tried it again with port 81 and this time it does work. Before I tried with 90, 8080, 9090, and 4040. I'm not sure why the 81 works but I'm happy with that.

Heh, probably because ZoneAlarm was blocking web traffic on those other ports?

Sorry, but tried port 90 and also works.

Tony's right, probably ZoneAlarm that blocks these ports ...