In this article we are going to set up a Socks5 Proxy server using SS5 on CentOS 7. SS5 is a high performance SOCKS proxy server implementing SOCK4 and SOCKS5 protocols. As a proxy server, SS5 authenticates, profiles and processes network requests for clients. It establishes connections to application hosts for client applications.
![]()
Hi,My CentoOS 5 system panics on boot with b'Kernel panic - not syncing: Attempted to kill init!' /b (see attached screenshot).The installation is a virtual appliance, which runs within a KVM box (though I believe this to be irrelevant).The filesystem of the bricked VM appears intact. I used the rescue system to verify this as follows: I attached the CentOS ISO image to the VM's dvd drive and selected it as the boot device.
Running blinux rescue/b from the installation DVD, started successfully and detected my bricked installation, mounting it under /mnt/sysimage.Everyhing appears to be in order and looking at /mnt/sysimage/etc/inittab I can't see something wrong. I changed the default runlevel from 5 to 1 and tried to restart the system but I get the exact same error.How can I proceed in diagnosing the reason why init fails?I've attached a screenshot of the boot failure and the inittab of my bricked installation. What's weird is that I can't seem to chroot into the bricked system from the 'linux rescue' mode.
I try a 'chroot /mnt/sysimage /bin/bash' and NOTHING happens. I come back to the prompt in /tmp with chroot having done nothing. I'm begining to worry that maybe I've been infected by some sort of rootkit. Is there some Linux 'antivirus' that searches for such things? I've never been infected (at leat, no aware of being infected) so I've never looked into such things.
If this IS the case, I'd like to at least know that the system was attacked.As far as the kernel version is concerned, I tried the previous kernel with no luck. The last thing I did on this machine (guest) was a 'yum install dante' (the socks proxy).
I had just started the dante daemon and ran a 'netstat -nlpt' to check what port it's listening on. At that point netstat 'hung' and the guest (centos) became unresponsive.Meanwhile, on the host system I was installing VirtualBox and thought that it might have affected the KVM daemon which was active (running my guest).
![]()
Therefore I simply rebooted (both host and guest) and got to where I am.I have fscked the partitions and looked at various data files: everything seems to be in order.I'm currently running a partimage on the guest, to save the system partition, as I intend to re-install everything in a new VM and gradually migrate the data/configuration. It's going to be a pain, but I'm not taking any risks, as I'm worried something bad may have happened.If anybody can recommend some course of action, please do so.
I'm going to keep the old VM around, because I really want to find out what happened.
IntroductionIn this post we are going to set up a Socks5Proxy server using SS5 on CentOS 7. The twomost common types of proxies are HTTP (Hyper Text Transfer Protocol) and (SecureSockets 5). The SOCKS4 and SOCKS4a protocols do not support UDP orauthentication. The current SOCKS5 and HTTP proxies differ in the followingways:.
In general terms, the HTTP proxies can only proxy HTTP(TCP) traffic whereas a SOCKS5 proxy can handle any type of traffic usingeither TCP or UDP. A SOCKS5 proxy does not interpret the traffic sentthrough it in any way whereas an HTTP proxy typically does. This meansthat a SOCKS5 proxy is more universal and can be used with moreapplications. An HTTP proxy can only be used with HTTP clients suchas a web browser, but since it is aware of the HTTP content, it can doclever things such as caching or rewriting headers in addition to theproxying service.
![]()
For the purpose of anonymity and privacy, a SOCKS5 proxyis a better choice since it can be put to more general use. That’s all, we havesuccessfully implemented SOCKS5 Proxy Server Using SS5 on CentOS 7. As a proxyserver, SS5 authenticates, profiles and processes network requests for clients.It establishes connections to application hosts for client applications. Whenthe client attempts to access the network, the client connects to the SS5daemon instead of the application host. When the clients request that SS5perform network activities for the client the activities might includes‘Connection’, ‘Bind’ and Udp Associated authentication. The SS5 protocol isindependent of application protocols, and can assist with different networkingservices, including telnet, ftp, finger, whois, gopher, and WWW access. DMA Radius: How to repair 'Incorrect key file for tableSome times if your production server goes down due to power failure you might face below error while accessing “Connection Tracking Reports” in Radius manager.Incorrect key file for table ‘./conntrack/2017@[email protected]’.
Try to repair itFollow below mentioned steps to resolve issue.How to repair tableUbuntu?Go to database folder cd /var/lib/mysql/conntrackservice mysql stopmyisamchk -r -v -f 2017@[email protected] mysql start# don’t forgot to change table nameHow to repair tableCentos?Go to database folder cd /var/lib/mysql/conntrackservice mysqld stopmyisamchk -r -v -f 2017@[email protected] mysqld start# don’t forgot to change table name.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |