background preloader

Packet Pushers Podcast — Too Much Networking Would NEVER be Enough - Iceweasel

Packet Pushers Podcast — Too Much Networking Would NEVER be Enough - Iceweasel

Podcast - Iceweasel Welcome to the social-engineer.org podcast! The second Monday of each month we will be releasing a new and exciting episode, each with its own specific topic of the month. Episode 039 – Information Gathering on Steroids – Nov 12, 2012 Episode 038 – “Live From DerbyCon” – Oct 15, 2012 Episode 037 – “Trust Me I’m Lying” An Interview with Ryan Holiday – Sept 10, 2012 Episode 036 – LIVE from Defcon 20: Social-Engineer Anniversary – July 31, 2012 Episode 035 – Mastering Elicitation with John Nolan – June 11, 2012 Episode 034 – Beating the Polygraph – Social Engineer Style – May 14, 2012 Episode 033 – Hacking Human Behavior – April 09, 2012 Episode 032 – Non-Verbal Human Hacking – Mar 12 2012 Episode 031 – Profiling People with Social Media – Feb 13, 2012 Episode 030 – How to S.E. Episode 029 – Force Multipliers in Modern Social Engineering – Dec 12, 2011 Episode 028 – Getting Physical With Social Engineering – Nov 14, 2011 Episode 027 – No Hype NLP for Social Engineers – Oct 10, 2011

Intro to VRF lite VRFs, or VPN Routing and Forwarding instances, are most commonly associated with MPLS service providers. In such networks, MPLS encapsulation is used to isolate individual customers' traffic and an independent routing table (VRF) is maintained for each customer. Most often, MP-BGP is employed to facilitate complex redistribution schemes to import and export routes to and from VRFs to provide Internet connectivity. However, VRF configuration isn't at all dependent on MPLS (the two components just work well together). Assume the topology illustrated below is a network owned by an enterprise. All router interfaces which provide transport for both types of traffic have been configured with two subinterfaces performing 802.1Q encapsulation; .10 for VLAN 10 (blue) and .20 for VLAN 20 (red). interface FastEthernet2/0 description R2 no ip address ! If this were a generic routed network, the network admin would be busy touching up his or her resume right now. Wait a tick, what just happened?

DevOps Cafe Podcast & Videos - Show Notes InfoSec Daily | Your daily source of Pwnage, Policy and Politics. - Iceweasel Ethernet and TCP Throughput Model This is a simplified model of TCP/IP over Ethernet behaviour of a single TCP connection intended to provide insight into throughput limitations of TCP/IP due to network transit latency. In the model, TCP/IP sends the maximum TCP receive window size worth of application data (filling the maximum possible receive buffer), then waits for a single acknowledgement for the entire max. window size burst. The model also assumes that the instant the acknowledgement is sent, the data is emptied from the receive buffer and the entire window size is again fully available. Analysis assumes no lost data (no retransmits are required, no delay associated with retransmit timer waits & no ACK timer waits); All datagrams sent are maximum size; No allowance for TCP slow start algorithm delay; This results in an upper bound style result. In Basic TCP, the maximum number of bytes that can be in transit (specified by the TCP receive window size) is limited to 64KB by the 16 bit window size in the TCP header.

Webpulp TV APOVPN – Your Link Back Home - Iceweasel Packet School 101 – Part 1 « Chris Sanders ** Disclaimer to all new readers – This blog post is VERY old and not really representative of my current work. I’ve just left it up here for historical purposes. If you are interested in learning more about packet analysis I’d reccommend reading some of my newer posts or looking at my book, Practical Packet Analysis Over the course of the next few weeks I am going to be putting out a series on network traffic analysis. We won’t get into any actual packet analysis in the introductory article We will, however, go ahead and make sure we have the appropriate software to proceed, along with a brief understanding of how it works and how to use it. Getting Equipped The software we will be using for this series is the ever popular Ethereal network sniffing application. There is no actual hardware required for doing this type of analysis, however, it makes things a LOT easier if you have an old 10/100 hub lying around. Ethereal Basics Slipping On To the Wire Homework Packet School 101 – Part 2

High Scalability - High Scalability Global Public Square - CNN.com Blogs - Iceweasel

Related: