9 ms·
Falsehoods programmers believe about networks
- flukus 10y agoI would add "local networks are fast": https://people.eecs.berkeley.edu/~rcs/research/interactive_latency.html https://people.eecs.berkeley.edu/~rcs/research/interactive_l...
- chris_wot 10y agoThe IP address returned from each hop on a traceroute is from the actual device that the ICMP packet was originally sent to.
- gruturo 10y ago> The IP address returned from each hop on a traceroute is from the actual device that the ICMP packet was originally sent to. Actually - the return packets are ICMP (TTL expired in transit), but the packets you send, _by default_, are UDP. Traceroute can indeed be instructed to use ICMP though, but it's not the default on an any OS I know.
- chris_wot 10y agoI knew someone would say this. Windows not uses ICMP by default, but there is no switch to use UDP packets instead of ICMP packets.[1] Yes, I'm well aware that UDP is the default on most Unix-based systems. 1. https://technet.microsoft.com/en-us/library/cc940128.aspx https://technet.microsoft.com/en-us/library/cc940128.aspx
- rvense 10y agoIt'd be great if someone wrote three lines explaining why one would believe each of those, why it's wrong, and why that's important.
- vlodiag 10y agoYeah I agree post seems to be a bit too dry. I would like that too.
- developer2 10y agoAnd by "it'd be great", what you really mean is "the article is completely useless without them". Half of the items are "no shit"; another 20% is "huh?", and the remaining are "that might be interesting to learn more about - but with no additional information, I don't even have enough keywords to Google to find out more".
- chris_wot 10y agoYou aren't using Google effectively enough then.
- thecatspaw 10y ago>It's an internal web app -- outsiders won't be able to discover where it is (@biosshadow) explain
- chris_wot 10y agoIf it has a public IP address, it can be discovered.
- extra88 10y agoEven if it doesn't have a public ip address, its existence can be discovered if an organization's DNS isn't separated into public and private. Then there are all the ways an employee can inadvertently or intentionally make its existence public.
- chris_wot 10y agoI know. :-) all those people downvoting... and not one of them typed in the following Google search: https://www.google.com.au/search?q=discovering+internal+web+applications https://www.google.com.au/search?q=discovering+internal+web+... Leading to gems like this: https://www.verisgroup.com/2014/07/15/internal-web-application-discovery-during-post-exploitation/ https://www.verisgroup.com/2014/07/15/internal-web-applicati... And this: https://books.google.com.au/books?id=lXr0AgAAQBAJ&pg=PA429&lpg=PA429&dq=discovering+internal+web+applications&source=bl&ots=vduDFYAnwx&sig=DZ7VsIyiWwkK71u78CUb129g0fk&hl=en&sa=X&ved=0ahUKEwiGi-7kx_PPAhVMVWMKHVeoCEkQ6AEIGjAA#v=onepage&q=discovering%20internal%20web%20applications&f=false https://books.google.com.au/books?id=lXr0AgAAQBAJ&pg=PA429&l... Or even this: http://www.pentest-standard.org/index.php/Intelligence_Gathering http://www.pentest-standard.org/index.php/Intelligence_Gathe...
- asmithmd1 10y agoOne that has bitten me: "ACKs come from an end node" Cellular carriers will ACK a packet destined for a device on their network before they have actually delivered it if they have the device registered and are confident they can deliver the packet "soon." I have seen packets happily being ACKed that are destined for a device that I just powered down. About a minute later the carrier starts telling the truth, but now you have no idea what actually got through to your device.
- angry_octet 10y agoAlso: - MAC addresses are unique. - LANs won't be bridged. - Spanning tree will converge quickly. - Quickly enough that it will beat BIOS getting to DHCP for netbooting. - There will only be one circuit in the network so you can disable spanning tree. - The path MTU will be at least 1500 (or 9000, or x). - Path MTU discovery will work. - Packets with DF bit set won't be fragmented. - ICMP won't be dropped. - Network circuits will be the same path in both directions. - There will be one NIC / a default route. - The domain name 'localhost' will always resolve to localhost, or 127.0.0.1. - A DNS responder exists on the network. - It is a good idea to try to resolve IP addresses as names. - A device will use IPv4 by default (some systems opportunistically look for A and AAAA addresses and try both). - All networks have a path to the internet. - There will be no proxy required, or - The proxy won't require a login, or - The proxy credentials won't have a backslash. I'm diverging higher up the stack at this point so I'll stop.
- nieve 10y ago> MAC addresses are unique Or at least they're unique on a single machine... except for the various OSes and hardware platforms that have deliberately made all MAC addresses the same for a given machine.
- angry_octet 10y agoAh, the old weak host model quirk of Linux IP stack and helpful RHEL6 (https://technet.microsoft.com/en-us/library/2007.09.cableguy.aspx https://technet.microsoft.com/en-us/library/2007.09.cableguy...). I'm not quite sure why it came about though. One more: - There will never be more than 1000/2000/... MAC addresses per subnet.
- tonyarkles 10y agoWay back in the land before time, I acquired a number of old 486s and ISA NICs. Being a good Slashdot nerd, I of course thought "lets make a Beowulf cluster of these!" So I've got the cluster set up, and it's mostly working. There's two nodes though that behave funny. Imagine my surprise when I try pinging one of them and get two responses per ping! Sure enough, two ISA NICs pulled randomly out of a box of garbage indeed had identical MACs. I learned a lot about IP and the MAC layer from that project!
- richm44 10y agoA few more: - Localhost is 127.0.0.1 - A TCP SYN will also always result in a SYN-ACK - Ok, a SYN-ACK or a RST - Ok, ok, an out-going TCP packet will always result in a TCP response
- chris_wot 10y ago"Nobody will ever be stupid enough to stick debug data in TCP RST payloads on a production system" https://support.f5.com/kb/en-us/solutions/public/13000/200/sol13223.html https://support.f5.com/kb/en-us/solutions/public/13000/200/s...
- jjp 10y agoSeems to have missed the falsehood that everything on the network will respond really quickly and so it's fine to have loads of blocking calls on starting an application
- bogomipz 10y agoWhy is this listed under falsehood? "Bytes must be "swapped" from the network byte-order to the host CPU byte-order." Don't PowerPC and Sparc hardware require byte swapping(depending on what endian mode they are in)? Or am I misreading this?
- angry_octet 10y agoWell, NBO is big endian and PPC/Sparc/MIPS were usually BE in servers, now in routers and TVs, and LE in printers... Though POWER8 switched to LE. So you can (and I have) write programs for these BE systems that completely neglect to use swizzling. You will also see code that doesn't use the swizzling macros (htons, ntohs, etc) because they 'know' the packets need to be swizzled and they do it always, when they shouldn't on some architectures.