I just signed up here. I'm 17 and live in CNY. I'm not your typical IT kind of guy, and you'd never even guess I was into IT if you ever saw me. I'm currently taking the IT Systems course at Madison-Oneida BOCES. I'm due to be graduating this year and plan on joining the military in the IT field. I'm trying to further my knowledge of IT, beyond what is taught in my course. I have all(or at least most) of the basics down, such as:
-Designing/creating networks to work to full functionality
-Sub-netting networks appropriately to save the most unused address space
-Access-control lists(standard, extended, named, timed, etc.)
-DHCP Server/Client configuration
-Basic Router/Switch security

The list goes on, but I think you can figure out my technical skill from that. My teacher says I'm advanced for my class, mainly due to my accuracy and speed of configuration, but also in the understanding of the material. But there are many things I don't understand, or haven't been taught.

Before I get into the more advanced questions, I'd like to ask how I would telnet into my Linksys WRT54G on Windows Vista. I allowed remote management on the router for port 23, but it says it cannot connect to it. I'm not too concerned with that though, but if somebody would like to answer that'd be great.

1. I'd like to learn how to use bash commands/scripts. I'm not familiar with these and I'd like to learn. Is there a certain language associated with it?
2. Firewalls - Is a firewall just ACLs? Or is it more complex? I know how to configure ACLs, but I'm not completely familiar with them.
3. Proxy Servers - how do I go about setting up a proxy server? I read a little bit about setting them up on routers. How do I configure them on, say, a Cisco2600 Series Router? Am I able to set one up on a home router, such as a Linksys WRT54G with v8 Firmware?
4. VPNs - I have no knowledge on VPNs and their configuration. I know that they create a tunnel(mainly from a work computer to a home computer or something of that sort) between workstations. Could somebody explain in depth on how to configure them?
5. Hacking - I would like to get into this STRICTLY FOR EDUCATIONAL PURPOSES ONLY. I have no intention of breaking into private areas with a purpose to steal information or anything. If I'm violating a rule by asking for information regarding this, I'll delete this part of my post. But if somebody would like to explain the fundamentals of it, please do it via PM so it's not in a post where everybody can see(though I figure everybody would know that anyway).
6. I can't really think of much else to ask about, but I know there's a lot more I need to know. Anybody with any good information regarding IT/Networking, please post all that you know. I'll probably come up with some more questions, so I'll update my post if I do.

0. Is the remote management via telnet? ssh? http? 23 is normally telnet and if it's enabled and you're on the LAN you just telnet to the right IP.
1. yes, bash. Google for tutorials
2. A firewall defines what traffic can pass in which direction(s) to which host(s). I'm not familiar with ACLs.
3. Consult your router documentation. Most consumer routers aren't very modifiable unless you put custom firmware on them.
4. http://en.wikipedia.org/wiki/Virtual_private_network http://www.google.com/search?num=30&...=&oq=&gs_rfai=
6. Google/wiki/OReilly books

In general, telnet isn't safe; but, that's my opinion.

Hacking ha many different definitions. The illegal type is cracking.
You could look into John the Ripper for eeing the strength of your passwords.

No, everyone here doesn't know how to hack but a few do.

I've used aircrack-ng for testing wireless network security.

Tools such as nmap, p0f, traceroute, wireshark, xprobe, and ping for teting and for bringing down crackers, scriptkiddies, etc.

Bash scripting starts two ways: from the bottom with c or from knowing the paths and options.

Firewalls differ.
I use BSD systems; so, my firewall is more of a default deny type.

http://tldp.org/LDP/abs/html/

http://www.linuxhomenetworking.com/w...Using_iptables

I don't believe that a WRT54G supports acting as a proxy server, although I have heard about people replacing the manufacturer's firmware with a form of embedded Linux, so I suppose that this could be achieved that way.

http://tldp.org/HOWTO/Firewall-HOWTO.html

There are lots of different means of creating a virtual private network. Conceptually, you are correct; essentially a tunnel is created, joining a host, LAN, or WAN with a remote network as if it were physically part of that other network.

http://tldp.org/HOWTO/VPN-HOWTO/

http://compnetworking.about.com/od/v...nwindowsxp.htm

I don't want to teach anyone "hacking," first because I have little to no experience with it, and second because it is a term which covers a lot of different things. "Hacking" could be something as simple as modifying the source code, machine code, or language of a program or script to make it do something other than it was intended to do. Or, it could be something as complicated as writing specially-designed raw packets to exploit a vulnerability in a service daemon running on a target system, taking control of that daemon and thereby gaining it's root priviledges on that system. I will say that the best way to learn about "hacking" is to study the issue from the other side of the coin and learn about security.

LOL . . . "please post all that you know" . . . I love your energy, don't lose it. I wish I was 17 again.

Good luck, man, you've chosen a very fun, exciting, and ever-changing field.

I can't answer all your questions, but I can help with this.
Unless this router runs a telnet server, you can not telnet into it. The way to manage it, is with a web browser, on your Vista system. http://192.168.1.1 press enter. The default user is blank ( don't enter anything ) and the password is admin. Here is a link to the doc. -->http://www.linksysbycisco.com/CA/en/...RT54G/download

That is true when shipped new, but the first time you connect you should create a user and change the password. If I can find this on the net, so can any one else.

Hacking - has two meanings. One is the alteration of a system for the users benefit. The second is the bad guys, doing things to others property. As long as your purpose is the first, go for it. I don't believe there are rules against that type of thing here. Personally, I will not help anyone with the second one.

Tutorials are a great source of information. You can find them on this board, and by googleing. Give that a try for information on VPN's Firewalls, and Proxy servers. BTW, you can do all that with linux, for free....

@ camorri - yes, I've already changed the username and passwords on both of my routers, and implemented security to my wireless on both of them so unknown users can't get on them.

Let me correct myself on that part about hacking - I'm simply looking for certain tools and ways to get into my own network through open ports and security holes, so I can fix them and gain a little insight on how crackers get into a network that has security holes. I have no intent to use this information anywhere besides my own LANs and possibly at my BOCES course, if my teacher will permit it. I'm not asking for a full-on guide on how to hack my own network, just some port numbers and how I'd access them. I have the program puTTY, if that will do anything. I also have Cain and Abel and I'm not really sure how to use it.

And thank you for the guides, for some reason whenever I search for guides I always end up with ones that are very vague and don't have much detail in them.

Oh, and one more question. Can I upgrade the firmware on my router to DD-WRT firmware without it changing the actual configuration of the router? I mean, I can easily set it back up, but I don't really want to take the time. I'd like to do this:
http://lifehacker.com/178132/hack-at...o-a-600-router

I have upgraded firmware before. I have never used firmware supplied by anyone other than the manufacturer. I would say there are risks you should understand. If something goes wrong, you could wind up with a device that is a nice blue paper weight. The manufacturer will not stand behind any other firmware on the router. ie you void any warranty. I'm not saying 'don't do it', I'm saying understand the risks. Be prepared with a backup plan if something goes wrong.

If it's your router, you can call the shots. If it is not, make sure the owner understands what you are thinking of doing, and the risks.

The writer of that article bought one of the supported routers on NewEgg, so at least it was his router if something went wrong.