**** BEGIN LOGGING AT Fri Nov 20 03:00:07 2009
Nov 20 03:08:52 <slick6661> would a --complete-reprogram help?
Nov 20 03:51:04 <mwester> http://www.cyrius.com/debian/nslu2/  <------ the sum total of all nslu2/debian knowlege resides here --- not on this channel.
Nov 20 03:51:17 <mwester> Quoting from the debian/nslu2 maintainer:
Nov 20 03:51:26 <mwester> Also, please remember that this nslu2-linux list should not be used
Nov 20 03:51:27 <mwester> for Debian related questions.  Instead, use debian-arm@lists.debian.org
Nov 20 03:51:27 <slick6661> ok
Nov 20 03:51:44 <mwester> So basically, as far as the debian folks are concerned, it's debian-arm
Nov 20 03:51:51 <mwester> the fact that it's an nslu2 is not important.
Nov 20 03:52:20 <mwester> The nslu2-linux wiki lists the location of the debian-arm IRC channel, they might be able to help with the debian installer.
Nov 20 03:52:41 <mwester> Of course, if your issue is with the hardware, or flashing any other non-debian firmware, there are people here who might know about that.
Nov 20 03:52:49 <mwester> We just don't see many debian folks here.
Nov 20 03:55:07 <slick6661> I see
Nov 20 03:57:40 <slick6661> I appreciate the pointers
Nov 20 04:17:58 <slick6661> keeping this more generic
Nov 20 04:18:12 <slick6661> is there a way to completely restore the NSLU2
Nov 20 04:18:31 <slick6661> I've loaded the firmware from the linksys website
Nov 20 04:18:54 <slick6661> but it still seems to be configured like it was
Nov 20 04:44:10 <mwester> It should boot up, and the lights will reflect that it has booted -- then you follow the linksys procedure for causing the firmware to reset the network settings by holding in the reset button in some fashion -- the linksys docs tell you that.
Nov 20 04:44:20 <mwester> (I don't remember the sequence exactly)
Nov 20 04:44:43 <mwester> Then after a restart, it should show up at 192.168.1.77, the default factory settings.
Nov 20 04:46:07 <mwester> You might also run the Linksys host software and see if it can reach the device (while it's running the linksys firmware) and let you change settings.
Nov 20 04:47:51 <mwester> If none of that works, then there is a "last resort" that is documented on the nslu2-linux wiki -- use it as a last resort, it is painful and difficult to do, and if you mistype one of the digits in the command that you will be issuing to the nslu2 bootloader itself, well if you get even one digit wrong you'll brick it.
Nov 20 04:48:22 <mwester> Look for the article on resetting or clearing the sysconfig partition.  but you've been warned!
Nov 20 04:49:38 <mwester> (Frankly, it might have been easier to put a fixed IP on one of your other hosts on that address range, and use that to reconfig the device; especially if you have a linux host - real easy to move the network range about.
Nov 20 04:49:40 <mwester> )
Nov 20 04:53:31 <slick6661> ah
Nov 20 04:54:01 <slick6661> I have it set up with a linux laptop (this machine) with a crossover cable to the slug
Nov 20 04:54:37 <slick6661> after poking around I found this
Nov 20 04:54:42 <slick6661>  The verification step failed, the flash has not been written
Nov 20 04:54:42 <slick6661>  correctly (or maybe there is a bug in upslug2).  Try repeating
Nov 20 04:54:42 <slick6661>  the verification step and, if that fails for the same reason,
Nov 20 04:54:42 <slick6661>  try repeating the whole upgrade.
Nov 20 04:55:57 <mwester> well, upslug2 works, so that's probably not the issue.
Nov 20 04:56:55 <slick6661> the NSLU2 doesn't seem to reboot either
Nov 20 04:57:06 <mwester> flash is erased
Nov 20 04:57:11 <mwester> nothing to reboot into
Nov 20 04:57:33 <slick6661> perhaps one of my flashes simply didn't take
Nov 20 04:58:13 <mwester> Unusual, but possible.
Nov 20 04:58:34 <mwester> The bootloader is still there - use the resetbutton technique to re-enter the upgrade mode, and reflash again.
Nov 20 04:58:34 <slick6661> wow this slug is being a tough son of a gun tonight
Nov 20 04:58:50 <slick6661> I flashed and it was still in upgrade mode
Nov 20 04:58:55 * mwester finds that a serial console on them tames them
Nov 20 04:59:03 <slick6661> lol
Nov 20 04:59:05 <slick6661> yea
Nov 20 04:59:17 <slick6661> that might a good idea
Nov 20 04:59:21 <mwester> If the flash is sucessful, it finishes with a reset, which results in a reboot.
Nov 20 04:59:36 <slick6661> yea I thought it shoudl reboot on it's own
Nov 20 04:59:40 <mwester> If there's nothing in flash, it might (or might not) enter upgrade mode.  Worth a try.
Nov 20 04:59:46 <slick6661> ok, looks like this flash rebotted the device
Nov 20 05:00:11 <slick6661> all lights are lit so it should be all set
Nov 20 05:00:42 <mwester> If the device has become (and remains) really flakey, there have been numerous reports of the PSUs failing as they age.
Nov 20 05:01:03 <slick6661> hmmmmmmmmmm
Nov 20 05:01:04 <mwester> That can result in all sorts of issues, including inability to boot, random resets, flashing failures, etc.
Nov 20 05:01:25 <slick6661> I would imagine
Nov 20 05:01:31 <slick6661> I might bring it into work
Nov 20 05:01:45 <slick6661> we have some crack electrical engineers and equipment to test that out
Nov 20 05:03:08 <mwester> +5V @ 2A fed to it from some other PSU is the easiest way to see if starts to behave, but if you have guys at work that are willing to poke at it, well that'll work.  But you might ask them to add a serial console instead. :)
Nov 20 05:03:15 <mwester> You did de-underclock it, right?
Nov 20 05:03:23 <slick6661> nope
Nov 20 05:03:30 <slick6661> just cause I didn't want to crack it open
Nov 20 05:03:50 <slick6661> but if I'm going to do that anyway it would be worth getting the extra 133 MHz
Nov 20 05:04:00 * mwester doesn't have much around here that has a valid warantee :)
Nov 20 05:04:13 <slick6661> lol
Nov 20 05:04:56 <mwester> So is it running linksys firmware now?
Nov 20 05:05:16 <slick6661> I made the mistake programming it with the linux image again
Nov 20 05:05:28 <slick6661> so I'm doing it now
Nov 20 05:05:39 <slick6661> I just get lazy with the up arrow
Nov 20 05:06:57 <slick6661> verifying now :)
Nov 20 05:07:21 <slick6661> ok it seems to have rebooted fine
Nov 20 05:08:21 <slick6661> It gave me the beep
Nov 20 05:08:41 <slick6661> I can see all the packets on wireshark
Nov 20 05:09:13 <slick6661> but it's behaving just like the old slug
Nov 20 05:10:02 <mwester> Yep
Nov 20 05:10:16 <mwester> did you do the linksys reset procedure?
Nov 20 05:10:18 <slick6661> I don't see DHCP requests
Nov 20 05:10:24 <slick6661> um
Nov 20 05:10:25 <slick6661> no
Nov 20 05:10:31 <slick6661> did I miss a step?
Nov 20 05:10:35 <mwester> Yes.
Nov 20 05:10:38 <slick6661> doh
Nov 20 05:10:40 <mwester> You just flashed the firmware.
Nov 20 05:10:43 <slick6661> yes
Nov 20 05:11:12 <mwester> The issue is that there is an area of flash used for persistent storage of user settings; and Debian honors that area as well.  
Nov 20 05:11:13 <slick6661> so I have to press the reset button on the back?
Nov 20 05:11:20 <mwester> You need to google to find out
Nov 20 05:11:32 <mwester> I don't remember the exact duration/sequence/whatever.
Nov 20 05:11:59 * ShadowJK vaguely remembers seeing instructions in the nslu2 wiki
Nov 20 05:12:03 <mwester> I just know that if you do something with the linksys firmware running with the reset button, you can make the linksys code write the defaults back into that area of flash.
Nov 20 05:12:12 <slick6661> I already downloaded the manual
Nov 20 05:12:14 <mwester> And from there, you can recover the device's network config :)
Nov 20 05:13:07 <slick6661> oh
Nov 20 05:13:10 <slick6661> that was it
Nov 20 05:13:11 * mwester has noted this as pretty much the number one question... so perhaps a blinking red wiki page with all the details would be good for someone to write up!
Nov 20 05:13:14 <slick6661> oh damn
Nov 20 05:13:24 <slick6661> all this time I was forgetting to reset the device
Nov 20 05:13:32 <slick6661> doh doh doh
Nov 20 05:13:49 <slick6661> I need a cigarette
Nov 20 05:13:57 * mwester volunteers slick6661 to write such a page and add it to the wiki, with text sizes suited so that nobody forgets that step in the future! :D
Nov 20 05:13:57 * slick6661 doesn't smoke
Nov 20 05:14:12 <slick6661> oh you be
Nov 20 05:14:14 <slick6661> bet
Nov 20 05:14:40 <slick6661> I got to see if I can edit the debian wiki page
Nov 20 05:14:53 <slick6661> I didn't see this anywhere in the troubleshooting page
Nov 20 05:25:03 <slick6661> looks like the linux image is comming through just fine
Nov 20 05:25:41 <slick6661> and I'm already halfway through editing a wiki
Nov 20 05:28:26 <slick6661> is there a reason why the linux image doesn't reset the networking like the linksys image does?
Nov 20 05:50:03 <mwester> The reset button is wired to do a reset at the kernel level, so it's not available to user-space.
Nov 20 05:51:00 <mwester> So if you had a non-responsive device, you would hit the reset button to force the kernel to power it off immediately.
Nov 20 19:11:25 <skip89w6> I think i have successfully set up openssh on my new unslung slug, but i am not sure how to exactly connect to it from a different network. I tried using puTTY and winSCP and connect using 192.168.1.77 , but that can't be right can it because that is a local adress? my question is how to i get into my darn slug from the outside world (other networks)
Nov 20 19:12:54 <Reedy> port forward port 22 on your router
Nov 20 19:12:59 <Reedy> then use externalip:22
Nov 20 19:13:24 <Reedy> If you dont have a static ip, look at using no-ip or dyndns or similar
Nov 20 19:18:00 <skip89w6> where do i use externalip:22
Nov 20 19:18:01 <skip89w6> ?
Nov 20 19:18:31 <skip89w6> where do i look up how to use no-ip or dyndns or similar?
Nov 20 19:18:37 <skip89w6> sorry if these are dumb questions
Nov 20 19:18:53 <Reedy> well, you dont need the :22
Nov 20 19:19:00 <Reedy> But the same was as you use putty/winscp locally
Nov 20 19:19:08 <Reedy> externally, you'd use your external ip
Nov 20 19:19:15 <Reedy> http://www.no-ip.com/
Nov 20 19:19:28 <Reedy> You need to run a client to have hte ip address... What os did you install?
Nov 20 19:19:41 <skip89w6> on the slug?
Nov 20 19:20:06 <skip89w6> i installed unslung 6.x
Nov 20 19:20:32 <skip89w6> my primary computer is a mac book... but i have a windows xp boot camp partition that i run winscp on
Nov 20 19:20:55 <Reedy> lol
Nov 20 19:21:14 <skip89w6> lol yeah
Nov 20 19:21:17 <Reedy> Maybe take a look at http://www.expandrive.com/mac
Nov 20 19:21:26 <Reedy> There must be scp clients for mac
Nov 20 19:21:46 <skip89w6> there are.. i just haven't tried yet.. i was doing betting following the faw about winscp on the wiki
Nov 20 19:22:59 <skip89w6> another quick question. i formatted my 500 gb drive on disk 2 slot on the slug.. and i was getting winscp to connect and everything inside the network so i was trying to transfer files and it was working, but my space ran out because it was only around 200 mb
Nov 20 19:23:06 <skip89w6> where did all the other space go?
Nov 20 19:23:21 <Reedy> Just because you formatted it and plugged it in, doesnt mean you were using it
Nov 20 19:23:38 <skip89w6> so how do i really use it?
Nov 20 19:24:01 <skip89w6> i just want to be able to access the 500 gb hard drive from wherever i go(outside) internet
Nov 20 19:24:08 <Reedy> on optware, depending on usb ports etc, its mounted somewhere
Nov 20 19:24:38 <Reedy> you can ipkg install noip to have your nslu2 be the noip update client
Nov 20 19:25:03 <Reedy> if you ssh in, can you pastebin the output of mount please?
Nov 20 19:25:04 <skip89w6> what do you suggest i should do in what order? 
Nov 20 19:25:33 <skip89w6> right now?
Nov 20 19:25:40 <Reedy> pleasre
Nov 20 19:25:44 <Reedy> and also fdisk -l
Nov 20 19:25:52 <Reedy> then i can try and help you work out where your space is ;)
Nov 20 19:26:21 <skip89w6> ok... i'm in class right now, but i'll be back on the network of my slug in 20 minutes. will you still be around?
Nov 20 19:26:57 <Reedy> oh, heh
Nov 20 19:27:01 <Reedy> Yeah, i'll be around for a few hours
Nov 20 19:27:04 <skip89w6> how do you pastebin the output of mount?
Nov 20 19:27:13 <Reedy> type the command, press enter
Nov 20 19:27:19 <Reedy> copy and paste the text to pastebin.com
Nov 20 19:27:23 <skip89w6> what is the command?
Nov 20 19:27:25 <skip89w6> ok
Nov 20 19:28:11 <Reedy> mount
Nov 20 19:28:13 <Reedy> and also
Nov 20 19:28:15 <Reedy> fdisk -l
Nov 20 19:28:33 <skip89w6> is "mount" the actual command?
Nov 20 19:28:51 <Reedy> yup
Nov 20 19:29:12 <skip89w6> ok i will be back in 15 min. thank you reedy
Nov 20 20:00:38 <skip89w6> hey so i copied the mount into pastebin.. what do you do after that?
Nov 20 20:01:57 <skip89w6> proc on /proc type proc (rw)
Nov 20 20:01:57 <skip89w6> usbdevfs on /proc/bus/usb type usbdevfs (rw)
Nov 20 20:02:44 <skip89w6> that can't be right
Nov 20 20:04:15 <skip89w6> here is the mount: http://pastebin.com/m6694dd29
Nov 20 20:16:53 <Reedy> whats fdisk -l give?
Nov 20 20:17:00 <skip89w6> nothing
Nov 20 20:17:13 <Reedy> are you logged in as root
Nov 20 20:17:14 <Reedy> ?
Nov 20 20:17:18 <skip89w6> yeah
Nov 20 20:17:20 <skip89w6> as far as i know
Nov 20 20:17:23 <Reedy> hmm
Nov 20 20:17:28 <Reedy> right
Nov 20 20:17:29 <skip89w6> nothing comes up
Nov 20 20:17:35 <skip89w6> when fdisk
Nov 20 20:17:37 <skip89w6> -l
Nov 20 20:17:44 <Reedy> From that mount screen, your 500gb isnt mounted anywhere
Nov 20 20:18:14 <skip89w6> i see. what should i do to fix that? i thought i followed the instructions word for word when unslung'ing
Nov 20 20:18:49 <Reedy> im sure the default firmware/unslung is supposed to automount secondary drivess..
Nov 20 20:18:56 <Reedy> What are you using as your primary drive?
Nov 20 20:19:21 <skip89w6> all i have is the single 500 gb plugged into disk#2 slot
Nov 20 20:19:41 <Reedy> ahh, so you've unslung to that?
Nov 20 20:19:54 <skip89w6> yeah.. that's bad huh? 
Nov 20 20:20:00 <Reedy> not really
Nov 20 20:20:05 <skip89w6> oh?
Nov 20 20:20:07 <Reedy> just most people tend to use a small drive/usb stick
Nov 20 20:20:14 <Reedy> whats df --si tell you?
Nov 20 20:20:19 <skip89w6> ok thats what i was thinking... i can do that to
Nov 20 20:20:20 <skip89w6> hold up
Nov 20 20:20:55 <skip89w6> http://pastebin.com/me6a64a0
Nov 20 20:21:03 <Reedy> heh
Nov 20 20:21:04 <Reedy> errm
Nov 20 20:21:06 <Reedy> -h
Nov 20 20:21:17 <skip89w6> not found
Nov 20 20:21:21 <Reedy> df -h
Nov 20 20:21:22 <Reedy> iirc unslung is 2.4 kernel, so its still using the old options
Nov 20 20:21:29 <Reedy> -h was replaced with --si
Nov 20 20:21:47 <skip89w6> http://pastebin.com/m38c7dff3
Nov 20 20:22:01 <Reedy> hmm
Nov 20 20:22:08 <Reedy> whats the web interface tell you about your drive?
Nov 20 20:22:34 <skip89w6> usb prt 2: Ready, 189MB (0% FREE)
Nov 20 20:22:58 <skip89w6> i can get a hold of a small usb stick and do that real quick
Nov 20 20:53:19 <skip89w6> sorry reedy if i missed your last reply, my computer went on the fritz. where we left off was trying to figure out where my 500gb went and i said i could get a small thumb drive if need be.
Nov 20 21:16:47 <Reedy> hmm
Nov 20 21:23:07 <skip89w6> yay your back
Nov 20 21:27:49 <Reedy> must be a way to do fdisk -l (or equivalent) on unslung
Nov 20 21:28:31 <Reedy> brb
Nov 20 21:29:37 <skip89w6> ok
Nov 20 21:34:12 <mwester> fdisk -l /dev/sda works just find on unslung, Reedy...
Nov 20 21:34:37 <mwester> and if you wish to avoid the Linksys-butchered-fdisk, you can actually do /bin/busybox fdisk -l /dev/sda
Nov 20 21:34:41 <mwester> :)
Nov 20 21:34:53 <Reedy> ohh, does it just not work to do fdisk -l and it list it all?
Nov 20 21:35:16 <mwester> No - ls /dev/sd*
Nov 20 21:35:16 <skip89w6> so what should i try?
Nov 20 21:40:48 <Reedy> /bin/busybox fdisk -l /dev/sda
Nov 20 22:02:34 <skip89w6> did it here: http://pastebin.com/m1c3f8a83
Nov 20 22:04:41 <Reedy> you've got a big piece of space 26-60770
Nov 20 22:05:24 <skip89w6> so what does that mean? how do i access that space? do i need to format something?
Nov 20 22:06:00 <skip89w6> or is it good to go its just in the /dev/sda2 directory?
Nov 20 22:06:30 <Reedy> no, thats only 12 blocks
Nov 20 22:06:43 <Reedy> and its not a directory
Nov 20 22:06:44 <Reedy> in theory, just creating a partition in the space would suffice, just weird its only used the start and end of the drive
Nov 20 22:07:00 <skip89w6> so what do you suggest?
Nov 20 22:08:21 <Reedy> personally, i'd do 2 things
Nov 20 22:08:25 <Reedy> one not use unslung ;)
Nov 20 22:08:34 <skip89w6> haha ok.
Nov 20 22:08:42 <Reedy> and two, use a smaller memory stick just for the os
Nov 20 22:09:05 <skip89w6> but all the comparisons on the wiki's suggest unslung to noobs. and that is def. what i am
Nov 20 22:09:23 <Reedy> lol
Nov 20 22:09:35 <Reedy> What are you wanting to use it for?
Nov 20 22:11:30 <mwester> The wiki is really clear on the partitioning for Unslung/Linksys firmware -- you can't just create a partition there.
Nov 20 22:11:54 <mwester> The Linksys "format" utility (GUI) does far more than just format and partition the device...
Nov 20 22:12:08 <Reedy> lol
Nov 20 22:12:40 <mwester> In all likelihood the problem is that the Linksys utility could not format that drive - it probably failed (and should have said so in the GUI).  The wiki also mentions why this would be the case -- the disk is too big.
Nov 20 22:12:50 <skip89w6> alright. i am wanting to just access the 500 gb hard drive from anywhere. 
Nov 20 22:13:04 <mwester> Remember that Linksys wrote that firmware in the days when a big disk was 80GB.
Nov 20 22:13:22 <skip89w6> ok mwester, so is the 500gb no good for the slug? should i forget about it?
Nov 20 22:13:35 <Reedy> no, its not that
Nov 20 22:14:00 <skip89w6> i will def. use a small thumb drive to run the os on
Nov 20 22:14:09 <Reedy> I had a 500gb drive when running debian on mine, all fine
Nov 20 22:14:21 <skip89w6> how did u access it?
Nov 20 22:14:33 <Reedy> samba over local network
Nov 20 22:14:40 <mwester> It will work, but not very well -- you would have the prepare it by hand, and everytime it had a problem you would have to fix it with a Linux system.  The problem is that with only 32MBytes of memory, the NSLU2 can't do a filesystem check/repair of large partitions.  You could also use other firmware, and split the disk into a pair of smaller partitions.
Nov 20 22:15:01 <mwester> But before you do that, let's get to the basics:
Nov 20 22:15:07 <skip89w6> yes please
Nov 20 22:15:22 <mwester> HOW do you intend to access it over the internet?  What do you expect it to do?
Nov 20 22:16:04 <skip89w6> i want to read and write from say my home in california to my school in washington
Nov 20 22:17:40 <mwester> That's entirely too vague to be useful.
Nov 20 22:17:59 <Reedy> mwester, he
Nov 20 22:18:05 <mwester> What does read and write mean to you?   use it like a local disk drive?  point a browser at it?
Nov 20 22:18:13 <Reedy> 's currently using ssh and winscp on his local network
Nov 20 22:18:17 <Reedy> wanted to do it over the internet
Nov 20 22:18:34 <mwester> Right, ssh is using a command line to interact with it.
Nov 20 22:18:52 <mwester> Another (arcane but valid) way to read/write.
Nov 20 22:19:03 <mwester> Oh - ftp is quite do-able as well.
Nov 20 22:19:50 <skip89w6> i just want to be able to get files form it and store files when need be to it
Nov 20 22:19:51 * mwester uses VPN software running on an Unslung device, so that his home network is entirely accessable from anywhere
Nov 20 22:20:07 <skip89w6> you use it that way?
Nov 20 22:20:12 <mwester> No
Nov 20 22:20:59 <mwester> There are far better file storage devices on the market -- and frankly, I find an 8GB flash disk is a better way to move loads of data than to wait for slow networks.
Nov 20 22:21:53 <mwester> Your typical DSL line, for example, has a very slow upload speed -- so reading an 8GB file (a movie for example) from home up to the internet somewhere would take many many hours, perhaps even days.
Nov 20 22:23:38 <mwester> The slug can be made to do that sort of thing, but you have to set your expectations based on what that little device can do, and what your internet connection can really do -- and then you need to consider security as well (if YOU can get into it, how do you plan to keep others from getting into it?)
Nov 20 22:24:47 <mwester> If you'd like to try it, I would suggest that you start by unslinging to a flash drive, then add a small disk, or another flash drive.  Using that you can safely experiment, figure out what works for you and not, without dealing with the hassles that large disk will give you.
Nov 20 22:25:27 <mwester> Then when you find what works for you, you can put the drive in service.
Nov 20 22:27:34 <mwester> And by experimenting a little, you'll know how you will access it (FTP, web browser, etc) -- and it might be that you'll decide you need something other than unslung (slugos, or openwrt, for example). 
Nov 20 22:36:36 <skip89w6> alright.. that helps a lot.
Nov 20 22:37:56 <skip89w6> quick questions. what is the easiest way to be able to access the small flash drives from an outside network. i started playing with openssh and winscp and putty, but winscp won't connect to 192.168.1.77 because isn't that local to the LAN? 
Nov 20 22:38:24 <skip89w6> reedy mentioned no-ip.com which i just looked briefly at and set up an account. is that what i need to be using?
Nov 20 22:42:08 <Reedy> if you dont have a static ip, you'll need something like that
Nov 20 22:45:39 <skip89w6> so how do i use it. i know i don't have a static ip
Nov 20 22:46:10 <skip89w6> what do i do with no-ip.com 
Nov 20 22:46:57 <Reedy> sign up or an account, choose a subdomain
Nov 20 22:47:20 <Reedy> install a client that reports back to them with your current ip
Nov 20 22:49:40 <mwester> Reedy,  did you forget to mention that the router needs to have a port opened up through it?
Nov 20 22:49:49 <skip89w6> port 80 right?
Nov 20 22:49:57 <Reedy> mwester, what for?
Nov 20 22:50:19 <mwester> Connections from the internet to actually get inside the local network.
Nov 20 22:50:32 <Reedy> originally i said that yeah :)
Nov 20 22:50:40 <mwester> Oh, ok. :)
Nov 20 22:51:04 <mwester> Because I wouldn't bother with no-ip (or dyndns) until after I got it working by IP address manually.
Nov 20 22:51:07 <Reedy> I was trying to think what port no-ip duc specifically might need opening ;)
Nov 20 22:51:25 <skip89w6> so i don't need to open a port?
Nov 20 22:51:26 <mwester> And some routers actually support dyndns or no-ip out-of-the-box
Nov 20 22:51:37 <Reedy> that is true
Nov 20 22:51:52 <mwester> Yes you do need ports opened -- your firewall in your router is blocking all attempts to reach into your local network.
Nov 20 22:51:59 <Reedy> skip89w6, you WILL need to open the ssh port if you want to connect via ssh etc externally
Nov 20 22:52:20 <skip89w6> ok right. is that port 80 or something different?
Nov 20 22:52:37 <Reedy> 80 is for http
Nov 20 22:52:39 <Reedy> 22 for ssh
Nov 20 22:52:59 <skip89w6> ok
Nov 20 22:53:11 <mwester> If you do that, keep in mind that its not just you that will be connecting to that port -- there are programs that run that seem to scan for open ports, and once they find the ssh or http port open, they'll hit it with programs designed to crack your passwords and break in.
Nov 20 22:53:39 <skip89w6> so i'm screwed lol?
Nov 20 22:53:43 <Reedy> not necesseriyl
Nov 20 22:53:50 <mwester> I would give you less than a day before something will probe the ssh port, less and 4 hours before something will probe the http port.
Nov 20 22:53:59 <skip89w6> ok
Nov 20 22:54:02 <Reedy> A simple way to help reduce that is to use a non standard ssh port
Nov 20 22:54:08 <mwester> If you don't have those locked down security before you open the ports, then you will be screwed.
Nov 20 22:54:19 <skip89w6> how do you lock it down?
Nov 20 22:54:30 <Reedy> Disable root access, for a start
Nov 20 22:54:36 <Reedy> or rather, root ssh logon
Nov 20 22:54:56 <Reedy> Theres plenty of guides about that on the internet :)
Nov 20 22:55:29 <skip89w6> ok i will look into those
Nov 20 22:57:10 <skip89w6> what do you guys use your slug for?
**** ENDING LOGGING AT Sat Nov 21 02:59:57 2009