January 7th, 2008 Chat Session

 

IRC Chat on Freenode.net/#pacslinux

 

(07:43:20 PM) The topic for #pacslinux is: Flavors of Ubuntu and various specialized distributions

(07:44:33 PM) teddy-dbear [n=teddy-db@c-71-230-172-98.hsd1.pa.comcast.net] entered the room.

(07:44:44 PM) burke-bear [n=burke-be@c-71-230-172-98.hsd1.pa.comcast.net] entered the room.

 

(07:49:50 PM) Prayer: Ooooo looky at all the new joiners now.

(08:10:12 PM) rich2506 [n=rich2506@c-69-249-33-239.hsd1.pa.comcast.net] entered the room.

(08:10:27 PM) rich2506: wuzzup y'all?

(08:10:45 PM) rmg: nothing at the moment

 

(08:11:14 PM) rich2506: got my connection fixed so i'm talking direct from my laptop

(08:12:18 PM) rmg: saw your email

(08:12:39 PM) rmg: just have to remember that dang proxy

(08:14:28 PM) rich2506: yeah, i need to remember the differences

 

(08:14:42 PM) jedijf: it was worse because of the network proxy to dl the firmware for the broadcom

(08:15:19 PM) jedijf: in general, at pacs, you will only need to use the firefox proxy

(08:17:50 PM) rich2506: ok

(08:19:45 PM) Norm76 [n=norm@c-76-116-4-147.hsd1.nj.comcast.net] entered the room.

 

(08:19:58 PM) rich2506: hey norm

(08:20:01 PM) Prayer: Any "paint" experts here ?

(08:20:18 PM) rich2506: MS Paint?

 

(08:20:22 PM) Prayer: yes

(08:20:42 PM) Norm76: Hello, Rich, Rich, & group.

(08:20:49 PM) rich2506: not an expert, but i've used it

 

(08:21:02 PM) Prayer: My foster daughter has asked how to put multiple pix on to one file (like montage)

(08:21:08 PM) teddy-dbear: Norm76: here, is it time for bed?

(08:21:25 PM) Norm76: For you, maybe.

(08:22:37 PM) rich2506: i've put together a montage of multiple jpg files, but they were just joined up next to each other, no overlapping

 

(08:26:53 PM) rich2506: seems to me i remember doing that in a regular word processor

(08:28:45 PM) jedijf: i use gimp (rather poorly) to make desktop backgrounds out of various images

(08:29:38 PM) jedijf: rmg51, will see one wed night

(08:30:42 PM) rmg: I see one every time I boot Teddy's laptop

 

(08:30:47 PM) rmg: or mine

(08:31:08 PM) rich2506: sounds like a project!

(08:32:47 PM) Norm76: I think MS paint might be too simplistic to do a montage. Have you considered paint.net?

(08:36:26 PM) Norm76: http://www.windowsvistamagazine.com/US/28190304696883278/12-fantastic-ways-to-make-your-photos-exciting.html. #8. Make a montage (halfway down the page).

 

(08:39:22 PM) rich2506: ca you do overlapping images with that?

(08:48:40 PM) Norm76: I think so. It supports layers.

(08:50:24 PM) rich2506: kewl. so anyone gonna see the state of the union address?

(08:52:12 PM) burke-bear: not me!!!!!

 

(08:52:29 PM) teddy-dbear: not me either!!!!

(08:52:54 PM) rmg: can't watch that stuff

(08:53:05 PM) rich2506: i'll check out the live-blogging from firedoglake.com

(08:54:02 PM) rich2506: saves me the trouble of turning on the teevee

 

(09:04:33 PM) rich2506: got stuff to do. seeya!

(09:04:49 PM) rich2506 left the room (quit: "Ex-Chat").

(09:10:27 PM) kb3ui [n=ubuntu@h-66-167-91-140.phlapafg.dynamic.covad.net] entered the room.

(09:11:14 PM) Norm76: Hello, Russ.

 

