Re: high performance open source DHCP solution?
* PC: If you're just fighting IOPS, another compromise might be using a ramdisk, and then committing that data to storage every x seconds. In this case, it's more straightforward to remove the fsync call from dhcpd. -- Florian Weimerfwei...@bfk.de BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
Re: high performance open source DHCP solution?
* Jimmy Hess: On Wed, Jul 20, 2011 at 9:31 AM, Nick Colton ncol...@allophone.net wrote: We were seeing similar issues with low leases, moved the dhcpd.leases file to a ramdisk and went from ~200 leases per second to something like 8,000 leases per second. Yes, blame RFC2131's requirement that a DHCP server is to ensure that any lease is committed to persistent storage, strictly before a DHCP server is allowed to send the response to the request; a fully compliant DHCP server with sufficient traffic is bound by the disk I/O rate of underlying storage backing its database. Come on, group commits are not that difficult to implement. With them, you should be able to obtain 8 kHZ leases on a single spindle (assuming the per-client data is just a few hundred bytes), without violating the RFC requirement. -- Florian Weimerfwei...@bfk.de BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
ATT Email/SMS gateway outage
Marginally operational, but I'm sure there are at least a few folks using that service as part of monitoring, so it probably bears mentioning. ATT appears to be having an email-to-SMS gateway issue. Messages sent to xxx...@txt.att.net are not being delivered to handsets. No bounce, but no delivery either. As a workaround, messages sent to xxx...@mms.att.netdo do get delivered. Confirmed in the NYC metro area and in Chicago at the moment. _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
Mac OS X Lion has DHCPv6
Just wanted to drop a note as a was pretty harsh on Apple when rumors of them not including DHCPv6 client support were floating about. In the past few days I've also seen people post that OS X doesn't have DHCPv6, because they were looking for DHCPv6 in the UI. Thankfully these reports are false. Just tried it myself on a newly upgraded Mac. Quick testing shows that when Automatic is used for the IPv6 setting, OS X will correctly look at the A, M, and O flags of an IPv6 RA and make use of DHCPv6 when instructed to. Thank you to everyone at Apple who made this happen. Especially James Woodyatt, who I gave a piratically hard time to wearing my end-user hat ;-) -- Ray Soucy Epic Communications Specialist Phone: +1 (207) 561-3526 Networkmaine, a Unit of the University of Maine System http://www.networkmaine.net/ _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
Re: Mac OS X Lion has DHCPv6
In a message written on Mon, Jul 25, 2011 at 10:50:21AM -0400, Ray Soucy wrote: Just wanted to drop a note as a was pretty harsh on Apple when rumors of them not including DHCPv6 client support were floating about. In the past few days I've also seen people post that OS X doesn't have DHCPv6, because they were looking for DHCPv6 in the UI. Thankfully these reports are false. Just tried it myself on a newly upgraded Mac. Quick testing shows that when Automatic is used for the IPv6 setting, OS X will correctly look at the A, M, and O flags of an IPv6 RA and make use of DHCPv6 when instructed to. Thank you to everyone at Apple who made this happen. Especially James Woodyatt, who I gave a piratically hard time to wearing my end-user hat ;-) I can also confirm, and even to the point where you can disable IPv4 and have a working IPv6 only client. It does DHCPv6 to get namesevers and the like, Safari works just fine for browsing IPv6 only sites, and there seem to be no hangups. Several other message boards point to a lot of changes under the hood in the Objective-C sockets classes to implement happy eyeballs. That is if a host is dual stacked and has both A and it tries both and caches which was faster and uses that for future connections. I'm unsure right now if it is just connect times, throughput, RTT, or what other metrics might be used, but apparently the result is, well, happy eyeballs. -- Leo Bicknell - bickn...@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ pgpF7dHy2Zkn0.pgp Description: PGP signature _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
Re: Mac OS X Lion has DHCPv6
On 25 Jul 2011, at 15:50, Ray Soucy wrote: Just wanted to drop a note as a was pretty harsh on Apple when rumors of them not including DHCPv6 client support were floating about. In the past few days I've also seen people post that OS X doesn't have DHCPv6, because they were looking for DHCPv6 in the UI. Thankfully these reports are false. Just tried it myself on a newly upgraded Mac. Quick testing shows that when Automatic is used for the IPv6 setting, OS X will correctly look at the A, M, and O flags of an IPv6 RA and make use of DHCPv6 when instructed to. Thank you to everyone at Apple who made this happen. Especially James Woodyatt, who I gave a piratically hard time to wearing my end-user hat ;-) +1 Running successfully on Lion with DHCPv6-supplied resolvers at the IETF meeting this week. Tim _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
USA DSL/T1 Service ?
Hello, I work for a French operator, so I know well wholesales solutions E1/Sdsl/Adsl online a few countries Europe. I am looking to find how wholesales work in the U.S., basically, we would be in New York City and would have a wholesales Dsl/T1 issued or L2TP VLAN. I tried contact operators like Qwest or AT T but impossible to have a credible interlocutor. So I posted in the nanog as I turn a little too round. Someone on the list could give me information on the techniques and the average price of trunk? Is there a solution that allows me to connect one site whatever it either the USA in Q1 was my point of presence in New York City? Thank you in advance olive _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
Re: ATT Email/SMS gateway outage
This appears to have just been restored. -- Adam Kennedy Network Engineer Omnicity, Inc. From: Drew Linsalata drew.linsal...@gmail.commailto:drew.linsal...@gmail.com Date: Mon, 25 Jul 2011 08:00:25 -0400 To: NANOG nanog@nanog.orgmailto:nanog@nanog.org Subject: ATT Email/SMS gateway outage Marginally operational, but I'm sure there are at least a few folks using that service as part of monitoring, so it probably bears mentioning. ATT appears to be having an email-to-SMS gateway issue. Messages sent to xxx...@txt.att.netmailto:xxx...@txt.att.net are not being delivered to handsets. No bounce, but no delivery either. As a workaround, messages sent to xxx...@mms.att.netdomailto:xxx...@mms.att.netdo do get delivered. Confirmed in the NYC metro area and in Chicago at the moment. _ NANOG mailing list NANOG@nanog.orgmailto:NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
Re: USA DSL/T1 Service ?
I don't think what you are after will be as feasible as it sounds like you're used to in Europe. In the US, there are _many_ different telephone companies each servicing a certain area, and they each have different policies and procedures on whether they will offer wholesale DSL in a given market. For this type of wholesale access, you will need to make arrangements with each operator in the area you want access to. I will tell you that the usage of IP/L2TP as a delivery mechanism is not as pervasive as I often hear about in other countries. In most cases, I've found telephone companies still require you to have an in-market ATM circuit to accept the handoff via PVC(s). This can get expensive, quickly, if you're trying to aggregate connections to a single POP in NYC that are not close to NYC, as you need to back haul that ATM circuit to each respective market. Additionally, FCC ruling some years back made it so the telephone companies no longer must make available wholesale access to their DSL/broadband networks, and as a result some no longer offer access to independent operators. Those on your list of potential operators that do continue to do so have had a policy of not offering new products/services to wholesale DSL customers since this ruling, which I guess is most likely for business reasons and perceived competitive threats to their own local broadband offerings. The long term availability of these services is in doubt as ADSL1 fades away. (Examples include: Qwest: No access to ADSL2 network/speeds, VDSL network/speeds. Lack/loss of wholesale access to DSL in markets not supported by ADSL1 or converted away from ADSL1. Verizon: No access to FIOS/Fiber-based services. Inability to get copper based ADSL services at a location converted to fiber.) Some, such as Verizon, also refuse to offer their wholesale solution to people not using it for resale (IE: enterprise customers), regardless of line quantities. If you wish to proceed, here are links to the appropriate provider information pages which detail their product offers and architectures: Qwest: http://www.qwest.com/wholesale/pcat/hsihostservice.html Verizon: https://www22.verizon.com/dslmembersonly/contents.jsp?show=aboutdsl ATT: Varies by market, but you can find your links here: http://www.business.att.com/wholesale/Family/ip-solutions-wholesale/dsl-transport-service-wholesale/ You may find in many cases, that contracting with a local/smaller ISP in each market who has an existing wholesale arrangement with your desired carrier in place, and asking them to deliver the services over L2TP, may be the best solution for smaller quantities of connections. Or seriously consider a VPN solution if it's more appropriate for what you are doing. On Mon, Jul 25, 2011 at 9:38 AM, Olivier CALVANO o.calv...@gmail.comwrote: Hello, I work for a French operator, so I know well wholesales solutions E1/Sdsl/Adsl online a few countries Europe. I am looking to find how wholesales work in the U.S., basically, we would be in New York City and would have a wholesales Dsl/T1 issued or L2TP VLAN. I tried contact operators like Qwest or AT T but impossible to have a credible interlocutor. So I posted in the nanog as I turn a little too round. Someone on the list could give me information on the techniques and the average price of trunk? Is there a solution that allows me to connect one site whatever it either the USA in Q1 was my point of presence in New York City? Thank you in advance olive _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
NANOG List Cutover Schedule
Hello All: We will be moving the mailing list at 12:00 PDT (GMT -7). The following is the cutover schedule and expected issues during the cutover. 1) 12:00 - move DNS for mailman.nanog.org (the MX for nanog.org) 2) 12:00 - shut down Mailman on s0.nanog.org (mailman.nanog.org) 3) 12:01 - final rsync of list data over to new server 4) 12:05 - send out a TEST message to the NANOG list 5) 12:30 - if message is not seen on list and no correctable errors are detected in the logfiles, revert to s0.nanog.org, troubleshoot, report and reschedule. If anyone has any questions or concerns please let me know. Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
TEST
This message is testing the new list server configuration. Please ignore. Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
RE: NANOG List Cutover Schedule
We are holding on this conversion at the moment and running on the existing configuration. I will update the list shortly with a revised schedule. Regards, Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) -Original Message- From: Michael K. Smith - Adhost [mailto:mksm...@adhost.com] Sent: Monday, July 25, 2011 11:44 AM To: NANOG list (nanog@nanog.org) Subject: NANOG List Cutover Schedule Hello All: We will be moving the mailing list at 12:00 PDT (GMT -7). The following is the cutover schedule and expected issues during the cutover. 1) 12:00 - move DNS for mailman.nanog.org (the MX for nanog.org) 2) 12:00 - shut down Mailman on s0.nanog.org (mailman.nanog.org) 3) 12:01 - final rsync of list data over to new server 4) 12:05 - send out a TEST message to the NANOG list 5) 12:30 - if message is not seen on list and no correctable errors are detected in the logfiles, revert to s0.nanog.org, troubleshoot, report and reschedule. If anyone has any questions or concerns please let me know. Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
NANOG List Cutover Schedule - COMPLETE
Hello: We have moved the NANOG mailing list to its new location. I've sent and received a test message successfully. If anyone is having issue after they have confirmed they have the correct DNS settings, please send me an email directly. 204.93.212.138 And 2001:1838:2001:3:2a0:d1ff:fee9:4f94 Regards, Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) -Original Message- From: Michael K. Smith - Adhost [mailto:mksm...@adhost.com] Sent: Monday, July 25, 2011 12:21 PM To: NANOG list (nanog@nanog.org) Subject: RE: NANOG List Cutover Schedule We are holding on this conversion at the moment and running on the existing configuration. I will update the list shortly with a revised schedule. Regards, Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) -Original Message- From: Michael K. Smith - Adhost [mailto:mksm...@adhost.com] Sent: Monday, July 25, 2011 11:44 AM To: NANOG list (nanog@nanog.org) Subject: NANOG List Cutover Schedule Hello All: We will be moving the mailing list at 12:00 PDT (GMT -7). The following is the cutover schedule and expected issues during the cutover. 1) 12:00 - move DNS for mailman.nanog.org (the MX for nanog.org) 2) 12:00 - shut down Mailman on s0.nanog.org (mailman.nanog.org) 3) 12:01 - final rsync of list data over to new server 4) 12:05 - send out a TEST message to the NANOG list 5) 12:30 - if message is not seen on list and no correctable errors are detected in the logfiles, revert to s0.nanog.org, troubleshoot, report and reschedule. If anyone has any questions or concerns please let me know. Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog _ NANOG mailing list NANOG@nanog.org https://mailman.nanog.org/mailman/listinfo/nanog
Change in NANOG IPv6 Address
Hello Everyone: The correct and updated IPv6 address for the NANOG list is 2001:1838::cc5d:d48a. Forward and reverse records are updated and the other address will continue to work while the DNS change propagates. Regards, Mike
