Finally, I have a website that I can just write about anything. Anything that come across my mind.
Actually I wanted to talked about why I hate how some people do their job. Some people they just simply do their job as long as it run and at the same time, I could not do that because I have to make sure that the network is up and running 24x7.
It is like politics. You could not critics, but others can critic your job. That is what we called
office politics
I mean it is not fair while you could not critic but at the same time if anything happen to what you maintain just because you simply do it like that person, you are to be pointed out. And I'm not critic because to show that I'm good in Networking but because I do know the best solution and I did not want people to give the wrong solution. Because in the end, I will be the one who have to solve it if the wrong solution fail in long term, unless if everybody know IT hands-on. And that is why I said that many people in my department are having misconception about many things and this is one of them.
I mean, if you simply think that for any project, we just make sure that it run and no need to make it as prefect or complete. And you say that the important thing for you is as long as it run. Errors, weakneasses, bugs and everything can be troubleshoot later. Well, at the same time you said that the server must be 24x7 ? And "kernel panic" is actually make the server crash. And kernel panic is also because we did not install the server properly.
Like for example using RedHat Advanced Server 2.1 with RAID 5 ? Hey RHCE out there, can you tell me whether is it stable running RHAS 2.1 with software RAID 5, and Oracle database using filesystem ext3 and at the same time, you backup from one partition to another in the same server is definitely stable ?
Believe me, we have crash 3 times at every friday and each one of them told that it is kernel panic.
And secondly, when the client DB are slow when accessing the Oracle DB in the server via a P2P, you are trying to suggest that we should take a look of what spyware that it tries to access ? I mean the internet access and the P2P is using different lease line.
I mean come on, let us try to think harder. In each client PC, you should know 3 routing table that is most important and it is sort in a way like below:-
Routing to network 192.168.21.0 using gateway 0.0.0.0
Routing to network 192.168.3.0 using gateway 192.168.21.2
Routing to network 0.0.0.0 (anywhere else), using 192.168.21.1
So, usually spyware would send information on the users PC to their company server which is located in the Internet. Let say the spyware would try to send it to gator.com.
In the Internet, these range of IPs definitely is not available anywhere because they are reserved IPs:-
- 10.0.0.0 - 10.255.255.255
- 172.16.0.0 - 172.31.255.255
- 192.168.0.0 - 192.168.255.255
(resource: http://www.iana.org/faqs/abuse-faq.htm#AllocationofIPAddresses)
Therefore, IP 192.168.3.0 would definitely not belong to any company, organization or even dinosaur in the Internet. And that's include companies that developed spywares and run the server that the spywares wanted to send those informations.
Therefore, there is no way that the spyware could be able to send anything via the P2P line.
In fact if you understand what is the reserved IPs, I don't think it would be difficult for you or anybody to understand that actually no spyware can go through the P2P line because usually P2P implementation only used private/reserverd IP such as the one aboved unless if the P2P is also using for Internet access or DNS query, which is not.
Only virus can spread through the P2P line. But that also can be minimized by configuring ACL inside the router at both P2P side, so that only port 1521 (Oracle DB) and 1383 (remote admin) can go through.
In fact, if we able to set up a firewall separate the labs and users who can access the P2P and the users who could not, I don't think any illegitimate traffic can go through. And to add more security, only users whom their PC have been configured with the correct routing can access the P2P. Users who did not, could not get any traffic go to the P2P, unless he intentionally wanted to do so.
Thus, I do not think P2P have any issues or even the client PCs.
And that is why we should concentrate the effort on troubleshooting the Oracle DB server only.
There are many other things that I wanted to explain but I think it is better if people understand first about Linux and networking before I can explain further, otherwise we will keep getting misunderstood. If you don't believe me, I am more than happy if you could asked your local IT expert on this matter.