similar to: Updated bogons file

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The initial file that I uploaded was incorrect. If you downloaded a file that still contains 72.0.0.0/8 then please download again. Sorry for the confusion. 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

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

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

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

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.

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

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

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

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

Hi, I''ve a little problem, I hope so.. First a hint, I haven''t a static IP - Adress and so I used a dyndns Provider. In DMZ runs a sftp server. It should accessible from net. My router is forwarding the traffic from port 22 to the machine in DMZ. Now, in basic installation I have rfc1918-dropping configured by net interface. My problem: If rfc1918 dropping is on I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 1 Dec 2014, Ian Allison wrote: > I realize I could expand my LDAP but I'm wary of just importing some > random schema. Well, >>random<< schema ;-) you should know what you are doing. Check what is added to your LDAP and you'll be fine. > I've had mixed results doing that in the past (the qmail

IANA ups/401 was registered by Charles Bennett for "Uninterruptibe Power Supply" but I have been unable to find any details of any protocol that might have been developed. The IANA ups/401 contact address corresponds to Charles Bennett's employment by Ohio University as an IT technologist for the Chemistry and Biochemistry Departments. I believe Charles Bennet died in March

I bought a UTStarcom F1000 WiFi IP Phone from http://www.luxoncomm.com and tested it with Asterisk. This is a my first impression of the device. The F1000 supports SIP. It looks and operates like a cell phone, and connects to the Internet through WiFi, so you can use it at any WiFi hotspot. I set up a 802.11b wi-fi network with a Linksys BEFW11S4 Wireless-B broadband router with no security