similar to: Updated bogons file -- Update

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 An updated bogons file is available at: http://shorewall.net/pub/shorewall/errata/2.0.8/bogons ftp://shorewall.net/pub/shorewall/errata/2.0.8/bogons Thanks to Lorenzo Martignoni for bringing the resent IANA allocations to my attention. - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \

Hi, according to: http://www.iana.org/assignments/ipv4-address-space the bogons table is outdated... tha attached patch fixes that... (done against 2.0.1) -- Regards Thomas PS. please CC me as I''m not subscribed to the list -------------- next part -------------- --- usr/share/shorewall/bogons.old 2004-04-19 18:28:00.000000000 +0300 +++ usr/share/shorewall/bogons 2004-04-20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To reflect recent allocations by the IANA, the following files are available: For Shorewall 2.0.0b and earlier: http://shorewall.net/pub/shorewall/errata/1.4.10/rfc1918 ftp://shorewall.net/pub/shorewall/errata/1.4.10/rfc1918 For Shorewall 2.0.1 and later: http://shorewall.net/pub/shorewall/errata/2.0.10/bogons

Updated rfc1918 and bogons files are now available: rfc1918 for Shorewall 2.0.0 and earlier: http://shorewall.net/pub/shorewall/errata/1.4.10/rfc1918 bogons for Shorwall 2.0.1: http://shorewall.net/pub/shorewall/errata/2.0.1/bogons Thanks go to Thomas Backlund for pointing out that the file was out of date. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool

As far as I can tell from <http://shorewall.net/errata.htm> the current shorewall bogons file is <http://shorewall.net/pub/shorewall/errata/2.0.8/bogons> which contains the line: 58.0.0.0/7 logdrop # Reserved This is incorrect. These two /8s were allocated to APNIC as of April 2004. See also <http://marc.theaimsgroup.com/?l=nanog&m=108319003517919&w=2> and the main

https://bugzilla.netfilter.org/show_bug.cgi?id=1179 Bug ID: 1179 Summary: vmap and sets cause "BUG: invalid range expression type set" Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: nft

hi: Just a litle update: 41/8 allocated to AfriNIC (APR 2005). 73/8 allocated to ARIN (MAR 2005). hope it helps.

Sorry if this is somewhat offtopic, but I''m interested in knowing how many on the list either manage or have dealt with networks in the following address blocks that have been recently assigned by ARIN: 58.0.0.0/24 59.0.0.0/24 69.0.0.0/24 through 72.0.0.0/24 82.0.0.0/24 through 88.0.0.0/24 We have recently changed ISPs and ended up with an address block in the 72.x space, which is

Hello All, I am trying to implement OpenVPN on Fedora core Linux 3 with the latest pathces installed. This server is used only as firewall/internet gateway/proxy/VPN server, with kernel 2.6.1-1.27.FC3 and kernel 2.6.1-1.27.FC3 SMP It has two NIC''s eth0 (10.0.0.150) connected to ADSL, eth1 (192.168.3.12) connected to the local network. I use shorewall 2.4 on this machine. I like to test

Hello All, I have a question about setting up the shorewall firewall for squid, I followed the instructions on "Using Shorewall with Squid" --> "Squid Running in the DMZ" section. For some reason I am unable to get the program to work. I am able to have the squid work properly by using squidclient program, but once I setup the firewall to use the redirect I am unable to

Lorenzo Martignoni at Univesita` degli Studi di Milano in Milan has established a mirror of the Shorewall web site. http://italy.shorewall.net http://cert-it.dico.unimi.it/shorewall Thanks Lorenzo! -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \

http://lists.digium.com/pipermail/asterisk-users/2003-March/008088.html "why is there such a delay in getting ipv6 rolled out when it solves all these problems ?" === There are many reasons... 1. Leasing Address Space from the I* society (small s...aka the Big Lie Society) is not desirable by all people... 2. The IPv6 Privacy Problem...that is especially important in the area of computer

------------ Forwarded Message ------------ Date: Tuesday, January 28, 2003 10:19 AM +0100 From: Lorenzo Martignoni To: Tom Eastep Subject: shorewall 1.3.13-3 I built a new debian version for shorewall-1.3.13: shorewall (1.3.13-3) unstable; urgency=high * fixed a bug in shorewall.conf: SHARED_DIR was pointing to the old location of shorewall scripts, now moved to

I would like to suggest that if we modify the IANA registration of nut/3493, we do it formally using the official IANA form https://www.iana.org/form/ports-services , and that we agree on the form contents before submitting it. For example, who is the new assignee and who is the new contact? The last thing the IANA services manager needs is to talk to an unstructured crowd of us. Roger On

No need to upgrade to this release if you already have the new bogons file or don''t use that file. The primary change is a fix to the install.sh script which previously gave an error on a new install. http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.11 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.11 Problems corrected in 2.0.11 1) The INSTALL file now include special

https://bugzilla.netfilter.org/show_bug.cgi?id=1464 Bug ID: 1464 Summary: Trying to populate a set raises a netlink error "Could not process rule: No space left on device" Product: nftables Version: unspecified Hardware: x86_64 OS: Gentoo Status: NEW Severity: normal

I tried to close everything I had open and filter as best as I could.. but left random lines in just in case it helps. 172.16.5.230 is my local machine and *.33.235 is the server. This is a slow save.. 13:48:39.852340 (60) 001F5B35DB28 Broadcast UDP - Other Ports 172.16.5.93 172.16.5.255 00:04:53.922946 293.922946 13:48:39.852605 (60) 001F5B35DB28 USC-IANA

The transport type application/ogg may now be used in applications. The IANA has assigned it in their namespace, so start adding it at will. See mail below. Linus ---------- Forwarded message ---------- Date: Mon, 10 Feb 2003 12:23:47 -0800 From: IANA <iana@iana.org> To: triad@df.lth.se Cc: Allison Mankin <mankin@psg.com>, Scott Bradner <sob@harvard.edu> Subject: RFC-to-be:

After reading this article: http://www.theregister.co.uk/2005/08/31/blocking_chinese_ip_addresses/ I got to thinking that there is really no reason for *any* traffic to hit my servers that comes from anywhere outside North America. So I wrote the perl script at the end of this posting to extract selected IP ranges posted at iana.org and convert them into iptables rules blocking any traffic

Just idly watching * in console mode and saw that someone from 50.49.54.102 tried to register with my *. whois gives:- OrgName: Internet Assigned Numbers Authority OrgID: IANA Address: 4676 Admiralty Way, Suite 330 City: Marina del Rey StateProv: CA PostalCode: 90292-6695 Country: US NetRange: 50.0.0.0 - 50.255.255.255 CIDR: 50.0.0.0/8 NetName: RESERVED-50