Re: Nat

[Doug Barton]

On 12/19/2015 07:17 AM, Sander Steffann wrote:

Hi Jeff,


It's far past time to worry about architectural purity.  We need people
deploying IPv6 *NOW*, and it needs to be the job of the IETF, at this
point, to fix the problems that are causing people not to deploy.


I partially agree with you. If people have learned how IPv6 works, deployed IPv6 (even if 
just in a lab) and came to the conclusion that there is an obstacle then I very much want 
to hear what problems they ran into. That's rarely the case unfortunately. Most of the 
time I hear "we don't want to learn something new".


A) You don't need to deploy something to see that the design is overly 
complex, and not a good fit for existing, well-entrenched workflows.


B) Many people have done this, and provided the exact feedback you 
describe, for well over a decade.


There is no technical reason that IPv6 cannot have full-featured DHCP. 
The only obstacles are the purists like you who insist on the entire 
installed base coming up to speed with their cleverness. All the user 
education in the world will not fix that problem.

Re: CPE that supports 464XLAT

[Ca By]

On Thursday, January 7, 2016, Daniel Corbe  wrote:

> Anyone out there aware of any DOCSIS 3.0 cable modems that have a working
> CLAT implementation?
>
>
Not modems, but home gateway routers

NEC has a product  http://www.necat.co.jp/en/ipv6/index.html

And it is supported in openwrt

Re: GPON vs. GEPON

[Carlos Alcantar]

At this point if you haven't deployed any of these system, make sure you know 
the road map of your vendor for N-GPON2 that is going to be the next wave of 
deployed pon systems.



https://www.calix.com/solutions/next-generation-pon.html


​
Carlos Alcantar
Race Communications / Race Team Member
1325 Howard Ave. #604, Burlingame, CA. 94010
Phone: +1 415 376 3314 / car...@race.com / http://www.race.com



From: NANOG  on behalf of Baldur Norddahl 

Sent: Wednesday, January 6, 2016 8:30 AM
To: nanog@nanog.org
Subject: Re: GPON vs. GEPON

The solution for selling 1G internet with EPON could be 10GEPON. This is
still cheaper than GPON. The idea is that the ONU has a cheap standard 1G
transmitter. Apparently you can make a 10G receiver very cheap, it is the
transmitter that is expensive. So it is 10G downstream and 1G upstream.
With the option to deliver 10G upstream per ONU. It is about reusing
standard ethernet components that are dirt cheap - you can buy ethernet SFP
modules for peanuts after all and 10G SFP+ modules are not that expensive
either.

However when we asked some vendors about this, nobody wanted to sell to us
because Europe (and USA I assume) is GPON while China is GEPON. They did
offer to sell us GPON at 10GEPON pricing instead...

Something fishy is going on. It is not about EC compliance as it is just a
matter of buying a 10GEPON card instead of GPON card to the same chassis
switch. Maybe patents?

Regards,

Baldur


On 6 January 2016 at 14:57, Colton Conor  wrote:

> If you take out "bitrate, split ratio, cross vendor compatibility and
> purchase price differences" then what else would you like to compare or
> know? Those would be the major differences I would say. We only deploy GPON
> here. I would say in a system like GEPON or GPON where a port is shared
> between users more bandwidth is better, and GPON has more capacity than
> GEPON. I am not sure which region you are in, but in the USA GEPON is
> almost non-existent from the larger players. Meaning that most GEPON
> equipment won't be ANSI certified, and might not have FFC certs.
>
> Huawei used to have a couple of slides.
>
> I looked on some other list and found the following:
>
> We considered EPON, and there are some inexpensive solutions from off shore
> that are worth considering.
>
>
>
> In the end, we went for GPON for two reasons:
>
>
>
> One, you can deliver a true 1Gbps service where more than one customer on a
> PON segment can actually get 1Gbps at a time, because the GPON supports
> 2.4Gbps of total usage on the segment.
>
>
>
> Two we like our current vendor, Adtran, and we wanted to put OLT cards into
> the same chassis and manage them using the same systems. The cost premium
> versus a new vendor for EPON wasn't huge. The CPE is the bigger cost, and
> we didn't see a real cost difference between EPON ONT and GPON ONT.
>
>
>
> In the end, the price difference for GPON versus EPON wasn't great - and
> while GPON is a bit "designed by committee" and there are some valid
> criticisms there, they're academic in light of the other factors.
>
> On Tue, Jan 5, 2016 at 3:00 PM,  wrote:
>
> > Hello all,
> >
> > For those of you with optical last mile networks that are familiar with
> > both GPON and GEPON, would you mind sharing experiences of the
> differences
> > between GPON and GEPON, especially from an operative perspective?
> >
> > For arguments sake let's assume bitrate, split ratio, cross vendor
> > compatibility and purchase price differences aren't of major interest.
> >
> > Thanks,
> >
> > Jared
> >
>