(09:11:48 PM) kb3ui: Good evening, Norm, and the group!

(09:12:06 PM) kb3ui: Flavors of Ubuntu - is there chocolate?

(09:12:43 PM) Norm76: The bear always has chocolate.

(09:13:19 PM) jedijf: chocohttp://www.flickr.com/photos/40804924@N00/472278057/

 

(09:13:31 PM) jedijf: http://www.flickr.com/photos/40804924@N00/472278057/

(09:14:33 PM) teddy-dbear: white, milk or caramel?

(09:14:58 PM) jedijf: http://www.linux-mag.com/id/2187

(09:15:55 PM) kb3ui: I *had* to ask!

 

(09:16:29 PM) kb3ui: Jim, you did great on Saturday!

(09:16:41 PM) jedijf: wshat did i do

(09:16:44 PM) jedijf: what

(09:17:00 PM) Prayer: Sooooo, is teddy running with chocobuntu ?

 

(09:17:04 PM) kb3ui: Your presentations! I'm sure that Don was impressed as well.

(09:17:49 PM) jedijf: it wasn't me; it was dsl booted to ram - damn impressive linux

(09:18:04 PM) jedijf: hmm

(09:18:17 PM) kb3ui: Sure! It demonstrates itself without human assistance!

 

(09:18:22 PM) ***teddy-dbear prefers chocolate in the tummy

(09:18:42 PM) kb3ui: DIJ - Damn Impressive Jim!

(09:18:47 PM) Prayer: so what did happen at the meeting sat ?

(09:18:48 PM) jedijf: ty haha

 

(09:19:15 PM) Prayer: I prefer dat small linux

(09:19:58 PM) kb3ui: Jim - while I think of it, I do think you may have been a little harsh on the guy who's working with Linux on wireless. *Somebody* might have told him to do what you didn't like him doing - this was on the Yahoo! group.

(09:20:40 PM) kb3ui: I don't understand the technical issue - I just got the impression that you were a wee bit unkind to him.

(09:21:45 PM) kb3ui: Sometimes it gets frustrating to try to help people out, and I can understand your patience being fried a little.

 

(09:22:23 PM) jedijf: i may have been, but it was to the point since i was the one who got it working, and after that reply, it got working again

(09:23:03 PM) kb3ui: Hey - as long as he's happy, that's what matters! Thanks!

(09:23:51 PM) jedijf: and the frustration is more geared towards the nm-applet mechanism anyway

(09:24:27 PM) jedijf: i don't like that it breaks away from linux 'standards' (if there is such a thing) to work

 

(09:24:59 PM) jedijf: and acting in a normal linux-like way actually breaks it, and doesn't allow it to work at all

(09:25:27 PM) kb3ui: It's important to direct your frustration at the mechanism, not the PACS Linux member, and to make that clear.

(09:25:35 PM) kb3ui: On the other hand, I thought it was fun to see you and Don interact - both of you are vastly different personalities.

(09:25:42 PM) jedijf: but that being all said and done; when it does work, it works well

 

(09:26:01 PM) jedijf: yeah - he is my contemplative alter-ego :D

(09:26:19 PM) kb3ui: Don - the PACS president - a very modest, quiet, and hardworking guy. You - a very modest, not quiet, and hardworking guy.

(09:26:46 PM) jedijf: no one has ever used modest to describe me before; thank you

(09:27:07 PM) kb3ui: I *do* think you would give a very good talk at a main meeting, if you're willing.

 

(09:27:28 PM) kb3ui: Has anyone ever used "quiet" to describe you? :)

(09:27:36 PM) jedijf: not that either ;)

(09:27:53 PM) kb3ui: Didn't think so!

 

(09:28:20 PM) rmg: all we have to do is figure out how to get his laptop to work with the projector

(09:28:45 PM) kb3ui: That's always been a challenge, and a perpetual problem with the AV equipment.

(09:29:30 PM) kb3ui: We all have busy lives, but the best solution is to try the projector out before the meeting.

