Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ive just set up a compaq proliant ml370 server to act as a ipcop firewall for my home network. The network consists of 2 vista pc's and 2 xp pc's ethernet wired through a hub to the firewall. After a few initial teething problems ipcop is set up and running as I believe it is supposed to. My problem is this:
If I shut down the vista pc's for any reason and then reboot it - I lose connection to the home network. (Havent tested this yet with the xp pc's). I have access to the internet and I can access the management pages for the ipcop firewall without problem so I know its nothing to do with the firewall or the cabling. If I try to open he network and sharing center it just gives me an empty window which is locked up. If I try to diagnose the problem I get a message telling me that the facility is not available. If I leave it long enough (an hour plus) it might suddenly correct itself (as it did earlier). Im fairly sure its down to a connection issue between vista and ipcop but I hae no idea where to start. the only other way Ive been able to reestablish the connection on the network has been to take the firewall out of the loop, restablish the network then put the firewall back in. This usually allows me to then reset the network cards to resinc it with the
As you can see a most unsatisfactory situation. can anyone tell me what is going on and more importantly how to solve it? Please be aware that I hae a very limited undertanding of linux and even less of ipcop.
This sounds more like an issue with windows. Why would there be an issue with the firewall if everything is connected into the hub? They should be able to access each other directly without going through the firewall, although the firewall will still see the traffic. Is there any reason why you did not use a switch instead? Also, when you are unable to see any of the other computers in the sharing center, are you able to ping the ip addresses? Are you able to map the shares directly using Map Network Drive?
A few steps I would try:
1. Use wireshark to see what packets are getting where
2. Use ip addresses to directly access other computer shares
3. Turn off any firewalls on the pc's.
4. Downgrade from vista to xp
Ok. Ive downloaded wireshark so all I need to do now is see what info it gives me. Ive just checked the "hub" and realised it is a switch not a hub - Ive only just replaced it a day or 2 ago so its new. Ive also tuned off the firewall running on my own pc so I'll see what that does too. I hadn't thought about direct access of the ip addresses so I shall look into that one. But as for downgrading from vista to xp well its a new pc and it came supplied. I might do so when the warrenty runs out but I guess you get what you pay for. Anyway thanks for the advise. I shall monitor it when I shut down and see what happens when I reboot. Thanks
Ok I just shut down my pc and the restarted it again. Same problem as before. I started up wireshark and got the following "The NPF driver isn't running. You may have trouble capturing or lsiting interfaces". Well when I try to list the interfaces - nothing. Ive tried to map to one of the other pc's and it wont let me access them. I did notice one peculiar thing that might help. The ip address for the one I tried to access should have been 192.168.0.xx however the router is reporting it back as 192.168.1.xx . which tells me its is not picking up its ip address from the firewall. Checking my own I note that mine also is in error. And to add to my confusion th ipcop is also reporting a 192.168.1.xx number instead of 192.168.0.254. So a question arises - is the ipcop set up correctly?
 just to clarify something. From the router to the ipcop the ip should be 192.168.1.xx and from the ipcop to the clients should be set at 192.168.0.xx - at least that is what I thought I was setting up when I installed ipcop.
On IPCop admin go to Services>DHCP Server and check that the GREEN server is enabled, check the start & end addresses to confirm the range it is handing out. Then, with your PCs running, scroll down to Current dynamic leases and see if IPCop has handed all of them a lease. If not check the LAN settings on the PCs.
We are experiencing trouble with an IPCop and a Vista Business computer.
The configuration is as follows:
-green network: 4 PCs: XP Professional, Windows Server 2008, ubuntu and Vista Businesss
-red network: router
all PCs can surf outside fine, except the Vista.
network configuration is similar to all of them.
the vista can sometimes surf, and sometimes not. when packets are rejected, the logs in the firewall show the following:
MAC address: ::::::
Dst port: here the concept varies, can be '53(DOMAIN)' or '161(SNMP)' or 'ICMP'
all type of traffic is blocked. web traffic, pings to IPs, address resolution, etc
but, what is more interesting.
if we keep a continuous ping to the IPCop alive, the firewall does not drop the traffic from the vista anymore
if we stop the ping, the traffic will stop working in a few minutes, then maybe be restarted again after several tries, etc.
one last comment: both green and orange interfaces are connected to the same switch, since we are testing the equipment but, as i said before, that does not interfere with all the other PCs.
what's more, a virtualized vista business can effectively connect to the internet also.
and first of all, thanks for such a quick response.
IPCop is running version 1.4.21
Windows Vista is using static IP
However, the problem I mentioned before disappeared.
The solution was to settle the network as in a real working environment.
Originally, both router and PCs where connected in the same switch, and used different logical networks. This seemed to turn crazy the IPCop: all PCs worked fine, except the Vista.
Now, PCs are in a switch which is NOT connected to the router, so the packets must physically go through the IPCop to reach the router.
The problem now, however, is that the IPCop will crash every now and then. Yesterday it stopped working twice.
When crashing, there is no visible answer in the screen, and no response to pings. The only way to set it to work again is to physically turn it off.
There is, however, a visual indicator when this happens: leds in the switch connected to the IPCop are flashing real quick.
We are inclined to believe there might be some kind of incompatibility with the motherboard, and are thinking of trying with a different one, and reinstall IPCop, but we really don't know.