To run Wireshark on OS X you have to install X11 for some reason, and Apple has apparently stopped developing this. It is now a separate thing called XQuartz.
It seems that at some point, either some files moved or a symlink got deleted, so Wireshark won’t start. When you click it, the top menu says “Wireshark” but the user interface never appears.
To get Wireshark running do the following:
Download Quartz 2.2.7 and install it on your OS X 10.10.4 system.
Open a terminal window and enter this command to re-make the symbolic link:
sudo ln -s /opt/X11 /usr/X11
(you will need to be an admin user of the system and put in your password at this point).
Now install Wireshark and you should be good to go.
To run Wireshark on OS X you have to install X11 for some reason, and Apple has apparently stopped developing this. It is now a separate thing called XQuartz.
It seems that at some point, either some files moved or a symlink got deleted, so Wireshark won’t start. When you click it, the top menu says “Wireshark” but the user interface never appears.
To get Wireshark running do the following:
Download Quartz 2.2.7 and install it on your OS X 10.10.4 system.
Open a terminal window and enter this command to re-make the symbolic link:
sudo ln -s /opt/X11 /usr/X11
(you will need to be an admin user of the system and put in your password at this point).
Now install Wireshark and you should be good to go.
How does Internet work - We know what is networking
I found differed kinds of explanations about what that Proxy ARP is all about. After going through all of them this explanation came out. It is fairly simple technique for nodes to get MAC address of a destination host that is on the same subnet but behind a router. It’s a technique that enables our R7 router on the image below to proxy ARP request from C1 computer which tries to find MAC address of computer C3. You need to note that C1 has address from /16 range and that is why it thinks that 192.168.50.50 is the same subnet as
Here at CloudFlare we are heavy users of the github.com/miekg/dns
Go DNS library and we make sure to contribute to its development as much as possible. Therefore when Dmitry Vyukov published go-fuzz and started to uncover tens of bugs in the Go standard library, our task was clear.
Fuzzing is the technique of testing software by continuously feeding it inputs that are automatically mutated. For C/C++, the wildly successful afl-fuzz tool by Michał Zalewski uses instrumented source coverage to judge which mutations pushed the program into new paths, eventually hitting many rarely-tested branches.
go-fuzz applies the same technique to Go programs, instrumenting the source by rewriting it (like godebug does). An interesting difference between afl-fuzz and go-fuzz is that the former normally operates on file inputs to unmodified programs, while the latter asks you to write a Go function and passes inputs to that. The former usually forks a new process for each input, the latter keeps calling the function without restarting often.
There is no strong technical reason for this difference (and indeed afl recently gained the ability to behave like go-fuzz), but it's likely due to the different ecosystems in which they Continue reading
This post will give a brief overview of network configuration automation, describe its challenges and benefits and will set off a series of posts showing how to automate a configuration of a typical enterprise network.
Continue readingThe post Worth Listening: Optical for the Campus appeared first on 'net work.
Gartner has updated their networking hype cycle. Not surprisingly:
Gartner won’t give you free access to the graph, but you’ll find it in an article published on The Register.
A Dell SecureWorks survey explains how compromised sites can be used for highly selective attacks.
Big Switch, Clemson, and SDN go way back together.