Re: [leaf-user] Leaf Bering and Shorewall doc
On Thu, 2005-02-24 at 06:11, Thomas Ginestet wrote: I want to configure Shorewall on my Leaf Bering 1.2 and i've found a french (for frenchy like me) translation of documentation but it was said to better read the Shorewall LRP doc...i didn't find it anymore. The only other documentation i've found was suitable for Mandrake and Redhat. So where can i find this LRP doc ( in English or in French ) ? Or can i use others docs to configure my Shorewall ? Thomas, Did you find our guide collection? If the information isn't there, all of Jacques's Bering website was archived. http://leaf-project.org/bering/ http://leaf-project.org/doc/guide/ http://prdownloads.sourceforge.net/leaf/website_bering.tar.gz?download You may find the information you're looking for on the Shorwall site. http://shorewall.net/ -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] Leaf Bering and Shorewall doc
Mike Noyes a écrit : On Thu, 2005-02-24 at 06:11, Thomas Ginestet wrote: I want to configure Shorewall on my Leaf Bering 1.2 and i've found a french (for frenchy like me) translation of documentation but it was said to better read the Shorewall LRP doc...i didn't find it anymore. The only other documentation i've found was suitable for Mandrake and Redhat. So where can i find this LRP doc ( in English or in French ) ? Or can i use others docs to configure my Shorewall ? Thomas, Did you find our guide collection? If the information isn't there, all of Jacques's Bering website was archived. http://leaf-project.org/bering/ http://leaf-project.org/doc/guide/ http://prdownloads.sourceforge.net/leaf/website_bering.tar.gz?download You may find the information you're looking for on the Shorwall site. http://shorewall.net/ Yes, thks to all. I've find the guide that fits to my distribution...now let's rock ! ;-) Thomas ps: Larry, I didn't choose the Bering 1.2 because it was for an university project, started and gave up last year by the previous student. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Cannot understand route table output.
Dear list, I have a Bering 1.2 firewall. I have read several man pages for ip route, and they all say ~ local - the destinations are assigned to this host. The packets are looped back and delivered locally. broadcast - the destinations are broadcast addresses. The packets are sent as link broadcasts. However, several lines in the output below don't make sense, specifically: broadcast 192.168.1.0 dev eth1 table local proto kernel scope link src 192.168.1.254 broadcast 216.x.y.64 dev eth0 table local proto kernel scope link src 216.x.y.89 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 How are 192.168.1.0, 216.x.y.64 or 127.0.0.0 broadcast addresses? I can ping 216.x.y.64, and I do not get bazillions of replies (a la solaris), so it I don't think it can be a broadcast address, IMHO. Can anybody explain this to me? TIA, Rick. Background: I issued the following command: ip route list table all Which gives (in my case) table main and local. The output is: # ip route list table all 216.x.y.64/26 dev eth0 proto kernel scope link src 216.x.y.89 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254 default via 216.x.y.65 dev eth0 broadcast 216.x.y.64 dev eth0 table local proto kernel scope link src 216.x.y.89 broadcast 192.168.1.0 dev eth1 table local proto kernel scope link src 192.168.1.254 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 local 192.168.1.254 dev eth1 table local proto kernel scope host src 192.168.1.254 local 216.x.y.89 dev eth0 table local proto kernel scope host src 216.x.y.89 broadcast 192.168.1.255 dev eth1 table local proto kernel scope link src 192.168.1.254 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 broadcast 216.x.y.127 dev eth0 table local proto kernel scope link src 216.x.y.89 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 216.x.y.89 is my external static IP 216.x.y.127 is the broadcast address (/26 network) 216.x.y.65 is the default gateway I have no idea what 216.x.y.64 is --- it is in no config file on Bering -- but I can ping it. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
