19 Feb
2017
19 Feb
'17
2:05 p.m.
Does anyone know how to reach VE2HOM? He is keeping his contact information well-hidden,
it appears.
His gateway at 206.80.251.222 is sending a lot of traffic with RFC1918 source address:
Feb 19 15:00:53 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222 SRC=192.168.0.5
DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=13455 DF PROTO=TCP SPT=40510 DPT=443
WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:00:57 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222 SRC=192.168.0.5
DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=38262 DF PROTO=TCP SPT=40512 DPT=443
WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:01:01 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222 SRC=192.168.0.5
DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=14124 DF PROTO=TCP SPT=40480 DPT=443
WINDOW=29200 RES=0x00 SYN URGP=0
Everyone remember: when you are combining the routing of AMPRnet and other network
traffic, make sure you
have the proper routing and/or NAT rules in place, and preferably also a filter, to make
sure you don't send traffic
with a source address like 192.168.0.5 into an AMPRnet tunnel.
Rob
19 Feb
19 Feb
4:12 p.m.
http://www.canada411.ca/res/8198321215/Pascal-Lafond/249160190.html
73
va7dgp
*Don Poaps*
*New Westminster, BC*
*VA7DGP DATA*
*VA7QU VOICE*
*Winlink: va7qu(a)winlink.org <va7qu(a)winlink.org>*
On Sun, Feb 19, 2017 at 6:05 AM, Rob Janssen <pe1chl(a)amsat.org> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Does anyone know how to reach VE2HOM? He is keeping his contact
information well-hidden, it appears.
His gateway at 206.80.251.222 is sending a lot of traffic with RFC1918
source address:
Feb 19 15:00:53 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=13455
DF PROTO=TCP SPT=40510 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:00:57 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=38262
DF PROTO=TCP SPT=40512 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:01:01 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=14124
DF PROTO=TCP SPT=40480 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Everyone remember: when you are combining the routing of AMPRnet and other
network traffic, make sure you
have the proper routing and/or NAT rules in place, and preferably also a
filter, to make sure you don't send traffic
with a source address like 192.168.0.5 into an AMPRnet tunnel.
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
5:23 p.m.
Hi Rob,
va2hom(a)gmail.com
73,
Michel
ve2bcw
sysop ve2uqh.ampr.org
2017-02-19 9:05 GMT-05:00 Rob Janssen <pe1chl(a)amsat.org>rg>:
(Please trim inclusions from previous messages)
_______________________________________________
Does anyone know how to reach VE2HOM? He is keeping his contact
information well-hidden, it appears.
His gateway at 206.80.251.222 is sending a lot of traffic with RFC1918
source address:
Feb 19 15:00:53 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=13455
DF PROTO=TCP SPT=40510 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:00:57 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=38262
DF PROTO=TCP SPT=40512 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:01:01 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62 ID=14124
DF PROTO=TCP SPT=40480 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Everyone remember: when you are combining the routing of AMPRnet and other
network traffic, make sure you
have the proper routing and/or NAT rules in place, and preferably also a
filter, to make sure you don't send traffic
with a source address like 192.168.0.5 into an AMPRnet tunnel.
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
8:13 p.m.
Hello Rob,
I have receive your email this morning and reply to it before your send
on the group, I also close my amprnet for the moment. I'm new with the
mikrotik router and don't know all, I get information on the internet to
get it work. Sorry for the bad packet this is not intentionnal.
73 de Pascal
ve2hom
Le 2017-02-19 à 09:05, Rob Janssen a écrit :
(Please trim inclusions from previous messages)
_______________________________________________
Does anyone know how to reach VE2HOM? He is keeping his contact
information well-hidden, it appears.
His gateway at 206.80.251.222 is sending a lot of traffic with RFC1918
source address:
Feb 19 15:00:53 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62
ID=13455 DF PROTO=TCP SPT=40510 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:00:57 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62
ID=38262 DF PROTO=TCP SPT=40512 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Feb 19 15:01:01 Packet DROP: IN=tunl0 OUT=eth1 TUNL=206.80.251.222
SRC=192.168.0.5 DST=44.137.42.18 LEN=60 TOS=0x00 PREC=0x00 TTL=62
ID=14124 DF PROTO=TCP SPT=40480 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0
Everyone remember: when you are combining the routing of AMPRnet and
other network traffic, make sure you
have the proper routing and/or NAT rules in place, and preferably also
a filter, to make sure you don't send traffic
with a source address like 192.168.0.5 into an AMPRnet tunnel.
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
2629
days inactive
2629
days old
3 comments
4 participants
participants (4)
-
Don Poaps -
Michel Beaudry -
Rob Janssen -
ve2hom Pascal Lafond