biOos
Think before you type.
With great power comes great responsibility.
IF you don´t take control of your data, someone else Will.
The only Way to Stop a Hacker is to think like One
To gain knowledge there is no shortcut
Showing posts with label Quick Notes. Show all posts
Showing posts with label Quick Notes. Show all posts
19 April 2017
04 January 2016
Quick Notes - HSRP
Use UDP as transport protocol
(IPv4) = port 1985
(IPv6) = port 2029
[Multicast address]
V1 = 224.0.0.2
V2 = 224.0.0.102
TTL = 1
[Mac Address Format]
• 0000.0C07.ACxx for HSRP version 1 for IPv4
• 0000.0C9F.Fxxx for HSRP version 2 for IPv4
• 0005.73A0.0xxx for HSRP version 2 for IPv6
xx is the group number
> High priority Wins
> Equal priority? High IPAddress Wins
biOos
(IPv4) = port 1985
(IPv6) = port 2029
[Multicast address]
V1 = 224.0.0.2
V2 = 224.0.0.102
TTL = 1
[Mac Address Format]
• 0000.0C07.ACxx for HSRP version 1 for IPv4
• 0000.0C9F.Fxxx for HSRP version 2 for IPv4
• 0005.73A0.0xxx for HSRP version 2 for IPv6
xx is the group number
> High priority Wins
> Equal priority? High IPAddress Wins
13 September 2015
Quick Notes - Clock/NTP ASA
Config
clock set 11:11:11 May 11 20XX
clock timezone XXX 3
clock summer-time XXX recurring 2 Sun Mar 2:00 1 Sun Nov 3:00
ntp authentication-key 1 md5 ***
ntp authenticate
ntp trusted-key 1
ntp server 1.1.1.1 key 1 source inside prefer
Verify
show clock detail
show ntp status
show ntp associations
clock set 11:11:11 May 11 20XX
clock timezone XXX 3
clock summer-time XXX recurring 2 Sun Mar 2:00 1 Sun Nov 3:00
ntp authentication-key 1 md5 ***
ntp authenticate
ntp trusted-key 1
ntp server 1.1.1.1 key 1 source inside prefer
Verify
show clock detail
show ntp status
show ntp associations
biOos
Quick Notes - DHCP Relay ASA
Config
conf t
dhcprelay server 1.1.1.1 dmz
dhcprelay enable inside
Verify
show dhcp relay statistics
show dhcp state
conf t
dhcprelay server 1.1.1.1 dmz
dhcprelay enable inside
Verify
show dhcp relay statistics
show dhcp state
biOos
Quick Notes - Capture traffic ASA
Put this on your tshoot belt:
conf t
capture CAPnAME interface out|inside
show capture CAPnAME
...
no capture CAPnAME interface out|inside
conf t
capture CAPnAME interface out|inside
show capture CAPnAME
...
no capture CAPnAME interface out|inside
biOos
20 February 2015
Wireshark - Quick Notes
Wireshark's most powerful feature is its vast array of display filters (over 174000 fields in 1000 protocols as of version 1.12.3). They let you drill down to the exact traffic you want to see and are the basis of many of Wireshark's other features, such as the coloring rules.
biOos
11 January 2015
Quick Notes - IPv6 RIPng
- Configure IPv6 global address
- Configure RIPng on interfaces
- Verify
[R1]
conf t ipv6 unicast-routing int f0/0 ipv6 address 2001:db8:56::1/64 ipv6 rip RIP6 enable no shut int lo0 ipv6 add 2001:db8:1::1/64 ipv6 rip RIP6 enable end
[R2]
conf t ipv6 unicast-routing int f0/0 ipv6 address 2001:db8:56::2/64 ipv6 rip RIP6 enable no shut int lo0 ipv6 add 2001:db8:2::1/64 ipv6 rip RIP6 enable end
[Verify]
R1# show ipv6 route
IPv6 Routing Table - 7 entries
...
C 2001:DB8:1::/64 [0/0]
via ::, Loopback0
L 2001:DB8:1::1/128 [0/0]
via ::, Loopback0
R 2001:DB8:2::/64 [120/2]
via FE80::200:FF:FE00:2, FastEthernet0/0
C 2001:DB8:56::/64 [0/0]
via ::, FastEthernet0/0
L 2001:DB8:56::1/128 [0/0]
via ::, FastEthernet0/0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
R1# show ipv6 int brief
FastEthernet0/0 [up/up]
FE80::200:FF:FE00:1
2001:DB8:56::1
Loopback0 [up/up]
FE80::CE00:15FF:FEFB:0
2001:DB8:1::1
R1# debug ipv6 rip
RIP Routing Protocol debugging is on R1# *Mar 1 00:17:39.635: RIPng: response received from FE80::200:FF:FE00:2 on FastEthernet0/0 for RIP6 *Mar 1 00:17:39.635: src=FE80::200:FF:FE00:2 (FastEthernet0/0) *Mar 1 00:17:39.635: dst=FF02::9 *Mar 1 00:17:39.635: sport=521, dport=521, length=52 *Mar 1 00:17:39.635: command=2, version=1, mbz=0, #rte=2 *Mar 1 00:17:39.639: tag=0, metric=1, prefix=2001:DB8:56::/64 *Mar 1 00:17:39.639: tag=0, metric=1, prefix=2001:DB8:2::/64 R1# *Mar 1 00:17:42.271: RIPng: Sending multicast update on Loopback0 for RIP6 *Mar 1 00:17:42.271: src=FE80::CE00:15FF:FEFB:0 *Mar 1 00:17:42.271: dst=FF02::9 (Loopback0) *Mar 1 00:17:42.271: sport=521, dport=521, length=72 *Mar 1 00:17:42.275: command=2, version=1, mbz=0, #rte=3 *Mar 1 00:17:42.275: tag=0, metric=1, prefix=2001:DB8:56::/64 *Mar 1 00:17:42.275: tag=0, metric=1, prefix=2001:DB8:1::/64 *Mar 1 00:17:42.275: tag=0, metric=2, prefix=2001:DB8:2::/64 *Mar 1 00:17:42.279: RIPng: Sending multicast update on FastEthernet0/0 for RIP6 *Mar 1 00:17:42.279: src=FE80::200:FF:FE00:1 R1# *Mar 1 00:17:42.279: dst=FF02::9 (FastEthernet0/0) *Mar 1 00:17:42.279: sport=521, dport=521, length=52 *Mar 1 00:17:42.279: command=2, version=1, mbz=0, #rte=2 *Mar 1 00:17:42.283: tag=0, metric=1, prefix=2001:DB8:56::/64 *Mar 1 00:17:42.283: tag=0, metric=1, prefix=2001:DB8:1::/64 *Mar 1 00:17:42.287: RIPng: Process RIP6 received own response on Loopback0 R1# unde all
R1# show ipv6 protocols
IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "static"
IPv6 Routing Protocol is "rip RIP6"
Interfaces:
Loopback0
FastEthernet0/0
Redistribution:
None
R2# ping 2001:db8:1::1 so lo0
Sending 5, 100-byte ICMP Echos to 2001:DB8:1::1, timeout is 2 seconds:
Packet sent with a source address of 2001:DB8:2::1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/28 ms
R2# show ipv6 rip
RIP process "RIP6", port 521, multicast-group FF02::9, pid 183 Administrative distance is 120. Maximum paths is 16 Updates every 30 seconds, expire after 180 Holddown lasts 0 seconds, garbage collect after 120 Split horizon is on; poison reverse is off Default routes are not generated Periodic updates 54, trigger updates 2 Interfaces: Loopback0 FastEthernet0/0 Redistribution: None
biOos
22 November 2014
Quick Notes - Bridge Protocol Data Units
BPDUs are used for root bridge election and for loop identification. By default, BPDUs are sent out every 2 seconds.
Switches use BPDUs to exchange STP information.
There are two types:
A switch sends out a BPDU on a port. The source address is the MAC address of that port and the destination address is the STP multicast address 01-80-c2-00-00-00.
The BPDU frame consists of the following fields:
biOos
Switches use BPDUs to exchange STP information.
There are two types:
- Configuration BPDUs: Used for calculating the STP
- TCN BPDUs: Used to inform about changes in the network topology
A switch sends out a BPDU on a port. The source address is the MAC address of that port and the destination address is the STP multicast address 01-80-c2-00-00-00.
The BPDU frame consists of the following fields:
- Protocol ID: Identifies the STP
- Version: Identifies the current version of the protocol
- Message type: Identifies the type of BPDU—configuration or TCN BPDU
- Flags: Used in response to a TCN BPDU
- Root bridge ID: Identifies the bridge ID of the root bridge
- Root path cost: Identifies the cost from the transmitting switch to the root
- Sender bridge ID: Identifies the bridge ID of the transmitting switch
- Port ID: Identifies the transmitting port
- Message age: Indicates the age of the current BPDU
- Maximum age: Indicates the timeout value
- Hello time: Identifies the time interval between generation of configuration BPDUs by the root
- Forward delay: Defines the time a switch port must wait in the listening and learning state
biOos
13 September 2014
Quick Notes - VTP Modes and Features
[-] VTPv1 and VTPv2 use four types of messages:
■ Summary Advertisement: This message is originated by VTP Server and Client switches every 5 minutes and, in addition, after each modification to the VLAN database. This message carries information about VTP domain name, revision number, identity of the last updater, time stamp of the last update, MD5 sum computed over the contents of the VLAN database and the
VTP password (if configured), and the number of Subset Advertisement messages that optionally follow this Summary Advertisement. Summary Advertisement messages do not carry VLAN database contents.
■ Subset Advertisement: This message is originated by VTP Server and Client switches after modifying the VLAN database. Subset Advertisements carry full contents of the VLAN database. One Subset Advertisement can hold multiple VLAN database entries. However, multiple Subset Advertisements might be required if the VLAN database is large.
■ Advertisement Request: This message is originated by VTP Server and Client switches to request their neighbors send the complete VLAN database or a part of it. Advertisement requests are sent when a VTP Client switch is restarted, when a switch enters the Client mode, or when a Server or Client switch receives a Summary Advertisement with a higher revision
number than its own.
■ Join: This message is originated by each VTP Server and Client switch periodically every 6 seconds if VTP Pruning is active. Join messages contain a bit field that, for each VLAN in the normal range, indicates whether it is active or unused (that is, pruned).
Note In any VTP version, VTP messages are transmitted and accepted only on trunk ports. Access ports neither send nor accept VTP messages. For two switches to communicate in VTP, they must first be interconnected through a working trunk link.
biOos
07 September 2014
Quick Notes - Switching Work Method
Store-and-forward
The switch fully receives all bits in the frame (store) before forwarding the frame (forward). This allows the switch to check the frame check sequence (FCS) before forwarding the frame, thus ensuring that errored frames are not forwarded.
Cut-through
The switch performs the address table lookup as soon as the Destination Address field in the header is received. The first bits in the frame can be sent out the outbound port before the final bits in the incoming frame are received. This does not allow the switch to discard frames that fail the FCS check, but the forwarding action is faster, resulting in lower latency.
Fragment-free
This performs like cut-through switching, but the switch waits for 64 bytes to be received before forwarding the first bytes of the outgoing frame. According to Ethernet specifications, collisions should be detected during the first 64 bytes of the frame, so frames that are in error because of a collision will not be forwarded.
biOos
The switch fully receives all bits in the frame (store) before forwarding the frame (forward). This allows the switch to check the frame check sequence (FCS) before forwarding the frame, thus ensuring that errored frames are not forwarded.
Cut-through
The switch performs the address table lookup as soon as the Destination Address field in the header is received. The first bits in the frame can be sent out the outbound port before the final bits in the incoming frame are received. This does not allow the switch to discard frames that fail the FCS check, but the forwarding action is faster, resulting in lower latency.
Fragment-free
This performs like cut-through switching, but the switch waits for 64 bytes to be received before forwarding the first bytes of the outgoing frame. According to Ethernet specifications, collisions should be detected during the first 64 bytes of the frame, so frames that are in error because of a collision will not be forwarded.
biOos
27 August 2014
Quick Notes - Frame Bridge/SW Flow
Decisions to forward, filter, or flood are based on the des MAC address. It is the motto of a bridge when in doubt to flood it out. However, all segments still belong to the same broadcast domain. Layer 2 and Layer 3 addresses are not changed during transmission.
NOTE
The traditional 80/20 segmentation rule says that 80 percent of the traffic should be local 20 percent remote. However, the exact opposite 20/80 rule is the typical today with high-speed backbones to support it.
biOos
26 August 2014
Quick Notes - BGP Looking Glass
“BGP Looking Glass servers are computers on the Internet running one of a variety of publicly available Looking Glass software implementations. A Looking Glass server (or LG server) is accessed remotely for the purpose of viewing routing info. Essentially, the server acts as a limited, read-only portal to routers of whatever organization is running the Looking Glass server. Typically, publicly accessible looking glass servers are run by ISPs or NOCs.”
[*] bgp-looking-glass
biOos
[*] bgp-looking-glass
biOos
25 August 2014
Quick Notes - Default Route ASA/FW
asa(config)# int gX
asa(config-int)# nameif outside
asa# show nameif
asa# conf t
asa(config)# route outside 0.0.0.0 0.0.0.0 next-hop
asa(config)# show route
biOos
24 August 2014
Quick Notes - IPv4 Multicast Address Space
Host Extensions for IP Multicasting [RFC1112] specifies the extensions
required of a host implementation of the Internet Protocol (IP) to
support multicasting. The multicast addresses are in the range
224.0.0.0 through 239.255.255.255. Address assignments are listed below.
The range of addresses between 224.0.0.0 and 224.0.0.255, inclusive, is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, such as gateway discovery and group membership reporting. Multicast routers should not forward any multicast datagram with destination addresses in this range, regardless of its TTL.
The range of addresses between 224.0.0.0 and 224.0.0.255, inclusive, is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, such as gateway discovery and group membership reporting. Multicast routers should not forward any multicast datagram with destination addresses in this range, regardless of its TTL.
[*] RFC1112
biOos
26 July 2014
07 July 2014
Subscribe to:
Posts (Atom)











