Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a feeling I'm missing something simple, but I just can't see what it is.
I am trying to set up my linux box (FC3) to do a bunch of server functions (Samba, FTP, Apache) Doing one thing at a time, I have Samba up and running with no problems except that I can't get threw the firestarter wall. I need to get this wall working correctly before I remove the firewall on my router. (All three computers have their own walls that are more configurable than the router one)
DHCP is running on the network assigning IP's above 192.168.1.100 255.255.255.0 and up I've configured firestarter on the policy page to allow the SAMBA service to 192.168.1.100//27. If I'm right this should allow 30 addresses starting at 192.168.1.100 to use the Samba service. The problem is when I apply the policy, and then restart the firewall, all access is blocked. If I stop the firewall, all is well again.
Any help is appreaciated, and I'll provide any information that I can.
Originally posted by peter_robb I'm not sure how well firestarter interprets bad subnet numbering..
192.168.1.128 is the end of a subnet..
You will have to find another way of entering that range of numbers, eg 192.168.1.100-129
Thanks for the input, I can easily change my DHCP service to give out lower addresses, say 192.168.1.10 to .40. Or I could modify the policy, to something like 192.168.1.100/28 which off the top of my head would allow addresses between .100 - .106 (But I think I've tried that...)
In anycase, thanks for the reply, I'll do some more testing when I get off work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.