Re: SMS gateways

[Alex Buie]

Based on a cursory pass of the FB website I can't find any of their
products that have a CDMA modem - so they're definitely incorrect in that
sense. Voice, text, 2G and 3G data are all CDMA on Verizon, unless you're
doing something with SMS over IMS which is only supported with LTE capable
hardware on the Verizon side.

On Thu, Jan 7, 2016 at 4:40 PM, David Hubbard  wrote:

> Scott, I was interested in that as well, it was in my original post.  I’m
> considering that and the SMSEagle; both are from Europe.  I can’t find too
> much on them from a real world war stories perspective, but there has been
> mention of the FoxBox on nanog in years past, so there are some users out
> there.
>
> I am not going the Microtik+cell modem route that Faisal mentioned in his
> reply post because the intent is to tie the SMS alerting into other systems
> using some form of API, and both FoxBox and SMSEagle make that incredibly
> easy by having a simple http interface for sending texts, or a full API if
> you need to do two way.  The nagios plugin (and Zabbix too) are super
> simple since it’s just HTTP POST to send the alerts.
>
> FoxBox claims it will work on Verizon networks because of the 3G support,
> but that doesn’t leave me with a comfortable feeling, so if we buy in, we’d
> probably get accounts from a GSM carrier for it, although I can’t find
> whether or not AT, etc. offer machine accounts, and I would not want to
> pay $50/mo per device just to send random texts.
>
> I did get an off list reply from someone who let me know that our existing
> OpenGear devices (cell+ethernet console servers that run linux) have the
> ability to send SMS using a utility already present in the OS install.
> Since we already have those in every location we’d also be putting an SMS
> gateway, I’m going to investigate if we could put a cgi script or something
> similar on them to accomplish the same goal with no additional equipment.
>
> David
>
>
>
>
> On 1/7/16, 3:34 PM, "NANOG on behalf of Scott Fisher" <
> nanog-boun...@nanog.org on behalf of littlefish...@gmail.com> wrote:
>
> >Does anyone having experience getting this to work on US networks?
> >
> >http://www.smsfoxbox.it/en/foxbox-lx800-gateway-100.html/
> >
> >I am interested on getting this working with our Nagios notifications.
> >
> >On Wed, Jan 6, 2016 at 9:40 PM, John Levine  wrote:
> >>>Thanks for those pointers. The "mega bill" problem is one I have to
> avoid. We used to use ISDN as backup to T1 circuits,
> >>>but had to abandon that after some wayward fail-overs resulted in $5000
> phone bills. I'll check the plan overage terms
> >>>carefully!
> >>
> >> Sounds like an excellent application for a $10/mo prepaid plan on
> >> something like Tracfone.  If disaster strikes and you need a lot of
> >> data one month, you can add extra credit directly from the phone.
> >>
> >
> >
> >
> >--
> >Scott
>

CPE that supports 464XLAT

[Daniel Corbe]

Anyone out there aware of any DOCSIS 3.0 cable modems that have a working CLAT 
implementation?

Re: Nat

[Doug Barton]

On 12/18/2015 01:20 PM, Lee Howard wrote:



On 12/17/15, 1:59 PM, "NANOG on behalf of Matthew Petach"



I'm still waiting for the IETF to come around
to allowing feature parity between IPv4 and IPv6
when it comes to DHCP.  The stance of not
allowing the DHCP server to assign a default
gateway to the host in IPv6 is a big stumbling
point for at least one large enterprise I'm aware
of.



Tell me again why you want this, and not routing information from the
router?


C'mon Lee, stop pretending that you're interested in the answer to this 
question, and wasting everyone's time in the process. You know the 
answers, just as well as the people who would give them.



Right now, the biggest obstacle to IPv6
deployment seems to be the ivory-tower types
in the IETF that want to keep it pristine, vs
allowing it to work in the real world.


There¹s a mix of people at IETF, but more operator input there would be
helpful. I have a particular draft in mind that is stuck between ³we¹d
rather delay IPv6 than do it wrong² and ³be realistic about how people
will deploy it."


On this topic the operator input has been clear for over a decade, and 
yet the purists have blocked progress this whole time. The biggest 
roadblock to IPv6 deployment are its most ardent "supporters."

Binge On! - get your umbrellas out, stuff's hitting the fan.

[Valdis Kletnieks]

So we went round and round back in November regarding Binge On! and whether
it was net neutrality. So here's some closure to that...

The EFF did some testing and discovered that what T-Mobile is actually doing
doesn't match what they said it was...

https://www.eff.org/deeplinks/2016/01/eff-confirms-t-mobiles-bingeon-optimization-just-throttling-applies

Apparently, John Legere, CEO of T-Mobile, doesn't know who the EFF is,
or why they're giving him a hard time.

"Part B of my answer is, who the fuck are you, anyway, EFF?" Legere said. "Why
are you stirring up so much trouble, and who pays you?"

http://www.theverge.com/2016/1/7/10733298/john-legere-binge-on-lie

/me makes popcorn


pgpxrENJeSCws.pgp
Description: PGP signature

Re: Smokeping targets

[Andrew Dampf]

Something I found that is helpful once you've gathered a list of targets is
the following command for generating config to paste:

traceroute -w 3 [IPaddress] | grep -v "*" | grep -v "traceroute" | sed -e
's/(//g' -e 's/)//g' | awk '{ gsub(/\./,"_",$2); print " "$2"\nmenu =
"$3"\ntitle = "$2" - "$3"\nhost = "$3"\n"}'

That generates a valid output for configs to ping each hop along the way to
your destination, which can be super useful. Not all of them allow ICMP but
a decent amount do.

On Thu, Jan 7, 2016 at 10:34 AM, Brian R. Swan  wrote:

> Hi all,
>
> I’m setting up smokeping to try and gather some latency statistics on my
> ISP to different parts of the world.  Does there exist a list or any
> generic recommendations of different targets to config within smokeping?
> Google and searching the NANOG mailing list have failed me, and I don’t
> want to just spam random IP addresses with ICMP requests if there’s a more
> official/accepted method for doing this.
>
> Thanks!
> Brian

Re: Smokeping targets

[Brian R. Swan]

Very cool - thanks for sharing that.

> On Jan 7, 2016, at 9:59 AM, Andrew Dampf  wrote:
> 
> Something I found that is helpful once you've gathered a list of targets is 
> the following command for generating config to paste:

Re: Smokeping targets

[Frederik Kriewitz]

Hello Brian,

