| rrittenhouse | Cheri703: You around by chance? I've been meaning to mess with this Quassel so I can figure it out. | 16:09 |
|---|---|---|
| Cheri703 | yep, doing my "pre-workday random internet browsing" so yeah :) | 16:09 |
| rrittenhouse | same LOL | 16:09 |
| paultag | http://littlebigpants.typepad.com/little_big_pants/2011/08/365-knitting-clock.html | 16:09 |
| paultag | AWESOME | 16:09 |
| paultag | knits a scarf once a year | 16:10 |
| rrittenhouse | When I fire up Quassel Core at home, it connects to the IRC server and channels that i apparently specified somewhere. Now when I connect with Quassel Client from work (or anywhere) it joins all of the channels as a second username. Is this right? | 16:10 |
| rrittenhouse | I thought it would attach to the server session? I understand this enables it to be multi-user but I just wasn't sure if I was doing it right or not. | 16:10 |
| Cheri703 | did you install just quasselclient or quassel? | 16:11 |
| rrittenhouse | on the server it installed client and core | 16:11 |
| rrittenhouse | but on my machine at work I installed the client only | 16:12 |
| Cheri703 | hmm..you have to manually install quasselcore, not full quassel | 16:12 |
| rrittenhouse | I take that back, both are installed on here. wtf | 16:12 |
| Cheri703 | ok, yeah, that's what happened | 16:12 |
| rrittenhouse | hmm | 16:12 |
| Cheri703 | quassel is both in a standalone thing | 16:12 |
| Cheri703 | quasselcore/quasselclient are what you want | 16:12 |
| rrittenhouse | Even though Quassel Core, Quassel Client, and Quassel are listed as being installed (Windows 7) I launched Quassel Client to connect back to Quassel Core at home. That should work, no? | 16:13 |
| rrittenhouse | I didn't launch core or just "quassel" on the client PC | 16:13 |
| Cheri703 | you install quassel core and connect with the client to set it up. | 16:13 |
| rrittenhouse | on the server I launched Quassel Core | 16:13 |
| rrittenhouse | hmm ok | 16:14 |
| Cheri703 | if core is installed and you are connected to the internet, it might be running on its own | 16:14 |
| Cheri703 | so auto connecting | 16:14 |
| Cheri703 | I'd uninstall core on the client machine and see what happens | 16:14 |
| rrittenhouse | Ah ok.. let me do that. | 16:14 |
| rrittenhouse | Thanks :) brb | 16:14 |
| Cheri703 | yup :) | 16:14 |
| rrittenhouse | Cheri703: The 0.80 windows package installs everything with no choice of what to install. | 16:30 |
| Cheri703 | hmmm | 16:30 |
| * Cheri703 goes to look around | 16:30 | |
| Cheri703 | on the website it says "with core, client, and standalone client" I'm going to open up my win7 vm and poke at it | 16:31 |
| rrittenhouse | Now, I basically installed the same "all package" on the server and client. When I fire up the server it connects as rrittenhouse. Now, I don't remember setting that part up but i'm sure I did. Then on the client machine I launch Quassel Client (not quassel core or just quassel) and it has me put in my quassel core info and then after I connect it has me enter a new IRC server to connect to. I would like if it would just sync to what | 16:35 |
| rrittenhouse | the server is running. | 16:35 |
| Cheri703 | when you open quassel on the windows machine, do you click on "quassel" or on "quasselclient"? | 16:35 |
| Cheri703 | rrittenhouse: yeah, something is wonky | 16:36 |
| rrittenhouse | client | 16:36 |
| Cheri703 | I'd start by uninstalling everything everywhere. is the server linux or windows? | 16:36 |
| rrittenhouse | The other end is Windows 7 as well | 16:36 |
| Cheri703 | ahhh, ok | 16:36 |
| Cheri703 | hang on, let me explore a bit | 16:36 |
| rrittenhouse | Mainly because the ubuntu server that I had irssi+ssh on died and I've been lazy | 16:36 |
| rrittenhouse | ok | 16:36 |
| Cheri703 | do you have access to the server right now? | 16:37 |
| rrittenhouse | yeah | 16:37 |
| Cheri703 | ok, so here's what I'd suggest. uninstall on both. on the server, initiate "quasselcore" it'll pop up a command prompt and do some stuff. then open up quasselclient (from either machine, but just for a test, try it from the server), set it up with the core located at 127.0.0.1, sign in. It should take you through the "core configuration wizard". After that, reinstall on the client computer and ONLY run quasselclient. connect using the info | 16:39 |
| Cheri703 | you set up in the core configuration. ???? profit | 16:39 |
| rrittenhouse | that is what I did step for step besides I had to add a quassel user using the cmd line because no wizard came up. | 16:40 |
| rrittenhouse | but I will gladly redo it because thats the only thing that I haven't done yet :) | 16:40 |
| Cheri703 | hmmm....weird | 16:40 |
| Cheri703 | ok, yeah, try it again and see what happens, if the same thing happens, then we'll go from there :) | 16:40 |
| Cheri703 | btw, what did you use to connect this time? | 16:41 |
| rrittenhouse | lol ok... thanks :) | 16:41 |
| rrittenhouse | quassel stand alone | 16:41 |
| Cheri703 | ah, ok | 16:41 |
| === dniMretsaM_away is now known as dniMretsaM | ||
| rrittenhouse | Cheri703: Heh I think it worked. | 17:13 |
| Cheri703 | woo! | 17:14 |
| rrittenhouse | The only thing that I didn't do the same as the first time was connecting to 127.0.0.1 on the machine with the server. I connected on the server (with the client app) but I used the DNS name that I assigned to it. | 17:14 |
| rrittenhouse | which didn't run me through the setup | 17:14 |
| rrittenhouse | It did this time... Thanks for the help :) | 17:14 |
| Cheri703 | awesome :) | 17:14 |
| Cheri703 | I tend to use ip addresses when working locally, like it wouldn't even occur to me to use an assigned name | 17:15 |
| rrittenhouse | Now I need to figure out the SSL portion sometime soon. | 17:15 |
| Cheri703 | ah, yeah | 17:15 |
| rrittenhouse | I had just set it up so I was testing the name resolution | 17:15 |
| rrittenhouse | but didn't think twice about it haha | 17:15 |
| Cheri703 | :) | 17:15 |
| rrittenhouse | you might have to use the 127.0.0.1 interface to make it work the first time | 17:15 |
| rrittenhouse | IDK :) Anyhow thanks. | 17:16 |
| rrittenhouse | Going to d/c and test it now | 17:16 |
| Cheri703 | not sure. if you were connecting from a client, you might just be able to use the local server ip | 17:16 |
| Cheri703 | that's what I do | 17:16 |
| Cheri703 | ok, cool :) | 17:16 |
| rrittenhouse | still up on the server side..gonna close this too. | 17:16 |
| rrittenhouse | Awesome. Still works as it should. | 17:17 |
| rrittenhouse | Yay less productive time at work again! | 17:17 |
| Cheri703 | \o/ | 17:17 |
| rrittenhouse | Kidding of course, IRC makes me more productive. Or thats what I tell myself anyhow. | 17:17 |
| * Cheri703 ....helping destroy the productivity of others for many years now | 17:17 | |
| Cheri703 | hehe | 17:18 |
| rrittenhouse | haha | 17:18 |
| drkokandy | when I installed Quassel compiled for Windows, It installed 3 different programs - Quassel, Quassel Client, and Quassel Core. But this was on Windows 8 Pro... I've never tried installing it on Windows 7. Glad it ended up working though! | 17:46 |
| rrittenhouse | drkokandy: Cheri703: Yeah and then we suffer our first power outage at home after I get it working LOL had to boot the machine back up while I was home for lunch. | 19:58 |
| Cheri703 | heh, that sucks, but it is still working, so thats good! | 19:59 |
| rrittenhouse | Yeah it was something I did on that initial setup. Now the PC should fire up when it gets power back (good and bad). | 20:06 |
| drkokandy | whoops lol | 20:30 |
| * skellat starts throwing emergency power brick onto charge in preparation for idiot drivers who've migrated to Ashtabula and haven't driven in a "proper" snow storm before taking out a power pole or two | 23:05 | |
| paultag | aw man, why do I always miss skellat | 23:28 |
| === Cheri703_ is now known as Cheri703 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!