ANNOUNCEMENT: FS.COM / Fiberstore Auto-Removal in effect Networking |
- ANNOUNCEMENT: FS.COM / Fiberstore Auto-Removal in effect
- Technical debt in networking?
- MTU vs Packet size
- Source IP Address on DNS Forwarding Servers
- Multiple Public Static IPs for 1 Linux Server
- Is it ok to buy HPE/Aruba switches off of Amazon.com?
- Advice for a Search and Rescue Command Center
- What is the first class of router hardware past SOHO?
- VPNs instead of segmentation with VLANs/VRFs
- Cisco ASA with egress and ingress netflow
| ANNOUNCEMENT: FS.COM / Fiberstore Auto-Removal in effect Posted: 01 Jan 2019 11:07 AM PST The r/networking ModTeam is seeing another uptick in focused, intentional mass-marketing efforts from Fiberstore Social Media Marketing representatives. We've had this problem with them in the past, warned them extensively, banished a dozen or more accounts and here they are, back again for more. As a result of the actions of the FS.COM marketing team, (or their contracted representatives) we are auto-removing any Fiberstore makes a good product. This is a defensive action in response to their offensive and unwelcomed marketing tactics. It's a new calendar year. Please feel free to make a mention to Fiberstore sales if you are making purchases from them about their social media marketing tactics or to advise them that whoever they are contracting to handle reddit.com on their behalf may be damaging their brand more than they are helping. [link] [comments]  |
| Posted: 01 Jan 2019 10:46 AM PST Hello, I work on the image analysis side of remote sensing. I got tasked with setting up a simple queueing messaging system. As such, in reading up and deepening my knowledge I started thinking about what technical debt there is accumulated in networking as a discipline. Such as IPv4 addresses running short. Most learning sources seem to show very graceful transition from early implementations (e.g. CSMA - CSMA/CD et.c.). What do you foresee will be the biggest issues in the near future in terms of limiting current implementations? [link] [comments]  |
| Posted: 01 Jan 2019 03:04 PM PST I am new in networking stuff and been learning most of it at the job. Recently I came across an issue where an MTU is set to 1500 bytes while the packet size is around 7000 bytes, and when the ping test is performed, 0 packets are received. [link] [comments]  |
| Source IP Address on DNS Forwarding Servers Posted: 01 Jan 2019 01:16 AM PST Design: LAN -> Router -> Public DNS Forwarder -> Public DNS Resolver/Recursive On this design, there's no internal DNS service. Apparently when a client from the LAN asks for DNS response, it will be sourced by a public address from the Router via NAT/PAT. My question: When our Public DNS Forwarder forwards the recursive queries to the public DNS Recursive servers, what will the source IP Address be? I suppose it would be the public IP Address of our Public Forwarder? If it'll help, Unbound will be the choice of DNS server software in this project. If yes, to those who know, can I confirm that the traffic will be something like below: 1. Private Client to Public Forwarder Source IP: PAT Address of Router; Destination IP: Public Forwarder
Would just like to confirm the traffic esp. the addressing portions. TIA! [link] [comments]  |
| Multiple Public Static IPs for 1 Linux Server Posted: 01 Jan 2019 03:21 PM PST Hello All, We have a CentOS-7 linux box that is running a piece of web hosting software. We have three different ISPs and public static IP blocks from each of them. My linux box has 3 separate NICs. My goal is to be able to access the linux server from any of the 3 unique public static IP addresses (should one of the ISPs go down or fail). I've gone ahead and assigned a Public Static IP from each ISP to a unique NIC port on the linux server. (NIC1 = Verizon, NIC2 = Crown Castle, NIC3= Cogent) I'm having a problem getting connectivity working properly on NIC2/NIC3 and I believe this has something to do with routing tables not being configured correctly on the linux server. Anyone have experience setting up something like this? Apologies if this is trivial, I'm not very familiar with routing tables. Thanks so much [link] [comments]  |
| Is it ok to buy HPE/Aruba switches off of Amazon.com? Posted: 01 Jan 2019 03:02 PM PST I've seen may people on here recommend against buying Cisco switches on Amazon because of gray market or counterfeit hardware concern as well as lifetime warranty possibly not being honored, but what about HPE/Aruba? Should this also be a concern? I'm looking to buy a single 2930F and they are significantly cheaper than the last quote I got from our current HPE switch provider (like 1/2 price). HPE warranty has been great for me. They have even exchanged dead 3Com switches that we bought in 2010. So I have no fears about Aruba/HPE warranty coverage. [link] [comments]  |
| Advice for a Search and Rescue Command Center Posted: 01 Jan 2019 01:15 PM PST A little bit about what i'm doing: Im working on setting up the network system for a new mobile command unit for a local search and rescue team. Basically it's an enclosed trailer built out with computers and fancy equipment to act as a base for any search or rescue missions. I have some computer experience (building home computers and just tinkering) like most people on here, but never set up a network system. So here is what I kinda have drawn up in my head. They will have a few ways of getting internet in the trailer. The first way will be via a mobile hotspot (either tethering off a phone or one of those Verizon hot spot devices). The second will be via another trailer. Basically it will just feed an ethernet cable to this trailer and receive internet this way. The third will be just picking up basic wifi while the trailer is in its storage location. My first question, is there a way to easily switch where the router in the trailer is picking up internet from? Can a normal "ethernet switch" accomplish this? Or will i have a hell of a time setting it up this way? Basically i want to use one central router that can be fed multiple ways if this makes any sense at all. After it comes to a router it will just kind of act like a normal home system then. Being able to then access via the wifi and ethernet cable, have a storage system attached to it, and printers etc. Im trying to keep it kind of basic for these guys, most of them are on the older side, and tech isn't necessarily their forte. They wont need super high speed efficiency, the only real thing would be accessing google earth for some of their topographical. Also looking for recommendations for routers that are available now. [link] [comments]  |
| What is the first class of router hardware past SOHO? Posted: 01 Jan 2019 12:02 PM PST Hi, I've really been struggling to understand how a network is designed beyond the classical home office network. The typical model seems to very commonly include an IPv4/IPv6 capable router, which always performs NAT on packets received from the LAN interface destined for the Internet, and IPv6 of some sort. Lately it seems routers are working very well with doing an IA_NA and IA_PD for a /64 residential size, single IPv6 prefix to distribute amongst the LAN segment. I have had a few people ask me if I am segretating my network into multiple LAN segments, to disclude IOT devices from snooping on the laptops/NAS, or to more fully segregate guest traffic into its own area. My networking skills rather stop fully at the residential. The model above must be roughly identical to a local branch router with a few distinct office departments - let's instead of calling it LAN/IOT/Guest, simply as Finance/Sales/Engineering. With this in mind, what type of gear do you folks typically go for? Is there a "tried and true" way to design a small network with multiple L2 networks? I don't know much about Cisco IOS, but it seems reasonable that it can provide NAT across multiple networks onto a single WAN address, and we have seen plainly it supports IPv6 in almost all of its various permutations so far. I would guess that other vendors compete in this space with Cisco. So my question is hopefully not technical, but vague enough for a small discussion - what is the next form of router after the SOHO class is inadequate, for the smallest of business networks? Thanks for any insights! This is obviously a thing I want to (eventually) do but I'm happy to keep the conversation high level so that it is more interesting. [link] [comments]  |
| VPNs instead of segmentation with VLANs/VRFs Posted: 01 Jan 2019 11:30 AM PST I've been hearing recently that some people have built their networks as a sort of "visitor network only", where you don't have access to anything else than the internet + VPN gateway. Then they'd install VPN clients to every PC in the network and have them create VPN tunnels to firewall, and do segmentation/rules towards internal services there. If you don't have company PC all you get is internet access. With this you wouldn't have to do for example VRFs at every distribution switch, just configure the "visitor network" everywhere and have company PCs do VPN if they need access to something else than just the internet. Also you wouldn't need 802.1x if you're doing open visitor network anyways. Have you seen/built this kind of networks? How did you handle printers/surveillance cameras/APs/"IoT"/etc? [link] [comments]  |
| Cisco ASA with egress and ingress netflow Posted: 01 Jan 2019 08:19 AM PST I have an ASA5510 running version 8.2.5 and has netflow configured. It only captures outbound traffic netflows, i.e. egress on the outside interface. In newer versions of say 8.3 or 9.X does netflow support both egress and ingress? I know that's the case for older versions of IOS of core routers, earlier versions only did ingress, then later versions supported both egress and ingress. Unlike the IOS on routers, the netflow on the ASA is not configured to a specific interface, its global. Thanks John [link] [comments]  |
| You are subscribed to email updates from Enterprise Networking news, blogs 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