you might want to consider joining the nlnog ring (https://ring.nlnog.net/).
You can request access to a full mesh smokeping for all hosts too.

Besides the ring host RIPE Atlas anchors (
https://atlas.ripe.net/anchors/list/) might be another option for hosts to
add to your list.
Am 07.01.2016 16:36 schrieb "Brian R. Swan" :

> Hi all,
>
> I’m setting up smokeping to try and gather some latency statistics on my
> ISP to different parts of the world.  Does there exist a list or any
> generic recommendations of different targets to config within smokeping?
> Google and searching the NANOG mailing list have failed me, and I don’t
> want to just spam random IP addresses with ICMP requests if there’s a more
> official/accepted method for doing this.
>
> Thanks!
> Brian

Re: How to update IPv6 geolocation data? Google sites blocked.

[David Sotnick]

Hi Hugo,

Thanks for the follow-up. For some reason both responses from Mr. Lewis
ended up my Gmail (domain) Spam folder. I have never had a NANOG response
go into Spam, so I didn't even think to check there.

I'll give this a shot today. Thanks again!

-David


On Wed, Jan 6, 2016 at 9:18 PM, Hugo Slabbert  wrote:

> On Wed 2016-Jan-06 16:23:21 -0800, David Sotnick 
> wrote:
>
> Really? Nobody here knows how one goes about updating IPv6 geolocation
>> data? Our /48 is still being denied access to Google sites due to unknown
>> geolocation.
>>
>> Help?
>>
>
> John Lewis responded with some info[1], which is backed up by Google's own
> support page[2][3].  No bets from me on how quickly or reliably that gets
> updated, though...
>
>
>> Best,
>> David
>>
>
> --
> Hugo
>
> h...@slabnet.com: email, xmpp/jabber
> PGP fingerprint (B178313E):
> CF18 15FA 9FE4 0CD1 2319 1D77 9AB1 0FFD B178 313E
>
> (also on Signal)
>
> [1] http://mailman.nanog.org/pipermail/nanog/2015-December/083078.html
> [2] https://support.google.com/websearch/answer/873?hl=en
> [3] https://support.google.com/websearch/answer/179386
>
>
> On Tue, Dec 22, 2015 at 1:34 PM, David Sotnick 
>> wrote:
>>
>> Hello, and Season's Greetings!
>>>
>>> We recently lit up a new IPv6-connected location and expanded our
>>> ARIN-allocated /48 network to a /44 network to accommodate the additional
>>> location (and future locations).
>>>
>>> However, since moving our small satellite office off our primary /48 and
>>> onto their own /48 as part of our /44 network, the users at that office
>>> are
>>> receiving messages from e.g. YouTube that the "user has not made this
>>> content available in your country".
>>>
>>> How does one go about updating this v6 geolocation data? This is
>>> impacting
>>> a bunch of our users.
>>>
>>> Thanks!
>>>
>>> -David
>>>
>>>

Re: Smokeping targets

[Clinton Work]

The NLNOG RING servers would be good targets and they expected to get
pinged.   
https://ring.nlnog.net/participants/

On Thu, Jan 7, 2016, at 08:34 AM, Brian R. Swan wrote:
> I’m setting up smokeping to try and gather some latency statistics on my
> ISP to different parts of the world.  Does there exist a list or any
> generic recommendations of different targets to config within smokeping? 

Re: Smokeping targets

[Brian R. Swan]

Doh!  Not sure why I didn’t think about Atlas prior to posting my question - 
that’s perfect.  

I have an Atlas node on my network too.  After I put it in and played with it 
for a week I started a big project at work and put it on the “to play with 
later” list and never got back to it. :)

Thanks!
Brian

> On Jan 7, 2016, at 10:26 AM, Frederik Kriewitz  wrote:
> 
> Hello Brian,
> 
> you might want to consider joining the nlnog ring (https://ring.nlnog.net/ 
> ).
> You can request access to a full mesh smokeping for all hosts too.
> 
> Besides the ring host RIPE Atlas anchors 
> (https://atlas.ripe.net/anchors/list/ ) 
> might be another option for hosts to add to your list.
> 

Re: SMS gateways

[Scott Fisher]

Does anyone having experience getting this to work on US networks?

http://www.smsfoxbox.it/en/foxbox-lx800-gateway-100.html/

I am interested on getting this working with our Nagios notifications.

On Wed, Jan 6, 2016 at 9:40 PM, John Levine  wrote:
>>Thanks for those pointers. The "mega bill" problem is one I have to avoid. We 
>>used to use ISDN as backup to T1 circuits,
>>but had to abandon that after some wayward fail-overs resulted in $5000 phone 
>>bills. I'll check the plan overage terms
>>carefully!
>
> Sounds like an excellent application for a $10/mo prepaid plan on
> something like Tracfone.  If disaster strikes and you need a lot of
> data one month, you can add extra credit directly from the phone.
>



-- 
Scott

Re: SMS gateways

[Scott Fisher]

I am well aware of email-to-sms, but that is dependant on
links/infrastructure that you are monitoring. (Think of it like having your
Nagios system running on the same hypervisor as your other production gear.
What happens if the hypervisor drops? How would you know?)

The hardware sms gateway allows for true oob notifications.

On Thursday, January 7, 2016, Faisal Imtiaz 
wrote:

> There are multiple ways to skin this cat !.
>
> No, not familiar with this product...
>
> However..
>
> 1) You know that you can send sms messages via email to pretty much any
> cell phone.
>
> 2) Personal Preference, if I was doing so, I would do it with a small
> mikrotik router + usb cell modem, very inexpensive, especially when
> combined with a M2M plan.
>
> Regards.
>
> Faisal Imtiaz
> Snappy Internet & Telecom
> 7266 SW 48 Street
> Miami, FL 33155
> Tel: 305 663 5518 x 232
>
> Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net
>
> - Original Message -
> > From: "Scott Fisher" >
> > To: "John Levine" >
> > Cc: "nanog list" >
> > Sent: Thursday, January 7, 2016 3:34:42 PM
> > Subject: Re: SMS gateways
>
> > Does anyone having experience getting this to work on US networks?
> >
> > http://www.smsfoxbox.it/en/foxbox-lx800-gateway-100.html/
> >
> > I am interested on getting this working with our Nagios notifications.
> >
> > On Wed, Jan 6, 2016 at 9:40 PM, John Levine  > wrote:
> >>>Thanks for those pointers. The "mega bill" problem is one I have to
> avoid. We
> >>>used to use ISDN as backup to T1 circuits,
> >>>but had to abandon that after some wayward fail-overs resulted in $5000
> phone
> >>>bills. I'll check the plan overage terms
> >>>carefully!
> >>
> >> Sounds like an excellent application for a $10/mo prepaid plan on
> >> something like Tracfone.  If disaster strikes and you need a lot of
> >> data one month, you can add extra credit directly from the phone.
> >>
> >
> >
> >
> > --
> > Scott
>