(09:29:32 PM) jedijf: i could have sworn that it had worked in the past -

 

(09:29:42 PM) jedijf: maybe not though -

(09:29:55 PM) jedijf: there are a couple of fixes

(09:30:21 PM) jedijf: the one that rmg51 used - but that only displayed 640x480

(09:31:05 PM) kb3ui: PACS should try to provide us with the same projector each time, if possible. And, if it buys new equipment, to choose similarly working types.

 

(09:31:42 PM) jedijf: no problem - its actually more of a linux problem than a hardware issue

(09:32:09 PM) rmg: that is the same projector

(09:32:10 PM) kb3ui: I recall that problems with AV equipment being the #1 source of complaints from PACS members. However, if it's a Linux problem, then it should be our problem.

(09:32:23 PM) rmg: and not just Linux

 

(09:32:26 PM) jedijf: so, being the rogues that we are, it is better to resolve it, than let them have any ammo

(09:32:43 PM) kb3ui: Something for us as a group to figure out and learn from.

(09:32:45 PM) rmg: I couldn't get XP to work with my TV

(09:33:14 PM) rmg: But I did get this laptop to work

 

(09:33:27 PM) jedijf: kb3ui, and it may be an issue related to the video hardware of the specific machine

(09:33:28 PM) rmg: at 1024x768

(09:33:58 PM) ***rmg agrees

(09:34:30 PM) jedijf: that's what my initial reading has discovered

 

(09:35:09 PM) jedijf: but i now have the rmg51 option as a failsafe

(09:35:22 PM) kb3ui: One thought is to get a cheap, used, laptop for the SIG that we'd always use for presentations.

(09:35:43 PM) rmg: if I can get Teddy's laptop to change resolutions that might work

(09:35:50 PM) kb3ui: Uniform hardware.

 

(09:36:33 PM) jedijf: we can play with it next month before the meeting - the room is vacant

(09:36:52 PM) kb3ui: That would be best.

(09:37:21 PM) kb3ui: Hopefully, once we get the problem licked, it won't keep coming back to get us!

(09:38:19 PM) jedijf: the worse part is a can't really remember if my laptop ever worked on a projector at pacs

 

(09:39:02 PM) jedijf: did i use my laptop and the projector for the cli stuff the previous month?

(09:39:18 PM) rmg: I don't remember you ever trying before

(09:40:10 PM) Norm76: You did the command line stuff from my laptop, Jim.

(09:40:37 PM) ***jedijf couldn't remember

 

(09:41:39 PM) jedijf: its an xorg.conf issue so it should be /fun/

(09:43:33 PM) kb3ui: I'm trying right now to use the Terminal Services Client under TightVNC to remotely access my Everex server running GoS. The connection keeps timing out. I can access the Everex's shared folders over the LAN, so the LAN doesn't appear to be the problem. One thing I noticed is that the Terminal Services Client's password field is grayed out, so I'm not getting my password over.

(09:44:40 PM) jedijf: kb3ui, i don't understand

(09:44:51 PM) jedijf: 'under tightvnc'

 

(09:45:35 PM) jedijf: is the everex running tightvnc server?

