freddy333 Posted October 7, 2016 Report Share Posted October 7, 2016 How do I disconnect foreign IP tcp connections on a BSD UNIX server? I know there is a command (tcpdrop or something like that???) that does this, but I cannot remember what it is or how to use it? Although they do not appear to have actually logged-in or gained access, I am seeing a great deal of unusual activity on a server that generally sees very little activity. A who or w shows I am the only person logged-in, but netstat reveals 2 foreign IPs that should not be there Link to comment Share on other sites More sharing options...
docthor Posted October 7, 2016 Report Share Posted October 7, 2016 @nikki6 ...maybe you can help here? The thing I'd do is to restart the interface (if no production server) and check if they'll show up again.Sent from my wooden drums via Tupperware Link to comment Share on other sites More sharing options...
Sogeha Posted October 7, 2016 Report Share Posted October 7, 2016 ^^^switch off and on again LOL^^^ First piece of advice from any IT help desk. Link to comment Share on other sites More sharing options...
freddy333 Posted October 7, 2016 Author Report Share Posted October 7, 2016 Thanks, but I am ahead of you. I finally got rid of them by rebooting the server and blocking them via the firewall, but I know there is a much simpler/quicker way to disconnect an IP (via tcpdrop or similar?) in real-time & without having to stop the network or reboot. Anyone? Link to comment Share on other sites More sharing options...
imajedi Posted October 7, 2016 Report Share Posted October 7, 2016 Did you try tcpkill Link to comment Share on other sites More sharing options...
freddy333 Posted October 7, 2016 Author Report Share Posted October 7, 2016 No, but I will give it a try. How is it used? Can you post a sample command line for a single IP address? Also, it may be a Linux command as I do not think it is installed on our BSD server. Link to comment Share on other sites More sharing options...
imajedi Posted October 7, 2016 Report Share Posted October 7, 2016 $ sudo tcpkill -i wlan0 host 192.168.1.214-h is help for most commands. Try tcpkill -h to see all the optionshttps://en.m.wikipedia.org/wiki/Tcpkill 1 Link to comment Share on other sites More sharing options...
freddy333 Posted October 7, 2016 Author Report Share Posted October 7, 2016 That looks like what I need, but unfortunately it is not installed. I will have to see if there is a version for BSD. Thank you. Link to comment Share on other sites More sharing options...
cib0rgman Posted October 7, 2016 Report Share Posted October 7, 2016 turn off the interface and turn it on, something like ifconfig eth0 down ifconfig eth0 up Link to comment Share on other sites More sharing options...
freddy333 Posted October 7, 2016 Author Report Share Posted October 7, 2016 Thanks, but that is 1 of the 1st things I tried (unsuccessfully). Link to comment Share on other sites More sharing options...
imajedi Posted October 8, 2016 Report Share Posted October 8, 2016 That looks like what I need, but unfortunately it is not installed. I will have to see if there is a version for BSD. Thank you.It's it the dnssniff package in Linux. Not sure if that helps for BSD Link to comment Share on other sites More sharing options...
RickFlorida Posted October 10, 2016 Report Share Posted October 10, 2016 What is the usefulness or purpose of Unix server? Link to comment Share on other sites More sharing options...
imajedi Posted October 10, 2016 Report Share Posted October 10, 2016 What is the usefulness or purpose of Unix server?Security and reliability are the two main advantages over windows if that's what you're asking Link to comment Share on other sites More sharing options...
Nanuq Posted October 10, 2016 Report Share Posted October 10, 2016 And true multi threading with process persistence.Translation: UNIX is a tool and Windows is a toy. 1 Link to comment Share on other sites More sharing options...
Sogeha Posted October 10, 2016 Report Share Posted October 10, 2016 1 hour ago, Nanuq said: And true multi threading with process persistence. Translation: UNIX is a tool and Windows is a toy. I prefer toys that work, so none of mine run Windoze Windows is based on MS DOS MS DOS is based on QDOS which stands for quick and dirty operating system. It was and still is a hacked together bodge job. The kernel is still not stable after 36 years. Hence operation critical machines tend to,avoid using it. Link to comment Share on other sites More sharing options...
RickFlorida Posted October 10, 2016 Report Share Posted October 10, 2016 (edited) I remember last year an airport traffic control was crippled because no one could work on the old windows 3.1 or some early version. So it sounds like the old windows was used by critical operations like air traffic control. Edited October 10, 2016 by RickFlorida Link to comment Share on other sites More sharing options...
Sogeha Posted October 10, 2016 Report Share Posted October 10, 2016 Lots of industrial stuff uses windows NT, especially for event loggers and data servers. I would think keeping aircraft in the air would be a good example of where to use redundancy: two or more different operating systems each using different software, nothing happens unless the outputs on all systems are the same. If not a warning is flashed up and the system is halted, paused or put into a loop in a safe state. Personally I just don't trust windows not to freeze, glitch, loose data or go blue screen. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now