13 Dec
2017
13 Dec
'17
10:42 a.m.
Hi All,
I am sure that this question is asked by many newbies but I have to ask it to bring up my
gateway... :)
I set up a gateway and coordinated the ip allocation with my regional IP coordinator.
But, however, testing behind NAT or without NAT (directly machine connected to internet (a
server on a colaction ISP)) didn't have success..
using ampr-ripd with compiled DEBUG options I cant get and response from the 44.0.0.1
For testting I just did
# ifconfig tunl0 up 44.176.200.1 netmask 255.255.255.255
and tried
#./ampr-ripd -d -v -i tunl0
the result is as follows but no success even if I wait for 2 hours...
IS THERE A WAY TO TEST THIS RIPD CONNECTION ? (a tool or sniffing with tcpdump..) HOW CAN
I BE SURE THAT I AM DOING EVERTHING RIGHT ?
Do I have to do something for multicast domain (e.g. 224.0.0.9)
Thanks
Baris TA7W
DEBUG OUTPUT:
------------------------
Using metric 0 for routes.
Using TCP window 840 for routes.
Using routing table 'main' (254).
Can not open encap file for reading: /var/lib/ampr-ripd/encap.txt
Max list size: 1000 entries
Detected tunnel interface address: 44.176.200.1
Interface detected: lo, IP: 127.0.0.1
Interface detected: eth0, IP: 80.211.231.30
Interface detected: eth1, IP: 0.0.0.0
Interface detected: eth2, IP: 0.0.0.0
Interface detected: tunl0, IP: 44.176.200.1
Assigned tunnel interface index: 5
Local IPs:
127.0.0.1
80.211.231.30
44.176.200.1
NL sending request.
NLMSG: get route (26)
RTA type: 1 (8 bytes): 8 8 8 8
NL response received.
NLMSG: request new route/route info (24)
RTA type: 15 (8 bytes): 254 0 0 0
RTA type: 1 (8 bytes): 8 8 8 8
RTA type: 4 (8 bytes): 2 0 0 0
RTA type: 7 (8 bytes): 80 211 231 30
RTA type: 5 (8 bytes): 80 211 231 1
RTA type: 8 (28 bytes): 8 0 2 0 220 5 0 0 8 0 8 0 180 5 0 0 8 0 10 0 64 0 0 0
RTA type: 12 (36 bytes): 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
NL sending request.
NLMSG: get route (26)
RTA type: 1 (8 bytes): 80 211 231 1
NL response received.
NLMSG: request new route/route info (24)
RTA type: 15 (8 bytes): 254 0 0 0
RTA type: 1 (8 bytes): 80 211 231 1
RTA type: 4 (8 bytes): 2 0 0 0
RTA type: 7 (8 bytes): 80 211 231 30
RTA type: 8 (28 bytes): 8 0 2 0 220 5 0 0 8 0 8 0 180 5 0 0 8 0 10 0 64 0 0 0
RTA type: 12 (36 bytes): 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Using gateway 80.211.231.1 for direct 44net endpoints via interface eth0.
Setting routes (0).
Creating multicast RIP UDP listening socket.
Setting up multicast interface.
Waiting for RIPv2 broadcasts...
13 Dec
13 Dec
9:49 a.m.
Hello Baris.
You need to enable udp port 520 for incoming packets.
Best regards.
Tom - SP2L
11:35 a.m.
Hi Tom,
Thanks for quick reply.
I am using ampr-ripd daemon which enables the UDP 520.. I can check its existency by
command
nc -u <MY_IP> 520
Should I do something else... I am not hehind a firewall or any iother network equipment.
My gateway is directly connected to INTERNET. My server has a real IP and all ports are
open....
Thanks
baris TA7W
----- Original Message -----
From: SP2L(a)wp.pl
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 12:49:42 PM
Subject: Re: [44net] GW Setup Problem
Hello Baris.
You need to enable udp port 520 for incoming packets.
Best regards.
Tom - SP2L
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
10:49 a.m.
Baris.
You should see something like below:
root@linux:/# ampr-ripd -d -v -i tunl0
Using metric 0 for routes.
Using TCP window 840 for routes.
Using gateway 192.168.0.1 for direct 44net endpoints via interface eth0.
Waiting for RIPv2 broadcasts...
ampr-ripd -d -v -i tunl0
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
RipV2 broadcasts take place every 5 minutes starting fom full hour.
So, no need to wait 2 hours.
Also, check ip route; you should have something like that:
root@linux:/# ip route |grep 44.0.0.1
44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840
root@linux:/#
Best regards.
12:04 p.m.
Thanks.. After filling an encap.txt file and placing it under /var/www/ampr-ripd I
started getting some more messages....
Now I have a full ip route table including 44.0.0.1
# ip route |grep 44.0.0.1
44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840
And also when I do a tracepath now I directly go to desired target...
# tracepath 44.132.128.1
1?: [LOCALHOST] pmtu 1480
1: 44.176.200.1 (44.176.200.1) 0.099ms pmtu 1472
1: 44.132.128.1 (44.132.128.1) 47.047ms reached
Resume: pmtu 1472 hops 1 back 1
Still I don't use a password.. I should figure out how to gether my password....
When I do a tracepath to 44.176.200.1 from another internet machine I cannot reach my
gateway :(
TA7W on progress...
baris
----- Original Message -----
From: SP2L(a)wp.pl
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 1:49:01 PM
Subject: Re: [44net] GW Setup Problem
Baris.
You should see something like below:
root@linux:/# ampr-ripd -d -v -i tunl0
Using metric 0 for routes.
Using TCP window 840 for routes.
Using gateway 192.168.0.1 for direct 44net endpoints via interface eth0.
Waiting for RIPv2 broadcasts...
ampr-ripd -d -v -i tunl0
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
RipV2 broadcasts take place every 5 minutes starting fom full hour.
So, no need to wait 2 hours.
Also, check ip route; you should have something like that:
root@linux:/# ip route |grep 44.0.0.1
44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840
root@linux:/#
Best regards.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
11:09 a.m.
Baris.
With latest ampr-ripd-2.3 _YOU DO NOT NEED_ password at all.
Use:
/usr/local/bin/ampr-ripd -t 1 -a <publicIP> -i tunl0 -s -v -L
<callsign>@<qthloc>
Best regards.
Tom - SP2L
12:07 p.m.
I have a message on debug output :
(total 648 entries).
RIP len 504 header version 2, Command 2 (Response)
Simple password: pLaInTeXtpAsSwD
Simple password authentication successful.
Is the password "pLaInTeXtpAsSwD" ? :)
Still no access to my gateway from internet (44.176.200.1)
Baris
----- Original Message -----
From: "Barış DİNÇ" <ta7w(a)antrak.org.tr>
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 3:04:40 PM
Subject: Re: [44net] GW Setup Problem
Thanks.. After filling an encap.txt file and placing it under /var/www/ampr-ripd I
started getting some more messages....
Now I have a full ip route table including 44.0.0.1
# ip route |grep 44.0.0.1
44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840
And also when I do a tracepath now I directly go to desired target...
# tracepath 44.132.128.1
1?: [LOCALHOST] pmtu 1480
1: 44.176.200.1 (44.176.200.1) 0.099ms pmtu 1472
1: 44.132.128.1 (44.132.128.1) 47.047ms reached
Resume: pmtu 1472 hops 1 back 1
Still I don't use a password.. I should figure out how to gether my password....
When I do a tracepath to 44.176.200.1 from another internet machine I cannot reach my
gateway :(
TA7W on progress...
baris
----- Original Message -----
From: SP2L(a)wp.pl
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 1:49:01 PM
Subject: Re: [44net] GW Setup Problem
Baris.
You should see something like below:
root@linux:/# ampr-ripd -d -v -i tunl0
Using metric 0 for routes.
Using TCP window 840 for routes.
Using gateway 192.168.0.1 for direct 44net endpoints via interface eth0.
Waiting for RIPv2 broadcasts...
ampr-ripd -d -v -i tunl0
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
Simple password: <password>
RipV2 broadcasts take place every 5 minutes starting fom full hour.
So, no need to wait 2 hours.
Also, check ip route; you should have something like that:
root@linux:/# ip route |grep 44.0.0.1
44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840
root@linux:/#
Best regards.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
11:28 a.m.
Baris.
Traceroute result:
root@linux:/# traceroute 44.176.200.1
traceroute to 44.176.200.1 (44.176.200.1), 30 hops max, 60 byte packets
1 * * *
2 * * *
...
29 * * *
30 * * *
root@linux:/#
Pinging:
root@linux:/d# ping -c5 44.176.200.1
PING 44.176.200.1 (44.176.200.1) 56(84) bytes of data.
--- 44.176.200.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4032ms
root@linux:/#
From Windows 8 44-net aware :
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Wszelkie prawa zastrzeżone.
C:\Windows\System32>ping -n5 44.176.200.1
IP address must be specified.
C:\Windows\System32>ping -n 5 44.176.200.1
Pinging 44.176.200.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 44.176.200.1:
Packets: Sent = 5, Received = 0, Lost = 5 (100% loss),
C:\Windows\System32>
Best regards.
Tom - SP2L
11:33 a.m.
Baris.
Also...
root@linux:/# host 44.176.200.1
Host 1.200.176.44.in-addr.arpa. not found: 3(NXDOMAIN)
root@linux:/#
Best regards.
Tom - SP2L
12:44 p.m.
On Wed, Dec 13, 2017 at 03:07:38PM +0300, Barış DİNÇ wrote:
I have a message on debug output :
(total 648 entries).
RIP len 504 header version 2, Command 2 (Response)
Simple password: pLaInTeXtpAsSwD
Simple password authentication successful.
Is the password "pLaInTeXtpAsSwD" ? :)
Yes, it is a dummy password, not intended for security but to satisfy
the protocol requirements.
Since you are seeing that, you are receiving the RIP transmissions from
the ampr gateway system. In addition, I am able to ping your gateway
address from amprgw, so there is no problem with connectivity between
amprgw and your gateway system.
The filter table on amprgw allows traffic from the internet to the three
addresses 44.176.206.1, 44.176.206.200, and 44.176.206.202.
I have confirmed that traffic to 44.176.206.1 is being encapsulated and
sent to 178.233.172.203.
You should try running tcpdump on your 44.176.206.1 system to see if
you see incoming internet connection attempts. There are always some
of those every minute or so and you should be getting them.
I suspect the problem may be the path back to amprgw from your
44.176.206.1 system. Check your routing tables to be sure that packets
intended for the internet (non-44 addresses) are encapsulated and sent
to amprgw on 169.228.34.84. Try running tcpdump and see what traffic
is being sent to and received from 169.228.34.84.
- Brian
2:24 p.m.
Baris, Rueben mentioned several replies ago to check your 44. address.
They are not the same as what the gateway is set up for you.
Cheers,
Don
On Wed, Dec 13, 2017 at 7:45 AM Brian Kantor <Brian(a)ucsd.edu> wrote:
On Wed, Dec 13, 2017 at 03:07:38PM +0300, Barış DİNÇ
wrote:
--
Cheers,
Don
I have a message on debug output :
(total 648 entries).
RIP len 504 header version 2, Command 2 (Response)
Simple password: pLaInTeXtpAsSwD
Simple password authentication successful.
Is the password "pLaInTeXtpAsSwD" ? :)
Yes, it is a dummy password, not intended for security but to satisfy
the protocol requirements.
Since you are seeing that, you are receiving the RIP transmissions from
the ampr gateway system. In addition, I am able to ping your gateway
address from amprgw, so there is no problem with connectivity between
amprgw and your gateway system.
The filter table on amprgw allows traffic from the internet to the three
addresses 44.176.206.1, 44.176.206.200, and 44.176.206.202.
I have confirmed that traffic to 44.176.206.1 is being encapsulated and
sent to 178.233.172.203.
You should try running tcpdump on your 44.176.206.1 system to see if
you see incoming internet connection attempts. There are always some
of those every minute or so and you should be getting them.
I suspect the problem may be the path back to amprgw from your
44.176.206.1 system. Check your routing tables to be sure that packets
intended for the internet (non-44 addresses) are encapsulated and sent
to amprgw on 169.228.34.84. Try running tcpdump and see what traffic
is being sent to and received from 169.228.34.84.
- Brian
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
11:41 a.m.
When I check port 520 availabilty with NETSTAT the following is the result
# netstat -anp | grep 520
udp 0 0 0.0.0.0:520 0.0.0.0:*
6032/./ampr-ripd
Baris (TA7W)
----- Original Message -----
From: "Barış DİNÇ" <ta7w(a)antrak.org.tr>
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 2:35:38 PM
Subject: Re: [44net] GW Setup Problem
Hi Tom,
Thanks for quick reply.
I am using ampr-ripd daemon which enables the UDP 520.. I can check its existency by
command
nc -u <MY_IP> 520
Should I do something else... I am not hehind a firewall or any iother network equipment.
My gateway is directly connected to INTERNET. My server has a real IP and all ports are
open....
Thanks
baris TA7W
----- Original Message -----
From: SP2L(a)wp.pl
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 12:49:42 PM
Subject: Re: [44net] GW Setup Problem
Hello Baris.
You need to enable udp port 520 for incoming packets.
Best regards.
Tom - SP2L
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
11:42 a.m.
Hi Baris,
I think you made a typo. Your subnet is 44.176.206.0/24 , not 44.176.200.0/24
--
Title AMSAT-TR TA7W Gateway
Hostname ta7w.barisdinc.com.tr
Gateway IP 178.233.172.203
Originally added 2017-11-21 18:41:51
Last modified 2017-12-13 05:51:13
Subnet 44.176.206.0/24
--
73,
Ruben - ON3RVH
-----Original Message-----
From: 44Net [mailto:44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org] On Behalf Of Baris
DINÇ
Sent: woensdag 13 december 2017 12:36
To: 44Net <44net(a)mailman.ampr.org>
Subject: Re: [44net] GW Setup Problem
Hi Tom,
Thanks for quick reply.
I am using ampr-ripd daemon which enables the UDP 520.. I can check its existency by
command
nc -u <MY_IP> 520
Should I do something else... I am not hehind a firewall or any iother network equipment.
My gateway is directly connected to INTERNET. My server has a real IP and all ports are
open....
Thanks
baris TA7W
----- Original Message -----
From: SP2L(a)wp.pl
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 12:49:42 PM
Subject: Re: [44net] GW Setup Problem
Hello Baris.
You need to enable udp port 520 for incoming packets.
Best regards.
Tom - SP2L
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
noon
I have both the 44.176.206 (which is behind a NAT) and 44.176.200 which is directly
connected to internet..
----- Original Message -----
From: "Ruben ON3RVH" <on3rvh(a)on3rvh.be>
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 2:42:35 PM
Subject: Re: [44net] GW Setup Problem
Hi Baris,
I think you made a typo. Your subnet is 44.176.206.0/24 , not 44.176.200.0/24
--
Title AMSAT-TR TA7W Gateway
Hostname ta7w.barisdinc.com.tr
Gateway IP 178.233.172.203
Originally added 2017-11-21 18:41:51
Last modified 2017-12-13 05:51:13
Subnet 44.176.206.0/24
--
73,
Ruben - ON3RVH
-----Original Message-----
From: 44Net [mailto:44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org] On Behalf Of Baris
DINÇ
Sent: woensdag 13 december 2017 12:36
To: 44Net <44net(a)mailman.ampr.org>
Subject: Re: [44net] GW Setup Problem
Hi Tom,
Thanks for quick reply.
I am using ampr-ripd daemon which enables the UDP 520.. I can check its existency by
command
nc -u <MY_IP> 520
Should I do something else... I am not hehind a firewall or any iother network equipment.
My gateway is directly connected to INTERNET. My server has a real IP and all ports are
open....
Thanks
baris TA7W
----- Original Message -----
From: SP2L(a)wp.pl
To: "44Net" <44net(a)mailman.ampr.org>
Sent: Wednesday, December 13, 2017 12:49:42 PM
Subject: Re: [44net] GW Setup Problem
Hello Baris.
You need to enable udp port 520 for incoming packets.
Best regards.
Tom - SP2L
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2332
days inactive
2332
days old
13 comments
5 participants
participants (5)
-
Barış DİNÇ -
Brian Kantor -
Don Moore -
Ruben ON3RVH -
SP2L＠wp.pl