(09:45:41 PM) kb3ui: Computer: 192.168.1.35 Protocol: VNC User Name: rtobias@everex-server Domain (?): (blank) Client Hostname: rtobias (the computer I'm running from now, under virtual Ubuntu. Protocol File: blank

(09:46:11 PM) kb3ui: everex-server is running TightVNC server. Can't prove that it's working.

 

(09:46:20 PM) jedijf: hmm

(09:46:36 PM) jedijf: on everex terminal type netstat -lant

(09:46:50 PM) jedijf: should show 5800 listening

(09:46:50 PM) kb3ui: BRB to check.

 

(09:48:33 PM) jedijf: if it is running, then from terminal server client JUST enter the everex ip address in computer blank and protocol set to vnc - NO USER name - and click connect

(09:49:10 PM) kb3ui: There is no 5800 listening. What does that mean?

(09:49:30 PM) jedijf: no server running

(09:49:43 PM) jedijf: on everex type x11vnc

 

(09:49:46 PM) kb3ui: Well, that would put a damper on things, I would think!

(09:49:52 PM) kb3ui: BRB to try.

(09:51:04 PM) jedijf: kb3ui, err 5900

(09:51:34 PM) kb3ui: sudo x11vnc: command not found. BRB to check on 5900.

 

(09:51:37 PM) jedijf: 5800 is http vnc interface

(09:52:17 PM) kb3ui: No 5900, either.

(09:52:33 PM) jedijf: kb3ui, sudo apt-get install x11vnc

(09:53:22 PM) kb3ui: I should already have TightVNC server installed on Everex. What is x11vnc?

 

(09:53:33 PM) jedijf: vnc server

(09:53:40 PM) kb3ui: Do I need to start up TightVNC server each time I boot server?

(09:54:04 PM) jedijf: yeah, until you add it to startup

(09:54:22 PM) jedijf: start it - netstat -lant to verify then come back

 

(09:54:26 PM) kb3ui: That's probably my problem. How do I start up TightVNC server from command line?

(09:54:39 PM) jedijf: vncserver

(09:54:43 PM) kb3ui: BRB

(09:56:10 PM) kb3ui: 5801 and 5901 are now listening.

 

(09:56:37 PM) kb3ui: Trying client.

(09:56:47 PM) jedijf: no user name

(09:56:53 PM) kb3ui: Yes.

(09:56:59 PM) jedijf: just server ip in computer blank

 

(09:57:18 PM) kb3ui: 192.168.1.35

(09:57:29 PM) jedijf: if it is running, then from terminal server client JUST enter the everex ip address in computer blank and protocol set to vnc - NO USER name - and click connect

(09:57:53 PM) kb3ui: Anything in "Client"?

 

(09:58:14 PM) jedijf: nope - just ip and connect

(09:58:44 PM) kb3ui: Protocol VNC

(09:58:55 PM) jedijf: yes

(09:59:35 PM) jedijf: if it doesnt connect do everex_ip:1

 

(09:59:51 PM) kb3ui: After clicking on "Connect", with just 192.168.1.35 and VNC entered in window, the window disappears, and nothing has happened so far.

(10:00:01 PM) jedijf: if it doesnt connect do everex_ip:1

(10:00:05 PM) kb3ui: Ok.

 

(10:00:17 PM) jedijf: 5800 is default and 0

(10:00:56 PM) kb3ui: No 5800. Just 5801 and 5901.

(10:01:32 PM) jedijf: that's why you may need to append :1 to ip_address

(10:01:40 PM) jedijf: 192.168.1.35:1

 

(10:01:41 PM) kb3ui: everex_ip "Terminal Server Client Error - An error has occurred. VNC viewer. Unable to connect to VNC server." same as before.

(10:01:55 PM) kb3ui: Think I misunderstood you - should be 192.168.1.35:1 ?

(10:02:01 PM) jedijf: yep

 

(10:02:05 PM) kb3ui: OK

(10:02:56 PM) kb3ui: Ooh! This time it asked for a password. Then it gave me the same error.

(10:03:02 PM) kb3ui: Retrying....

(10:03:32 PM) kb3ui: Same result.

 

(10:03:50 PM) kb3ui: How does it know what logon name I'm using if I left it blank?

(10:03:59 PM) kb3ui: Password without logon ID?

(10:04:04 PM) jedijf: yep

(10:04:17 PM) kb3ui: Yep?

 

(10:04:20 PM) Prayer: I'm baack

(10:04:28 PM) jedijf: when the server was set up you only set a password to access the box

(10:04:35 PM) jedijf: maybe two passwords

(10:04:41 PM) jedijf: maybe none

 

(10:04:43 PM) kb3ui: Ah! I did! Let me try that password.

(10:12:50 PM) kb3u1 [n=ubuntu@h-68-166-177-51.phlapafg.dynamic.covad.net] entered the room.

(10:13:09 PM) Prayer: tow logins?

(10:13:27 PM) kb3u1: VncViewer must be a resource hog. I apparently had too many windows open, so it knocked me off GAIM. But it did work!

 

(10:13:44 PM) jedijf: hooray !!

(10:13:47 PM) Prayer: kb3u1 zzzzzzzzzzzz7 io

(10:13:48 PM) kb3u1: Jim, what is the meaning of 192.168.1.35:0 the 0?

(10:13:57 PM) kb3u1: zzzzzz7 io?

 

(10:14:07 PM) jedijf: port 5900 is 0 5901 is :1 etc

(10:14:09 PM) Prayer: port '0' ?

(10:14:43 PM) kb3u1: So, why is it using Port 5901 instead of 5900, as you had figured?

(10:14:56 PM) jedijf: display 0 is the x server

 

(10:15:32 PM) jedijf: want to try something neat?

(10:15:34 PM) kb3u1: and 1 is, what?

(10:15:37 PM) kb3u1: Sure!

(10:15:41 PM) jedijf: port 5901

 

(10:15:50 PM) kb3u1: 5901 is, what?

(10:15:56 PM) kb3u1: if 5900 is the x server.

(10:16:04 PM) jedijf: ok stop

(10:16:09 PM) Prayer: who's on first and what's on second ?

 

(10:16:17 PM) jedijf: when you used netsat -lant

(10:16:31 PM) jedijf: that told you what ports were listening for connection

(10:16:38 PM) jedijf: 5901 was listening

(10:16:45 PM) jedijf: that was the vnc server

 

(10:17:10 PM) kb3u1: I hear you, and understand you. But it seems to me that the process should be more transparent for the less technical user.

(10:17:13 PM) jedijf: so to connect to port 5901 we type ip_address:1 or ip_address:5901 (literal)

(10:17:40 PM) kb3u1: 192.168.1.35:5901 would work as well? Ok.

(10:18:06 PM) jedijf: the :0 :1 :2 is short for 5900 5901 5902

 

(10:18:15 PM) kb3u1: Gotcha!

(10:18:57 PM) jedijf: i can connect to all the machines in my office independently by the different 'display' :1 etc numbers

(10:19:30 PM) jedijf: from the machine you are on now dl x11vnc

(10:19:38 PM) jedijf: sudo apt-get install x11vnc

 

(10:19:57 PM) jedijf: when it is done type x11vnc -connect 151.197.56.227

(10:20:06 PM) kb3u1: Ok. Remember that I'm running virtually under VMWare.

(10:20:25 PM) jedijf: and that will send your screen to my machine

(10:20:41 PM) kb3u1: Why can't I just run the Terminal Services Client like I did to my Everex?

 

(10:20:58 PM) jedijf: your server initiates the call thru any firewall to my viewer in listen mode

(10:21:05 PM) jedijf: this is my remote support setup

(10:22:01 PM) kb3u1: Just for yucks, I'm trying it with my Terminal Services Client to see what happens.

(10:22:07 PM) jedijf: you would view my screen - this way if you need support - i can view your screen

 

(10:22:55 PM) kb3u1: Maybe I can try it on my Everex, which already has x11vnc since it now works?

(10:23:07 PM) jedijf: try it

(10:23:35 PM) kb3u1: BRB

(10:25:32 PM) kb3ui left the room (quit: Read error: 110 (Connection timed out)).

 

(10:25:54 PM) kb3u1: I'm still here! x11vnc is not installed on the everex after all. WIll now try on this machine.

(10:26:20 PM) jedijf: prolly could have used vncserver -connect 151.197.56.227

(10:27:36 PM) kb3u1: That should work. BRB

(10:31:08 PM) kb3u1: It doesn't recognize -connect as a valid option. Leaving it out it doesn't like, either.

 

(10:31:29 PM) jedijf: x11vnc works best

(10:31:44 PM) kb3u1: How do I get through firewalls?

(10:32:31 PM) jedijf: oops

(10:32:38 PM) jedijf: prolly could have used vncserver -connect 151.197.56.227:5500

 

(10:32:54 PM) jedijf: forgot the listener port :)

