<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" color="#000000" face="Tahoma,sans-serif">Brian,<br><br> You do need the port forwarding set to the correct IP for echolink to work.<br><br>You either need to use static IP in the RPi2 or better yet static dhcp in the router. The router can be setup to assign the same IP each time based on the mac address of the RPi2.<br><br>Do 'ip a' at the linux prompt of your RPi2. Look under eth0 for inet addr - that is your assigned RPi2 IP address on your lan. This is the address you need to port forward to in your router for echolink, iax, ssh, etc.<br id="FontBreak"></font><br><font style="" face="Tahoma,sans-serif">But again if this address is not setup static as I mentioned above at one end or the other it can change and then whatever port forwarding you set would not be valid.</font><br><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div>> From: TxLawMan@aol.com<br>> To: arm-allstar@hamvoip.org<br>> Date: Mon, 2 Nov 2015 11:26:23 -0600<br>> Subject: Re: [arm-allstar] arm-allstar Digest, Vol 18, Issue 1<br>> <br>> Hey Doug,<br>> <br>> It's kind of odd looking. The IP address originally assigned to my RPi2 was<br>> 192.168.1.108. That looks like it is still connected to my router. Looking<br>> in ifconfig, it looks like the dongle reassigned the RPi2 the 127.0.0.1 IP<br>> address.<br>> <br>> I don't see anything (IN MY ROUTER) that looks like the IOGear dongle is<br>> connecting, but I did initially set it up with my laptop (with the WIFI<br>> turned off) and it worked. Now that I have it on the RPi2, I am able to make<br>> connections via the Allstar node, so it is connected to internet. I just<br>> can't do anything with the Echolink side of it. <br>> <br>> On my cell phone, the wifi is turned off. I read that you could not have<br>> more than one instance of Echolink from the same public IP.<br>> <br>> I'm about to go home for lunch. I'll see if I can get the dongle assigned an<br>> IP from the router, and get the 192.168.1.108 IP flowing through there.<br>> <br>> Brian<br>> KC5YSM<br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Sun, 1 Nov 2015 17:28:57 -0600<br>> From: "B. Cater" <TxLawMan@aol.com><br>> To: "Arm-Allstar Email List" <arm-allstar@hamvoip.org><br>> Subject: [arm-allstar] RE Echolink Server Reporting issues<br>> Message-ID: <00d501d114fd$1569c630$403d5290$@aol.com><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> Update:<br>> <br>> <br>> <br>> I connected an Ethernet cable back up and at the same time changed the<br>> server names, as a friend had suggested. It then reported to the server, but<br>> I cannot connect from my cellphone app vis the phone data system (not my<br>> wifi).<br>> <br>> <br>> <br>> I connected the dongle back in place of the cable and had the same result. I<br>> guess my reporting issue was the server names. I had changed them before but<br>> I had added a fourth one and I guess it didn't like that.<br>> <br>> <br>> <br>> Now to figure out why I can't actually use it no, even though it's<br>> reporting.<br>> <br>> <br>> <br>> Without amateur radio, I would be trying to think of something to do, haha!<br>> <br>> <br>> <br>> Brian<br>> <br>> KC5YSM<br>> <br>> Allstar Node: 42045<br>> <br>> Echo node: 450004<br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20151101/9b2a94d<br>> a/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Sun, 1 Nov 2015 22:02:30 -0500<br>> From: Doug Crompton <doug@crompton.com><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Subject: Re: [arm-allstar] RE Echolink Server Reporting issues<br>> Message-ID: <BLU171-W1173B289464796F845EACBEBA2C0@phx.gbl><br>> Content-Type: text/plain; charset="windows-1252"<br>> <br>> Brian,<br>> <br>> If it reports 127.0.0.1 it is not getting an IP address from the router and<br>> it would not work. You should be assigned a valid address for the RPi2<br>> whether it is connected wired or wireless. I assume your router assigns<br>> 192.168.x.x addresses.<br>> <br>> Make sure the IOgear is actually wireless connecting to your router. Try it<br>> with another computer or device.<br>> <br>> If echolink is working you should be able to display the downloaded database<br>> in the Asterisk client -<br>> <br>> asterisk -rvvv<br>> <br>> echolink dbdump<br>> <br>> When you say cellphone is not working - do you mean echolink via cell?<br>> <br>> Remember you can't use wifi to connect echolink to your node as both would<br>> then be on the same network.<br>> <br>> There is no port forwarding in the IOgear just in your router.<br>> 73 Doug<br>> WA3DSP<br>> http://www.crompton.com/hamradio<br>> <br>> <br>> From: TxLawMan@aol.com<br>> To: arm-allstar@hamvoip.org<br>> Date: Sun, 1 Nov 2015 17:28:57 -0600<br>> Subject: [arm-allstar] RE Echolink Server Reporting issues<br>> <br>> Update: I connected an Ethernet cable back up and at the same time changed<br>> the server names, as a friend had suggested. It then reported to the server,<br>> but I cannot connect from my cellphone app vis the phone data system (not my<br>> wifi). I connected the dongle back in place of the cable and had the same<br>> result. I guess my reporting issue was the server names. I had changed them<br>> before but I had added a fourth one and I guess it didn?t like that. Now to<br>> figure out why I can?t actually use it no, even though it?s reporting.<br>> Without amateur radio, I would be trying to think of something to do, haha!<br>> BrianKC5YSMAllstar Node: 42045Echo node: 450004 <br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> Visit the BBB and RPi2 web page - http://hamvoip.org<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20151101/344bb00<br>> 0/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> <br>> End of arm-allstar Digest, Vol 18, Issue 1<br>> ******************************************<br>> <br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> Visit the BBB and RPi2 web page - http://hamvoip.org<br>> <br></div> </div></body>
</html>