-- 
Scott

Re: SMS gateways

[Faisal Imtiaz]

There are multiple ways to skin this cat !.

No, not familiar with this product... 

However..

1) You know that you can send sms messages via email to pretty much any cell 
phone.

2) Personal Preference, if I was doing so, I would do it with a small mikrotik 
router + usb cell modem, very inexpensive, especially when combined with a M2M 
plan.

Regards.

Faisal Imtiaz
Snappy Internet & Telecom
7266 SW 48 Street
Miami, FL 33155
Tel: 305 663 5518 x 232

Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net

- Original Message -
> From: "Scott Fisher" 
> To: "John Levine" 
> Cc: "nanog list" 
> Sent: Thursday, January 7, 2016 3:34:42 PM
> Subject: Re: SMS gateways

> Does anyone having experience getting this to work on US networks?
> 
> http://www.smsfoxbox.it/en/foxbox-lx800-gateway-100.html/
> 
> I am interested on getting this working with our Nagios notifications.
> 
> On Wed, Jan 6, 2016 at 9:40 PM, John Levine  wrote:
>>>Thanks for those pointers. The "mega bill" problem is one I have to avoid. We
>>>used to use ISDN as backup to T1 circuits,
>>>but had to abandon that after some wayward fail-overs resulted in $5000 phone
>>>bills. I'll check the plan overage terms
>>>carefully!
>>
>> Sounds like an excellent application for a $10/mo prepaid plan on
>> something like Tracfone.  If disaster strikes and you need a lot of
>> data one month, you can add extra credit directly from the phone.
>>
> 
> 
> 
> --
> Scott

Re: SMS gateways

[Scott Fisher]