(10:33:00 PM) kb3u1: Ok. BRB

(10:34:40 PM) kb3u1: "Unrecognized option -connect". it then gives me a list of its options.

(10:34:56 PM) jedijf: yeah you need x11vnx

 

(10:34:59 PM) jedijf: vnc

(10:35:07 PM) jedijf: x11vnc

(10:35:30 PM) kb3u1: I will need to download and install it. Something to try for another night.

(10:35:51 PM) jedijf: yeah, i tested yesterday anticipating some remote support work

 

(10:35:59 PM) jedijf: its real convenient

(10:35:59 PM) kb3u1: But we did get the terminal services client to work on my local LAN, and that's what I wanted to accomplish.

(10:36:19 PM) kb3u1: Your help is very much appreciated!

(10:36:36 PM) jedijf: you can also try vncviewer 192.168.1.35:1 from command line ;)

 

(10:37:03 PM) kb3u1: True. That should work even easier.

(10:37:15 PM) kb3u1: How would one deal with firewalls, if necessary?

(10:37:46 PM) kb3u1: To get into your system, for example.

(10:37:50 PM) kb3u1: or you into mine.

 

(10:37:53 PM) jedijf: if you are connecting to an external site - that site needs to forward the appropriate port to the appropriate box

(10:38:49 PM) jedijf: if you install x11vnc which is server you can send your connection to me - that's what i was trying to show you - that way you don't need to configure anything

