[ home | files | links | topics | stickers | about ]

Todays Stats

Visitors: 105
Referrers: 9
User Agents: 45
Pages Served: 368
Total Pages



m0n0wall And You: Die Harder
hardware : by Corey - October 24th 2006, 12:11PM
Recently, the router at the gym where I work out has been going on the fritz. It's a D-Link DI-524 so it stands to reason. As the local technology consultant for the gym, I convinced them to allow me to build a m0n0wall box for them.

The issue is that the gym is a small private studio and they are trying very hard to make it look chic and fashionable. To me, this means that they'd rather not have a honking Dell Optiplex G1 like the unit I built a few months ago. I found a solution over in SA's SH/SC forum: The IBM NetVista N2800 8364 Thin Client.

In the thread, a guy from England discussed how he made his unit work. His site has a good write-up on how to accomplish it, including this image where he outlines what is what inside the case. I picked up an 8364 off eBay for $55 shipped.

Dealing with the two BIOS flavors can be a bit daunting if you're not experienced in editing BIOS settings so if you attempt to do this, please make sure you're not dumb. But even if you are, there is a PWD_RST jumper that will restore everything back to the land of lollypops and bikinis.

The issue I'm having at the moment is one that apparently plagues the Ethernet models of the 8364. During the Linux boot process, the screen becomes garbled and the machine eventually locks. As recommended on the aforementioned page, enabling the on-board Ethernet controller seems to solve this problem.

While that was well and fine, a new problem that is undocumented as far as I can tell has emerged. The keyboard I am using to assign interfaces as well as the LAN IP address is not functioning correctly when attached to the thin client. The same keyboard works fine on my server so I know the keyboard is not the issue. Strange characters are entered for every keystroke and always entered twice. It's the oddest thing I've seen in a while. If anyone has any ideas how to work around this, please leave a comment. I'll post an update when I get it resolved.

Now, what did I do with that USB keyboard...


+ anonymous
  Oct 26, 2006 07:49
the only things i can think of to check are A. the keyboard mapping and B. the language of the keyb layout. I once had this same problem only to find out the the keyb lang wasnt set to en-us (or us-en, whichever it is), also you might trying working on the system through SSH.
My .02


+ Corey T.
  Oct 26, 2006 14:53
SSH isn't going to work because it does not have an SSH sever, nor can you access a bash-like CLI shell.

As far as the keyboard, I'm pretty sure I checked that but I'm going to look again for good measure. Thanks for the idea.


+ anonymous
  Oct 26, 2006 21:18
vnc? i mean there has to be some kind of remote access feature.


+ Corey T.
  Oct 26, 2006 23:49
This is not the FreeBSD OS you might think. Also, VNC does not run in linux except in the enterprise version. You should read my earlier m0n0wall posts and the m0n0wall website to see how it works.


+ Tommy G.
  Oct 27, 2006 08:53
Um, VNC will run on linux. I think I used to use RealVNC.


+ Corey T.
  Oct 27, 2006 11:27
They changed thier support levels according to their download page. But who knows; it is a mystery!


+ anonymous
  Oct 27, 2006 11:44
they do have a vnc (ported?) to freebsd. url is


+ anonymous
  Oct 27, 2006 11:45


-+- neodux blog -+-
Page generated for in 0.03971 seconds.
rss 2.0 feed