In this show, we discuss recent briefings we received from CloudGenix, Light Cyber, VMware, and Meru. We also go on a little rabbit trail about Brocade, because they came to mind. You know how we are.
The post Community Show – Our Briefing Review for February 2015 appeared first on Packet Pushers.
Just another advertisement for a Network Engineer…
Industry press, networking blogs, vendor marketing whitepapers and analyst reports are full of grandiose claims of benefits of whitebox switching and hardware disaggregation. Do you ever wonder whether these people actually practice their theories?
Read more ...BGP Route reflectors are used as an alternate method to full mesh IBGP and helps for scaling. BGP Route reflector clustering is used to provide redundancy in an RR design. Route Reflectors and its clients create a cluster. In an IBGP topologies, every BGP speaker has to be in a logically full mesh. Route reflectors… Read More »
The post BGP Route Reflector Clusters appeared first on Network Design and Architecture.
As a System Engineer, I do occasionally have to do real field work. When that happens, having access to a TFTP and FTP server is sometimes required. Although the [lack of] UI makes the use counterintuitive, these tools are available in OSX. This post includes the commands required to enable, confirm, and disable both TFTP and FTP in the native Mac environment.
//load the TFTP daemon (typically starts automatically) sudo launchctl load -F /System/Library/LaunchDaemons/tftp.plist //confirm that TFTP is listening (netstat) netstat -atp UDP | grep tftp --output-- udp6 0 0 *.tftp *.* //IPv6 Listening udp4 0 0 *.tftp *.* //IPv4 Listening //unload the TFTP daemon sudo launchctl unload -F /System/Library/LaunchDaemons/tftp.plist //confirm that TFTP is no longer listening (netstat) netstat -atp UDP | grep tftp --no output--
//load the FTP daemon (typically starts automatically) sudo launchctl load -w /System/Library/LaunchDaemons/ftp.plist //confirm that FTP is listening (netstat) netstat Continue reading
I recently set up a free Amazon AWS server. As I experimented with it, I installed a GUI desktop. Then I encountered some issues that I eventually resolved by creating a new user with its own password and then using that user for the rest of my activities.
For my own reference, and in the hope others will find it useful, here is the procedure I followed:
I posted the details in my blog post, below.
The default ubuntu userid does not have a password. The Amazon AWS documentation on managing users recommends creating new users with password disabled. So, why set up a new user with a password?
After installing a GUI desktop, you need to a use a password to authenticate operations performed by GUI software such as Ubuntu Software Center. I did not see any problems caused by configuring a user password. I found it was best to work in a “normal” Linux user account that has a password.