(10:39:22 PM) kb3u1: But you still have to get into my firewall?

(10:39:28 PM) jedijf: nope

 

(10:39:44 PM) jedijf: you initiated the connection out to me

(10:39:54 PM) jedijf: i just have to 'catch' it

(10:40:03 PM) jedijf: that's why it is perfect for support

(10:40:16 PM) jedijf: no configuration on your end

 

(10:40:36 PM) kb3u1: Sounds very interesting and potentially quite useful!

(10:41:45 PM) jedijf: but if you want to access everex from outside the lan all you have to do is forward port 5901 to 192.168.1.35 on your router

(10:41:58 PM) jedijf: and make sure the server is running

(10:42:18 PM) jedijf: then from any computer with vnc you can access server

 

(10:42:46 PM) jedijf: or you can setup tightvnc to serve http on port 5801 and access via any browser

(10:43:00 PM) jedijf: you did say 5801 was listening

(10:43:25 PM) jedijf: so from client open browser and in address bar type 192.168.1.35:5801

(10:43:38 PM) jedijf: on the local lan

 

(10:44:02 PM) jedijf: external_ip:5801 from outside in any browser (java enabled)

(10:44:33 PM) kb3u1: Ok. I've captured what you've said, and need to absorb and try it.

(10:44:46 PM) jedijf: after you forward 5801 on router to server

(10:45:01 PM) jedijf: you can connect to server now from firefox

 

(10:45:10 PM) kb3u1: How do I forward 5801 again? Is that through the x11vnc -connect command?

(10:45:29 PM) jedijf: no - that would be trhough your router config

(10:46:04 PM) jedijf: x11vnc -connect send your connection to someone waiting to receive it

(10:46:40 PM) kb3u1: That person has to be online. Forwarding can be done without someone there to receive it?

 

(10:47:12 PM) jedijf: stop - i think you are getting confused

(10:47:21 PM) kb3u1: Can you provide me with a reference?

(10:47:56 PM) jedijf: the -connect stuff is for YOU to get remote support from someone (whoever is at the end of the ip_address after connect)

(10:48:32 PM) jedijf: forwarding is done at your router to know when a port request comes in where on the local lan to send it

 

(10:48:55 PM) jedijf: so for example - if you want to be able to access your server from outside the lan

