Thespis

Members
  • Content count

    47
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Thespis

  • Rank
    DDP Fan club member
  • Birthday 05/21/1976

Profile Information

  • Interests
    It varies, but I am somewhat of a Networking Guru. I maintain a network with over 30,000 ports, 700 switches, and 800 APs. The network backbone is a 10Gb/s link between 6 Cisco 6509's. All connected to the Internet via another 6500 that has a 1Gb/s MetroE connection. I also maintain the campus firewalls and VPNs.
  • Location
    Server Room

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Recent Profile Visitors

597 profile views
  1. Well, sorry to disappoint you, but the only people able to obtain the MAC address of that IP are the people that have a Layer 2 link to the MAC address of the computer/device that has that Layer 3 IP Address. Here's a link that might explain the difference in the different layers. If you want more information just google "osi model". http://en.wikipedia.org/wiki/OSI_model
  2. you're kidding, right?
  3. I'm with you on the dislike front. They should just call it what it is...a commercial!
  4. According to the RFC, there is no minimum length. Or a required length at all. I agree there should be. So the difference in your lengths and the padding comes from the network drivers. At least that would be my guess. Only 22 Bytes are fixed, the rest is variable. http://www.faqs.org/rfcs/rfc826.html Ethernet transmission layer (not necessarily accessible to the user): 48.bit: Ethernet address of destination 48.bit: Ethernet address of sender 16.bit: Protocol type = ether_type$ADDRESS_RESOLUTION Ethernet packet data: 16.bit: (ar$hrd) Hardware address space (e.g., Ethernet, Packet Radio Net.) 16.bit: (ar$pro) Protocol address space. For Ethernet hardware, this is from the set of type fields ether_typ$<protocol>. 8.bit: (ar$hln) byte length of each hardware address 8.bit: (ar$pln) byte length of each protocol address 16.bit: (ar$op) opcode (ares_op$REQUEST | ares_op$REPLY) nbytes: (ar$sha) Hardware address of sender of this packet, n from the ar$hln field. mbytes: (ar$spa) Protocol address of sender of this packet, m from the ar$pln field. nbytes: (ar$tha) Hardware address of target of this packet (if known). mbytes: (ar$tpa) Protocol address of target.
  5. Biosphear it's spelled marque, not mar-key. Also, vary != very. I'm sorry I couldn't sit back and watch you butcher the language anymore. Below are some dictionary entries for very and vary. As for the OP's topic, I have to agree with McGrewSecurity on this one. Learn on your own network. "Hacking" someone else's network is a good way to get arrested or sued. Or in Biosphear's case almost expelled from school. Is it really worth that? I think not.
  6. You haven't seen our ro and rw strings then. 8-P
  7. As I said, if you want to block the entire IP Range owned by that ISP, you would use: 91.0.0.0 255.240.0.0 91.16.0.0 255.248.0.0 Because they own 91.0.0.0-91.23.255.255. If you want to block just the Class B 91.0.0.0/16, then it's 91.0.0.0 255.255.0.0
  8. Yeah, there's a few of those in different classrooms around campus. Maybe not that type, but roughly the same idea.
  9. Class A is an 8bit subnet mask. Class B is a 16bit subnet mask and Class C is a 24bit subnet mask. The 17bit subnet mask you proposed would include half of the 91.0.0.0/16 subnet. 91.0.0.0 - 91.0.127.255. If you want to block everything in the Class B, then you need a 255.255.0.0 subnet mask. 91.0.0.0 255.255.0.0 If you want their entire block it's going to be more than one mask since they have more than 16 and less than 32: 91.0.0.0 255.240.0.0 91.0.0.0-91.15.255.255 91.16.0.0 255.248.0.0 91.16.0.0-91.23.255.255 There you go. On a side note, I finally found something that I know more about than McGrewSecurity. YAY!!! hahaha 9-)
  10. Again, what are you trying to do? Hamachi is encrypted by default. If you have two computers in a Hamachi network, any traffic that you send between them will be encrypted. Even across the Internet.
  11. Hamachi is a VPN, and it's already encrypted. I'm not sure what you're wanting to do. Can you be more specific?
  12. To find out more about Solaris, go to the source. http://www.sun.com/software/solaris/index.jsp By the way, if you're running Solaris x86, then I can see possibly having some issues. It's not as stable as the Sparc edition of Solaris.
  13. That's b/c it's really VI, and not VIM. In linux vi is aliased to vim. I grew up on VI, so I still hit escape after entering any text, even in vim. But considering 80% of my day to day job is done in Solaris I don't mind vi. I like it. Also, $ takes you to the end of a line. 0 takes you to the beginning. Crtl-D is page down and Crtl-U is page up. They should work in VIM also. As for the OP's question. Solaris is ROCK solid. The only time I've ever had any problem with Solaris is when hardware starts failing. The only thing you have to watch out for is that for the most part you aren't going to find installable packages. Everything is pretty much compiled. With that said, you can find binaries for Solaris. You can find good stuff at http://www.sunfreeware.com/ and http://www.blastwave.org/ .
  14. Pin Name Cable colour Description 1 VCC Red +5V 2 Dāˆ’ White Data āˆ’ 3 D+ Green Data + 4 GND Black Ground http://en.wikipedia.org/wiki/USB
  15. cr250, where are you from?