22 Oct
2016
22 Oct
'16
2:29 p.m.
It was made through Brian.
On Sat, Oct 22, 2016 at 3:04 PM, Jerry DeLong <kd4yal(a)gmail.com> wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Miguel,
>
> I am sure you have not made any DNS request to me.
> So you need to make sure DNS is setup.
>
> Email me off the list and I can add your DNS entries.
>
>
> Jerry, KD4YAL
>
>
> On Sat, Oct 22, 2016 at 2:43 PM, Miguel Rodriguez
> <miguemely101(a)gmail.com> wrote:
> > (Please trim inclusions from previous messages)
> > _______________________________________________
> > I know it worked because I used to have a double-natted network which
> > passed IPIP traffic to a mikrotik router. Now I'm just consolidating to
> one
> > EdgeRouter.
> >
> >
> > On Sat, Oct 22, 2016 at 2:42 PM, Miguel Rodriguez <
> miguemely101(a)gmail.com>
> > wrote:
> >
> >> After a packet-capture, I noticed that I am not getting any IPIP traffic
> >> at all.
> >>
> >> On Sat, Oct 22, 2016 at 1:50 PM, Miguel Rodriguez <
> miguemely101(a)gmail.com>
> >> wrote:
> >>
> >>> I thought I put my callsign in my signature, but I guess I did not,
> haha.
> >>> 44.98.17.32 / 27 KM4VYU
> >>>
> >>> I'll see if I can do a packet-capture on the outside port.
> >>>
> >>> On Sat, Oct 22, 2016 at 8:29 AM, Rob Janssen <pe1chl(a)amsat.org>
wrote:
> >>>
> >>>> (Please trim inclusions from previous messages)
> >>>> _______________________________________________
> >>>>
> >>>>> I've tried a few other things with no avail at this point.
> >>>>>
> >>>>
> >>>> Put a monitoring device at the outside port, or start a data
capture
> in
> >>>> the router itself when EdgeOS can
> >>>> do that, and then check what is arriving when you do the outside
ping.
> >>>>
> >>>> When you see packets coming from 169.228.66.251 addressed to your
> >>>> external IP with protocol field 4 you
> >>>> at least know the external causes are covered. You can then
> concentrate
> >>>> on the setup of your router.
> >>>>
> >>>> When no such packets appear, the problem is in your gateway setup
at
> >>>> portal.ampr.org or your DNS entry.
> >>>>
> >>>> As I don't see your callsign or AMPRnet IP anywhere in your
message I
> >>>> can't do much research...
> >>>>
> >>>>
> >>>> Rob
> >>>>
> >>>> _________________________________________
> >>>> 44Net mailing list
> >>>> 44Net(a)hamradio.ucsd.edu
> >>>> http://hamradio.ucsd.edu/mailman/listinfo/44net
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Miguel Rodriguez
> >>> 12th Grade Student
> >>> miguemely101(a)gmail.com
> >>> Tel: *561-758-0631 <561-758-0631>*
> >>>
> >>>
> >>> *Accredited District Since 2008; Re-certification - January 2013*
> >>>
> >>> Home of Florida's first LEED Gold Certified School
> >>>
> >>> *Disclaimer*: Under Florida law, e-mail addresses are *public records*.
> >>> If you do not want your e-mail address released in response to a public
> >>> records request, do not send electronic mail to this entity. Instead,
> >>> contact this office by phone or in writing.
> >>>
> >>>
> >>
> >>
> >> --
> >> Miguel Rodriguez
> >> 12th Grade Student
> >> miguemely101(a)gmail.com
> >> Tel: *561-758-0631 <561-758-0631>*
> >>
> >>
> >> *Accredited District Since 2008; Re-certification - January 2013*
> >>
> >> Home of Florida's first LEED Gold Certified School
> >>
> >> *Disclaimer*: Under Florida law, e-mail addresses are *public records*.
> >> If you do not want your e-mail address released in response to a public
> >> records request, do not send electronic mail to this entity. Instead,
> >> contact this office by phone or in writing.
> >>
> >>
> >
> >
> > --
> > Miguel Rodriguez
> > 12th Grade Student
> > miguemely101(a)gmail.com
> > Tel: *561-758-0631*
> >
> >
> > *Accredited District Since 2008; Re-certification - January 2013*
> >
> > Home of Florida's first LEED Gold Certified School
> >
> > *Disclaimer*: Under Florida law, e-mail addresses are *public records*.
> If
> > you do not want your e-mail address released in response to a public
> > records request, do not send electronic mail to this entity. Instead,
> > contact this office by phone or in writing.
> >