(10:49:29 PM) jedijf: open your router config and look for port forwarding and forward port 5901 to 192.168.1.35

(10:50:17 PM) jedijf: then with any client from anywhere - when the server is running vncserver you can access it (assuming you know your external ip_address)

(10:50:29 PM) kb3u1: Ok. Think I now understand. Will need to check with Earthlink as have no documentation on their router.

 

(10:50:47 PM) jedijf: in a browser type 192.168.1.1

(10:51:00 PM) jedijf: bet that gets to the admin page ;)

(10:51:06 PM) kb3u1: That's my router's address.

(10:51:54 PM) jedijf: that's usually where you access their web admin interface

 

(10:52:35 PM) kb3u1: Yes, that does work!

(10:53:19 PM) jedijf: what brand is the router

(10:53:21 PM) jedijf: ?

(10:53:38 PM) kb3u1: BRB

 

(10:54:27 PM) kb3u1: XyXel

(10:54:31 PM) kb3u1: Zyxel

(10:54:42 PM) kb3u1: Got the remote administration page.

(10:55:09 PM) kb3u1: Remote Management Control

 

(10:55:09 PM) kb3u1: <hr>

(10:55:09 PM) kb3u1: Server Type Access Status Port Secured Client IP Telnet All Disable LAN Only WAN Only FTP All Disable LAN Only WAN Only Web All Disable LAN Only WAN Only Â

(10:55:09 PM) kb3u1: <hr>

(10:55:10 PM) kb3u1: Â Â Â

 

(10:55:24 PM) kb3u1: Telnet, FTP, or Web.

(10:55:53 PM) jedijf: do you know model - if not try user name admin pass 1234

(10:56:12 PM) kb3u1: I already did. Had to change password to get on.

(10:56:22 PM) kb3u1: I now have the administrative page.

 

(10:56:49 PM) jedijf: poke around until you find 'port forwarding'

(10:58:51 PM) kb3u1: Don't see anything promising there. I may need to ask Earthlink Technical Support.

(10:59:21 PM) jedijf: look here for more info http://www.portforward.com/

(10:59:42 PM) jedijf: or enter model number here and we can help

 

(11:00:50 PM) jedijf: all the zyxel's are listed on the router page :)

(11:03:30 PM) kb3u1: Ok - I found it.

(11:04:03 PM) kb3u1: I will need to try this offline, unless I end up breaking my Internet connection!

(11:04:41 PM) kb3u1: Looks as if I need to download software called PFConfig.

 

(11:05:21 PM) kb3u1: No - that's only if I don't want to manuall configure it.

(11:05:25 PM) kb3u1: manually

(11:05:32 PM) kb3u1: Ok.

(11:05:57 PM) jedijf: take your time - read all the info - there is a lot of good stuff on that site

 

(11:06:14 PM) kb3u1: Looks like it! :)

(11:06:20 PM) jedijf: gotta run - time to sleep - good job russ :)

(11:06:43 PM) jedijf: and i /will/ tone down my replies - thanks for your input

(11:07:19 PM) jedijf left the room ("Time to make the donuts.").

 

(11:16:31 PM) kb3u1: Got to pay some bills, guys, so I'll see you here next week.

(11:19:14 PM) teddy-dbear: nite-nite

(11:19:53 PM) kb3u1: Good night, everyone!

(11:19:56 PM) kb3u1 left the room (quit: "Download Gaim: http://gaim.sourceforge.net/").

 

(11:20:44 PM) Norm76: Goodnight, everybody left.

(11:21:03 PM) Norm76 left the room (quit: "Leaving.").

(11:21:42 PM) burke-bear: time for this teddy bear to go to bed

(11:21:53 PM) teddy-dbear: yeah, me too

 

(11:22:29 PM) rmg: looks like chat is over, see you next week

(11:23:23 PM) burke-bear left the room (quit: "Leaving.").

(11:23:41 PM) teddy-dbear left the room (quit: "Leaving.").

---

This page has been viewed times.