I emailed smsfoxbox support asking about US network support. I am
hoping to hear back soon and I will let you all know the answer.

Thanks,
Scott

On Thu, Jan 7, 2016 at 4:40 PM, David Hubbard
 wrote:
> Scott, I was interested in that as well, it was in my original post.  I’m 
> considering that and the SMSEagle; both are from Europe.  I can’t find too 
> much on them from a real world war stories perspective, but there has been 
> mention of the FoxBox on nanog in years past, so there are some users out 
> there.
>
> I am not going the Microtik+cell modem route that Faisal mentioned in his 
> reply post because the intent is to tie the SMS alerting into other systems 
> using some form of API, and both FoxBox and SMSEagle make that incredibly 
> easy by having a simple http interface for sending texts, or a full API if 
> you need to do two way.  The nagios plugin (and Zabbix too) are super simple 
> since it’s just HTTP POST to send the alerts.
>
> FoxBox claims it will work on Verizon networks because of the 3G support, but 
> that doesn’t leave me with a comfortable feeling, so if we buy in, we’d 
> probably get accounts from a GSM carrier for it, although I can’t find 
> whether or not AT, etc. offer machine accounts, and I would not want to pay 
> $50/mo per device just to send random texts.
>
> I did get an off list reply from someone who let me know that our existing 
> OpenGear devices (cell+ethernet console servers that run linux) have the 
> ability to send SMS using a utility already present in the OS install.  Since 
> we already have those in every location we’d also be putting an SMS gateway, 
> I’m going to investigate if we could put a cgi script or something similar on 
> them to accomplish the same goal with no additional equipment.
>
> David
>
>
>
>
> On 1/7/16, 3:34 PM, "NANOG on behalf of Scott Fisher" 
>  wrote:
>
>>Does anyone having experience getting this to work on US networks?
>>
>>http://www.smsfoxbox.it/en/foxbox-lx800-gateway-100.html/
>>
>>I am interested on getting this working with our Nagios notifications.
>>
>>On Wed, Jan 6, 2016 at 9:40 PM, John Levine  wrote:
Thanks for those pointers. The "mega bill" problem is one I have to avoid. 
We used to use ISDN as backup to T1 circuits,
but had to abandon that after some wayward fail-overs resulted in $5000 
phone bills. I'll check the plan overage terms
carefully!
>>>
>>> Sounds like an excellent application for a $10/mo prepaid plan on
>>> something like Tracfone.  If disaster strikes and you need a lot of
>>> data one month, you can add extra credit directly from the phone.
>>>
>>
>>
>>
>>--
>>Scott



-- 
Scott

Re: SMS gateways

[Faisal Imtiaz]

Yep, agreed in certain situations a hardware gateway is more useful. 

That is what I listed as item #1. A small Mikrotik Router + USB Cell Stick of 
your choice. 
make for a very inexpensive, flexible gateway. 

http://mum.mikrotik.com/presentations/CO10/day1/03-arnis_3g.pdf 
(quiet a few options for different form-factors) 

http://mum.mikrotik.com/presentations/US11/us11-brian.pdf 

Regards 

:) 

Faisal Imtiaz 
Snappy Internet & Telecom 
7266 SW 48 Street 
Miami, FL 33155 
Tel: 305 663 5518 x 232 

Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net 

> From: "Scott Fisher" 
> To: "Faisal Imtiaz" 
> Cc: "John Levine" , "nanog list" 
> Sent: Thursday, January 7, 2016 3:55:07 PM
> Subject: Re: SMS gateways

> I am well aware of email-to-sms, but that is dependant on links/infrastructure
> that you are monitoring. (Think of it like having your Nagios system running 
> on
> the same hypervisor as your other production gear. What happens if the
> hypervisor drops? How would you know? )
> The hardware sms gateway allows for true oob notifications.

> On Thursday, January 7, 2016, Faisal Imtiaz < fai...@snappytelecom.net > 
> wrote:

>> There are multiple ways to skin this cat !.

>> No, not familiar with this product...

>> However..

