I’m supposed to come up with a DDOS preventive solution on our edge network. Need inputs Networking |
- I’m supposed to come up with a DDOS preventive solution on our edge network. Need inputs
- ICX 6610-48P does not route between VLANs
- finding a device's ip
- Which of these four books is recommended for gaining a deeper insight into the TCP/IP suite?
- Issues with ASA passing vpn traffic to next hop
I’m supposed to come up with a DDOS preventive solution on our edge network. Need inputs Posted: 04 Dec 2021 04:52 PM PST (Ours is a fairly large company equivalent to a cloud provider and we see DDOS attacks everyday and quite large as well) Existing conditions:
We still see a lot of spoofed attacks. My manager and his manager are half convinced that we need to implement uRPF (BCP38) on our edge routers and asked me to design/implement this solution. The goal is that we avoid spoofed attacks instead of trying to mitigate them.
Loose uRPF wont work because we have almost the entire ipv4 internet prefixes in our rib.
Some other things: We pretty much have the entire internet (ipv4 prefixes) in our edge routers RIB. We use juniper ptx. Im sure I didn't include all the info you need to give me an input since there is so much info, so please do ask whats needed and I'll reply in the comments or update the post. [link] [comments] |
ICX 6610-48P does not route between VLANs Posted: 04 Dec 2021 12:17 PM PST Hi all, EDIT1: Placing the 192.168.21.2 on a different VLAN than VLAN 1 allows me to ping between VLANs. I don't use VLAN 1, but would still like to know why that is even though the problem is effectively solved. EDIT2 (ISSUE SOLVED): u/417SKCFAN solved the issue in the comments. VLAN 1 acts differently than in Cisco land, and I would have to set my native VLAN in order to use it. Thank you all for the help! I am transitioning over from Cisco to Brocade, and I am having some confusion. I added my VLANs, added router interfaces to each of them, and added my ports. I am able to ping connected devices from my switch, but am unable to ping the devices from devices in other VLANs, and it doesn't seem to be routing the traffic between them. Say I have a device in vlan 1 (192.168.21.2), I can't ping the device in VLAN 2 (200.1.1.2) from that first device, while the switch is able to ping both. I also can't ping any of my router interfaces from (192.168.21.2). How do I get the switch to route between my VLANs? Do I have to enable routing? (I read that all you need is the correct firmware). My show ip interface, shows that all router interfaces are part of default-vrf. Do I have to create a VRF? Thanks for the help! show flash: show ip route: show ip interface: show run: [link] [comments] |
Posted: 04 Dec 2021 08:49 AM PST Hello! I was wondering if anyone knew of a way to find a devices ip address by directly connecting to its ethernet port. I have a mac directly connected to a NVR id like to get the ip address from to do some configuration to. I was going to try Wireshark but i believe it requires me to know the subnet that it is on (i dont have that information). [link] [comments] |
Which of these four books is recommended for gaining a deeper insight into the TCP/IP suite? Posted: 04 Dec 2021 06:29 PM PST I would like to gain a deeper insight into the TCP/IP suite. I've seen four books recommended. I don't wish to read them all, as they will most likely have overlapping knowledge. The books are:
Which of these four should I get? Thank you. [link] [comments] |
Issues with ASA passing vpn traffic to next hop Posted: 03 Dec 2021 03:45 PM PST I have an ASA with a vpn tunnel on it. That tunnel has a network object-group in its encryption domain with 14 addresses in it. Of these 14 destinations, 12 pass traffic onto the directly connected next hop firewall, and 2 do not reach the next hop. I verified routing for each address and they are all the same, and no ACL is blocking the traffic. I tried deleting and re-adding the two addresses to the object-group. Any ideas? I am able to bring up the tunnel using packet tracer to initiate traffic on those IPs, so the IPs aren't missing from the other side. [link] [comments] |
You are subscribed to email updates from Enterprise Networking Design, Support, and Discussion. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States |
No comments:
Post a Comment