>> 1) You know that you can send sms messages via email to pretty much any cell
>> phone.

>> 2) Personal Preference, if I was doing so, I would do it with a small 
>> mikrotik
>> router + usb cell modem, very inexpensive, especially when combined with a 
>> M2M
>> plan.

>> Regards.

>> Faisal Imtiaz
>> Snappy Internet & Telecom
>> 7266 SW 48 Street
>> Miami, FL 33155
>> Tel: 305 663 5518 x 232

>> Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net

>> - Original Message -
>> > From: "Scott Fisher" < littlefish...@gmail.com >
>> > To: "John Levine" < jo...@iecc.com >
>> > Cc: "nanog list" < nanog@nanog.org >
>> > Sent: Thursday, January 7, 2016 3:34:42 PM
>> > Subject: Re: SMS gateways

>> > Does anyone having experience getting this to work on US networks?

>> > http://www.smsfoxbox.it/en/foxbox-lx800-gateway-100.html/

>> > I am interested on getting this working with our Nagios notifications.

>> > On Wed, Jan 6, 2016 at 9:40 PM, John Levine < jo...@iecc.com > wrote:
>> >>>Thanks for those pointers. The "mega bill" problem is one I have to 
>> >>>avoid. We
>> >>>used to use ISDN as backup to T1 circuits,
>> >>>but had to abandon that after some wayward fail-overs resulted in $5000 
>> >>>phone
>> >>>bills. I'll check the plan overage terms
>> >>>carefully!

>> >> Sounds like an excellent application for a $10/mo prepaid plan on
>> >> something like Tracfone. If disaster strikes and you need a lot of
>> >> data one month, you can add extra credit directly from the phone.




>> > --
>> > Scott

> --
> Scott

Re: SMS gateways

[David Hubbard]

Scott, I was interested in that as well, it was in my original post.  I’m 
considering that and the SMSEagle; both are from Europe.  I can’t find too much 
on them from a real world war stories perspective, but there has been mention 
of the FoxBox on nanog in years past, so there are some users out there.

I am not going the Microtik+cell modem route that Faisal mentioned in his reply 
post because the intent is to tie the SMS alerting into other systems using 
some form of API, and both FoxBox and SMSEagle make that incredibly easy by 
having a simple http interface for sending texts, or a full API if you need to 
do two way.  The nagios plugin (and Zabbix too) are super simple since it’s 
just HTTP POST to send the alerts.

FoxBox claims it will work on Verizon networks because of the 3G support, but 
that doesn’t leave me with a comfortable feeling, so if we buy in, we’d 
probably get accounts from a GSM carrier for it, although I can’t find whether 
or not AT, etc. offer machine accounts, and I would not want to pay $50/mo 
per device just to send random texts.

I did get an off list reply from someone who let me know that our existing 
OpenGear devices (cell+ethernet console servers that run linux) have the 
ability to send SMS using a utility already present in the OS install.  Since 
we already have those in every location we’d also be putting an SMS gateway, 
I’m going to investigate if we could put a cgi script or something similar on 
them to accomplish the same goal with no additional equipment.

David




On 1/7/16, 3:34 PM, "NANOG on behalf of Scott Fisher"  wrote:

>Does anyone having experience getting this to work on US networks?
>
>http://www.smsfoxbox.it/en/foxbox-lx800-gateway-100.html/
>
>I am interested on getting this working with our Nagios notifications.
>
>On Wed, Jan 6, 2016 at 9:40 PM, John Levine  wrote:
>>>Thanks for those pointers. The "mega bill" problem is one I have to avoid. 
>>>We used to use ISDN as backup to T1 circuits,
>>>but had to abandon that after some wayward fail-overs resulted in $5000 
>>>phone bills. I'll check the plan overage terms
>>>carefully!
>>
>> Sounds like an excellent application for a $10/mo prepaid plan on
>> something like Tracfone.  If disaster strikes and you need a lot of
>> data one month, you can add extra credit directly from the phone.
>>
>
>
>
>-- 
>Scott