astlinux-users — AstLinux Users Mailing List

[Astlinux-users] Problems with Busybox Tar exclude

[Michael K. <mic...@ip...>]

I can for the life of me work out how to exclude a directory. 
I want to tar all /tftpboot except /tftpboot/phonefirmware and all its subdirectories.

Does anyone know the valid format?

Regards
Michael Knill

Re: [Astlinux-users] Port Forwarding FTP

[Lonnie A. <li...@lo...>]

Hi Dan, (and others)

A power-user tidbit, when performing a "Restart Firewall" from the web interface or from the CLI ...
--
arno-iptables-firewall restart
--
the current active netfilter conntrack states are maintained throughout, a very desirable feature, as such it causes minimal network disruption to users during the process.

In rare situations, particularly when changing firewall rules it may be possible a previous existing conntrack state may temporally short-circuit the firewall rule change.  BTW, not particularly unique to AstLinux, I've seen this behavior in other products as well.

If this situation has you scratching your head, you can either reboot the box or from the command line ...
--
arno-iptables-firewall stop
arno-iptables-firewall start
--
in either case the netfilter conntrack states will be flushed.

Again this is a rare situation, probably occurs more often in the lab testing, but may have occurred in your situation.

Lonnie


On Jul 28, 2017, at 9:22 AM, da...@ry... wrote:

> Good morning Lonnie and all,
>  
> Let's write this one off to pilot error.  I'm baffled why it didn't work yesterday but works today.  But we'll take it.
>  
> Sorry for the mis-fire.  Thanks for the help!
>  
> Take care,
>  
> Dan
>  
> -----Original Message-----
> From: "Lonnie Abelbeck" <li...@lo...>
> Sent: Friday, July 28, 2017 8:23am
> To: "AstLinux Users Mailing List" <ast...@li...>
> Subject: Re: [Astlinux-users] Port Forwarding FTP
> 
> Hi Dan,
> In the lab, I just tested using the following firewall rule:
> <2BF6853C-182A-4AEC-BB19-B57206F54325.png>
> It worked as expected.
> If it is possible to restrict the allowed source address (other than 0/0) that would be good.
> Lonnie
> 
> On Jul 28, 2017, at 5:32 AM, da...@ry... wrote:
> 
> Hi Lonnie,
>  
> Thanks for the prompt reply and detailed insight. We'll circle back with feedback on our findings, as requested. 
>  
> For what it's worth, we've had similar discussions with this client about reliance on FTP. They're slowly replacing it with secure protocols but progress is slow. 
>  
> Dan
>  
> -----Original Message-----
> From: "Lonnie Abelbeck" <li...@lo...>
> Sent: Thursday, July 27, 2017 9:27pm
> To: "AstLinux Users Mailing List" <ast...@li...>
> Subject: Re: [Astlinux-users] Port Forwarding FTP
> 
> Hi Dan,
> 
> My first thought is *don't do that* :-) The FTP credentials are not encrypted, easily captured, etc. . Using FTP over a VPN (OpenVPN), or use SFTP (TCP 22) would be much better choices.
> 
> If you really, really must allow FTP inbound on the external interface when AstLinux is a NAT firewall you must use "NAT EXT->LAN" of TCP 21 to your internal FTP server. The Linux kernel will automatically apply the FTP helper to track the TCP 20 data channel, so only NAT-forward TCP 21 .
> 
> Be sure to remove any "Pass EXT->LAN" TCP 21 rules.
> 
> Note that "Pass EXT->LAN" is for non-NAT'ed situations when the networks are routed, not NAT'ed. For example with IPv6 you would use "Pass EXT->LAN". For NAT'ed situations with IPv4 use "NAT EXT->LAN".
> 
> Note that with "NAT EXT->LAN" you could make the public TCP port non-standard and forward to the standard TCP 21 internally. I've never tried this, as the FTP helper has to cooperate, so this may or may not work, also depends on the FTP client.
> 
> Let us know how it goes.
> 
> Lonnie
> 
> 
> 
> On Jul 27, 2017, at 7:44 PM, da...@ry... wrote:
> 
> > All,
> > 
> > I just helped a friend reconfigure an AstLinux installation. Until today, it had been behind a NAT'd router/firewall. This afternoon, we added a NIC card and promoted AstLinux to replace the router/firewall. 
> > 
> > All the complicated bits worked fine. However, testing revealed that a simple port forwarding to an internal FTP server (port 21) isn't working. The FTP server is working from within the LAN but we can't access it from the Internet. We enabled EXT=>LAN using the web interface and we can see the rule in iptables but it doesn't seem to work. 
> > 
> > I'd appreciate any troubleshooting suggestions. 
> > 
> > Thanks,
> > 
> > Dan 
> 
> 
> <2BF6853C-182A-4AEC-BB19-B57206F54325.png>------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Port Forwarding FTP

[<da...@ry...>]

<font face="arial" size="2"><p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Good morning Lonnie and all,</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Let's write this one off to pilot error. &nbsp;I'm baffled why it didn't work yesterday but works today. &nbsp;But we'll take it.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Sorry for the mis-fire. &nbsp;Thanks for the help!</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Take care,</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Dan</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">-----Original Message-----<br />From: "Lonnie Abelbeck" &lt;li...@lo...&gt;<br />Sent: Friday, July 28, 2017 8:23am<br />To: "AstLinux Users Mailing List" &lt;ast...@li...&gt;<br />Subject: Re: [Astlinux-users] Port Forwarding FTP<br /><br /></p>
<div id="SafeStyles1501251560">Hi Dan,
<div>In the lab, I just tested using the following firewall rule:</div>
<div><img src="cid:2BF...@pr..." alt=""></div>
<div>It worked as expected.</div>
<div>If it is possible to restrict the allowed source address (other than 0/0) that would be good.</div>
<div>Lonnie</div>
<div><br />On Jul 28, 2017, at 5:32 AM, <a href="mailto:da...@ry...">da...@ry...</a> wrote:<br /><br />
<blockquote>Hi Lonnie,<br />&nbsp;<br />Thanks for the prompt reply and detailed insight. We'll circle back with feedback on our findings, as requested.&nbsp;<br />&nbsp;<br />For what it's worth, we've had similar discussions with this client about reliance on FTP. They're slowly replacing it with secure protocols but progress is slow.&nbsp;<br />&nbsp;<br />Dan<br />&nbsp;<br />-----Original Message-----<br />From: "Lonnie Abelbeck" &lt;<a href="mailto:li...@lo...">li...@lo...</a>&gt;<br />Sent: Thursday, July 27, 2017 9:27pm<br />To: "AstLinux Users Mailing List" &lt;<a href="mailto:ast...@li...">ast...@li...</a>&gt;<br />Subject: Re: [Astlinux-users] Port Forwarding FTP<br /><br />Hi Dan,<br /><br />My first thought is *don't do that* :-) The FTP credentials are not encrypted, easily captured, etc. . Using FTP over a VPN (OpenVPN), or use SFTP (TCP 22) would be much better choices.<br /><br />If you really, really must allow FTP inbound on the external interface when AstLinux is a NAT firewall you must use "NAT EXT-&gt;LAN" of TCP 21 to your internal FTP server. The Linux kernel will automatically apply the FTP helper to track the TCP 20&nbsp;data channel, so only NAT-forward TCP 21 .<br /><br />Be sure to remove any "Pass EXT-&gt;LAN" TCP 21 rules.<br /><br />Note that "Pass EXT-&gt;LAN" is for non-NAT'ed situations when the networks are routed, not NAT'ed. For example with IPv6 you would use "Pass EXT-&gt;LAN". For NAT'ed situations with IPv4 use "NAT EXT-&gt;LAN".<br /><br />Note that with "NAT EXT-&gt;LAN" you could make the public TCP port non-standard and forward to the standard TCP 21 internally. I've never tried this, as the FTP helper has to cooperate, so this may or may not work, also depends on the FTP client.<br /><br />Let us know how it goes.<br /><br />Lonnie<br /><br /><br /><br />On Jul 27, 2017, at 7:44 PM, <a href="mailto:da...@ry...">da...@ry...</a> wrote:<br /><br />&gt; All,<br />&gt;&nbsp;<br />&gt; I just helped a friend reconfigure an AstLinux installation. Until today, it had been behind a NAT'd router/firewall. This afternoon, we added a NIC card and promoted AstLinux to replace the router/firewall.&nbsp;<br />&gt;&nbsp;<br />&gt; All the complicated bits worked fine. However, testing revealed that a simple port forwarding to an internal FTP server (port 21) isn't working. The FTP server is working from within the LAN but we can't access it from the Internet. We enabled&nbsp;EXT=&gt;LAN using the web interface and we can see the rule in iptables but it doesn't seem to work.&nbsp;<br />&gt;&nbsp;<br />&gt; I'd appreciate any troubleshooting suggestions.&nbsp;<br />&gt;&nbsp;<br />&gt; Thanks,<br />&gt;&nbsp;<br />&gt; Dan&nbsp;<br /><br /><br /></blockquote>
</div>
</div></font>

Re: [Astlinux-users] Port Forwarding FTP

[<da...@ry...>]

<font face="arial" size="2"><p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Hi Lonnie,</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Thanks for the follow-up and going the extra mile. &nbsp;I tested a different installation from home this morning and it also worked as expected. &nbsp;There's clearly more to this story.</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">I'm hoping to gain access to the problematic unit sometime later this afternoon. &nbsp;This is starting to sound quite a bit like pilot error but I'll let you and the group know either way! &nbsp;&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">Dan&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">&nbsp;</p>
<p style="margin:0;padding:0;font-family: arial; font-size: 10pt; word-wrap: break-word;">-----Original Message-----<br />From: "Lonnie Abelbeck" &lt;li...@lo...&gt;<br />Sent: Friday, July 28, 2017 8:23am<br />To: "AstLinux Users Mailing List" &lt;ast...@li...&gt;<br />Subject: Re: [Astlinux-users] Port Forwarding FTP<br /><br /></p>
<div id="SafeStyles1501246603">Hi Dan,
<div>In the lab, I just tested using the following firewall rule:</div>
<div><img src="cid:2BF...@pr..." alt=""></div>
<div>It worked as expected.</div>
<div>If it is possible to restrict the allowed source address (other than 0/0) that would be good.</div>
<div>Lonnie</div>
<div><br />On Jul 28, 2017, at 5:32 AM, <a href="mailto:da...@ry...">da...@ry...</a> wrote:<br /><br />
<blockquote>Hi Lonnie,<br />&nbsp;<br />Thanks for the prompt reply and detailed insight. We'll circle back with feedback on our findings, as requested.&nbsp;<br />&nbsp;<br />For what it's worth, we've had similar discussions with this client about reliance on FTP. They're slowly replacing it with secure protocols but progress is slow.&nbsp;<br />&nbsp;<br />Dan<br />&nbsp;<br />-----Original Message-----<br />From: "Lonnie Abelbeck" &lt;<a href="mailto:li...@lo...">li...@lo...</a>&gt;<br />Sent: Thursday, July 27, 2017 9:27pm<br />To: "AstLinux Users Mailing List" &lt;<a href="mailto:ast...@li...">ast...@li...</a>&gt;<br />Subject: Re: [Astlinux-users] Port Forwarding FTP<br /><br />Hi Dan,<br /><br />My first thought is *don't do that* :-) The FTP credentials are not encrypted, easily captured, etc. . Using FTP over a VPN (OpenVPN), or use SFTP (TCP 22) would be much better choices.<br /><br />If you really, really must allow FTP inbound on the external interface when AstLinux is a NAT firewall you must use "NAT EXT-&gt;LAN" of TCP 21 to your internal FTP server. The Linux kernel will automatically apply the FTP helper to track the TCP 20&nbsp;data channel, so only NAT-forward TCP 21 .<br /><br />Be sure to remove any "Pass EXT-&gt;LAN" TCP 21 rules.<br /><br />Note that "Pass EXT-&gt;LAN" is for non-NAT'ed situations when the networks are routed, not NAT'ed. For example with IPv6 you would use "Pass EXT-&gt;LAN". For NAT'ed situations with IPv4 use "NAT EXT-&gt;LAN".<br /><br />Note that with "NAT EXT-&gt;LAN" you could make the public TCP port non-standard and forward to the standard TCP 21 internally. I've never tried this, as the FTP helper has to cooperate, so this may or may not work, also depends on the FTP client.<br /><br />Let us know how it goes.<br /><br />Lonnie<br /><br /><br /><br />On Jul 27, 2017, at 7:44 PM, <a href="mailto:da...@ry...">da...@ry...</a> wrote:<br /><br />&gt; All,<br />&gt;&nbsp;<br />&gt; I just helped a friend reconfigure an AstLinux installation. Until today, it had been behind a NAT'd router/firewall. This afternoon, we added a NIC card and promoted AstLinux to replace the router/firewall.&nbsp;<br />&gt;&nbsp;<br />&gt; All the complicated bits worked fine. However, testing revealed that a simple port forwarding to an internal FTP server (port 21) isn't working. The FTP server is working from within the LAN but we can't access it from the Internet. We enabled&nbsp;EXT=&gt;LAN using the web interface and we can see the rule in iptables but it doesn't seem to work.&nbsp;<br />&gt;&nbsp;<br />&gt; I'd appreciate any troubleshooting suggestions.&nbsp;<br />&gt;&nbsp;<br />&gt; Thanks,<br />&gt;&nbsp;<br />&gt; Dan&nbsp;<br /><br /><br /><br />------------------------------------------------------------------------------<br />Check out the vibrant tech community on one of the world's most<br />engaging tech sites, <a href="http://Slashdot.org">Slashdot.org</a>! <a href="http://sdm.link/slashdot">http://sdm.link/slashdot</a><br />_______________________________________________<br />Astlinux-users mailing list<br /><a href="mailto:Ast...@li...">Ast...@li...</a><br />https://lists.sourceforge.net/lists/listinfo/astlinux-users<br /><br />Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....<br />------------------------------------------------------------------------------<br />Check out the vibrant tech community on one of the world's most<br />engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________<br />Astlinux-users mailing list<br />Ast...@li...<br />https://lists.sourceforge.net/lists/listinfo/astlinux-users<br /><br />Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....</blockquote>
</div>
</div></font>

Re: [Astlinux-users] Port Forwarding FTP

[Lonnie A. <li...@lo...>]

Hi Dan,

In the lab, I just tested using the following firewall rule:



It worked as expected.

If it is possible to restrict the allowed source address (other than 0/0) that would be good.

Lonnie


On Jul 28, 2017, at 5:32 AM, da...@ry... wrote:

> Hi Lonnie,
>  
> Thanks for the prompt reply and detailed insight. We'll circle back with feedback on our findings, as requested. 
>  
> For what it's worth, we've had similar discussions with this client about reliance on FTP. They're slowly replacing it with secure protocols but progress is slow. 
>  
> Dan
>  
> -----Original Message-----
> From: "Lonnie Abelbeck" <li...@lo...>
> Sent: Thursday, July 27, 2017 9:27pm
> To: "AstLinux Users Mailing List" <ast...@li...>
> Subject: Re: [Astlinux-users] Port Forwarding FTP
> 
> Hi Dan,
> 
> My first thought is *don't do that* :-) The FTP credentials are not encrypted, easily captured, etc. . Using FTP over a VPN (OpenVPN), or use SFTP (TCP 22) would be much better choices.
> 
> If you really, really must allow FTP inbound on the external interface when AstLinux is a NAT firewall you must use "NAT EXT->LAN" of TCP 21 to your internal FTP server. The Linux kernel will automatically apply the FTP helper to track the TCP 20 data channel, so only NAT-forward TCP 21 .
> 
> Be sure to remove any "Pass EXT->LAN" TCP 21 rules.
> 
> Note that "Pass EXT->LAN" is for non-NAT'ed situations when the networks are routed, not NAT'ed. For example with IPv6 you would use "Pass EXT->LAN". For NAT'ed situations with IPv4 use "NAT EXT->LAN".
> 
> Note that with "NAT EXT->LAN" you could make the public TCP port non-standard and forward to the standard TCP 21 internally. I've never tried this, as the FTP helper has to cooperate, so this may or may not work, also depends on the FTP client.
> 
> Let us know how it goes.
> 
> Lonnie
> 
> 
> 
> On Jul 27, 2017, at 7:44 PM, da...@ry... wrote:
> 
> > All,
> > 
> > I just helped a friend reconfigure an AstLinux installation. Until today, it had been behind a NAT'd router/firewall. This afternoon, we added a NIC card and promoted AstLinux to replace the router/firewall. 
> > 
> > All the complicated bits worked fine. However, testing revealed that a simple port forwarding to an internal FTP server (port 21) isn't working. The FTP server is working from within the LAN but we can't access it from the Internet. We enabled EXT=>LAN using the web interface and we can see the rule in iptables but it doesn't seem to work. 
> > 
> > I'd appreciate any troubleshooting suggestions. 
> > 
> > Thanks,
> > 
> > Dan 
> 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Port Forwarding FTP

[<da...@ry...>]

Hi Lonnie,
 
Thanks for the prompt reply and detailed insight. We'll circle back with feedback on our findings, as requested. 
 
For what it's worth, we've had similar discussions with this client about reliance on FTP. They're slowly replacing it with secure protocols but progress is slow. 
 
Dan
 
-----Original Message-----
From: "Lonnie Abelbeck" <li...@lo...>
Sent: Thursday, July 27, 2017 9:27pm
To: "AstLinux Users Mailing List" <ast...@li...>
Subject: Re: [Astlinux-users] Port Forwarding FTP



Hi Dan,

My first thought is *don't do that* :-) The FTP credentials are not encrypted, easily captured, etc. . Using FTP over a VPN (OpenVPN), or use SFTP (TCP 22) would be much better choices.

If you really, really must allow FTP inbound on the external interface when AstLinux is a NAT firewall you must use "NAT EXT->LAN" of TCP 21 to your internal FTP server. The Linux kernel will automatically apply the FTP helper to track the TCP 20 data channel, so only NAT-forward TCP 21 .

Be sure to remove any "Pass EXT->LAN" TCP 21 rules.

Note that "Pass EXT->LAN" is for non-NAT'ed situations when the networks are routed, not NAT'ed. For example with IPv6 you would use "Pass EXT->LAN". For NAT'ed situations with IPv4 use "NAT EXT->LAN".

Note that with "NAT EXT->LAN" you could make the public TCP port non-standard and forward to the standard TCP 21 internally. I've never tried this, as the FTP helper has to cooperate, so this may or may not work, also depends on the FTP client.

Let us know how it goes.

Lonnie



On Jul 27, 2017, at 7:44 PM, da...@ry... wrote:

> All,
> 
> I just helped a friend reconfigure an AstLinux installation. Until today, it had been behind a NAT'd router/firewall. This afternoon, we added a NIC card and promoted AstLinux to replace the router/firewall. 
> 
> All the complicated bits worked fine. However, testing revealed that a simple port forwarding to an internal FTP server (port 21) isn't working. The FTP server is working from within the LAN but we can't access it from the Internet. We enabled EXT=>LAN using the web interface and we can see the rule in iptables but it doesn't seem to work. 
> 
> I'd appreciate any troubleshooting suggestions. 
> 
> Thanks,
> 
> Dan 



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Port Forwarding FTP

[Lonnie A. <li...@lo...>]

Hi Dan,

My first thought is *don't do that* :-)  The FTP credentials are not encrypted, easily captured, etc. .  Using FTP over a VPN (OpenVPN), or use SFTP (TCP 22) would be much better choices.

If you really, really must allow FTP inbound on the external interface when AstLinux is a NAT firewall you must use "NAT EXT->LAN" of TCP 21 to your internal FTP server.  The Linux kernel will automatically apply the FTP helper to track the  TCP 20 data channel, so only NAT-forward TCP 21 .

Be sure to remove any "Pass EXT->LAN" TCP 21 rules.

Note that "Pass EXT->LAN" is for non-NAT'ed situations when the networks are routed, not NAT'ed.  For example with IPv6 you would use "Pass EXT->LAN".  For NAT'ed situations with IPv4 use "NAT EXT->LAN".

Note that with "NAT EXT->LAN" you could make the public TCP port non-standard and forward to the standard TCP 21 internally.  I've never tried this, as the FTP helper has to cooperate, so this may or may not work, also depends on the FTP client.

Let us know how it goes.

Lonnie



On Jul 27, 2017, at 7:44 PM, da...@ry... wrote:

> All,
>  
> I just helped a friend reconfigure an AstLinux installation.  Until today, it had been behind a NAT'd router/firewall.  This afternoon, we added a NIC card and promoted AstLinux to replace the router/firewall.  
>  
> All the complicated bits worked fine. However, testing revealed that a simple port forwarding to an internal FTP server (port 21) isn't working.  The FTP server is working from within the LAN but we can't access it from the Internet.  We enabled EXT=>LAN using the web interface and we can see the rule in iptables but it doesn't seem to work.  
>  
> I'd appreciate any troubleshooting suggestions.  
>  
> Thanks,
>  
> Dan 

[Astlinux-users] Port Forwarding FTP

[<da...@ry...>]

All,
 
I just helped a friend reconfigure an AstLinux installation.  Until today, it had been behind a NAT'd router/firewall.  This afternoon, we added a NIC card and promoted AstLinux to replace the router/firewall.  
 
All the complicated bits worked fine. However, testing revealed that a simple port forwarding to an internal FTP server (port 21) isn't working.  The FTP server is working from within the LAN but we can't access it from the Internet.  We enabled EXT=>LAN using the web interface and we can see the rule in iptables but it doesn't seem to work.  
 
I'd appreciate any troubleshooting suggestions.  
 
Thanks,
 
Dan  
 

Re: [Astlinux-users] Urgent, no external access after reboot

[Michael K. <mic...@ip...>]

Whoops thanks Michael for that. Sigh!
Had a ; instead of a # for a comment in user.conf. DoH!

Regards
Michael Knill

-----Original Message-----
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Wednesday, 26 July 2017 at 4:30 pm
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Urgent, no external access after reboot

> Am 26.07.2017 um 06:15 schrieb Michael Knill <mic...@ip...>:
> 
> One of my customers power rebooted the Astlinux box and the phones are working fine but no external access.
> When I reset the firewall it comes up with:
> Firewall has Restarted. WARNING: Not all firewall rules are applied
>  
> Any ideas?
>  
> Regards
> Michael Knill

Hi Michael,

try to restart the firewall in the CLI (via SSH) to see more output and possible error messages.
Maybe a rule is wrong, or maybe the disk is corrupt …

Michael

http://www.mksolutions.info




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Urgent, no external access after reboot

[Michael K. <li...@mk...>]

> Am 26.07.2017 um 06:15 schrieb Michael Knill <mic...@ip...>:
> 
> One of my customers power rebooted the Astlinux box and the phones are working fine but no external access.
> When I reset the firewall it comes up with:
> Firewall has Restarted. WARNING: Not all firewall rules are applied
>  
> Any ideas?
>  
> Regards
> Michael Knill

Hi Michael,

try to restart the firewall in the CLI (via SSH) to see more output and possible error messages.
Maybe a rule is wrong, or maybe the disk is corrupt …

Michael

http://www.mksolutions.info

[Astlinux-users] Urgent, no external access after reboot

[Michael K. <mic...@ip...>]

One of my customers power rebooted the Astlinux box and the phones are working fine but no external access.
When I reset the firewall it comes up with:
Firewall has Restarted. WARNING: Not all firewall rules are applied

Any ideas?

Regards
Michael Knill

Re: [Astlinux-users] Persistent Host Bans On Full Reboot

[Cody A. <ald...@gm...>]

Lonnie,

Thank you for the info and the link. I am learning more as each day goes by
and each issue pops up. :)

-Cody

On Tue, Jul 25, 2017 at 5:01 PM, Lonnie Abelbeck <li...@lo...>
wrote:

>
>
> +1
>
> Cody, if you have a list of bad hosts/nets you can create a
> "/mnt/kd/blocklists/blocked-hosts.netset" file or may want to use FireHOL
> blocklists, take a read ...
>
> Firewall External Block List
> https://doc.astlinux-project.org/userdoc:tt_firewall_external_block_list
>
> Lonnie
>
>
>

Re: [Astlinux-users] Persistent Host Bans On Full Reboot

[Cody A. <ald...@gm...>]

Michael,

Thank you. I figured it was an easy fix. I just did not know what it was. :)

-Cody


On Tue, Jul 25, 2017 at 2:38 PM, Michael Keuter <li...@mk...>
wrote:

>
>
> Hi Cody,
>
> Adaptive Ban scans the /var/log/messages file for specific errors, and
> then block IP addresses.
> When you reboot by default the log files are deleted because they are
> living a temporary filesystem.
>
> You can change that, if you set "PERSISTLOG=yes" in your "user.conf" and
> reboot.
> From that point on the logs are stored in "/mnt/kd/log".
>
> ## Persistent Logs
> ## If this variable is defined, logs are saved to the keydisk instead of
> RAM
> PERSISTLOG=yes
>
> Michael
>
>
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Re: [Astlinux-users] Persistent Host Bans On Full Reboot

[Lonnie A. <li...@lo...>]

On Jul 25, 2017, at 1:38 PM, Michael Keuter <li...@mk...> wrote:

> 
>> Am 25.07.2017 um 20:26 schrieb Cody Alderson <ald...@gm...>:
>> 
>> Hi,
>> 
>> First time post to the list. I am not a pro by any stretch of the  imagination for Astlinux or Linux or Asterisk for that matter. Fortunately, telephony is a hobby rather than a way to earn a living.
>> 
>> Anyway, I noticed that Adaptive Ban does not persist with the IP host address ban upon reboot of the Asterisk box. Would you please advise me as to how to make a host ban persistent as I have a couple of IPs consistently sniffing around for a way in. I tried a few searches of the archives for an answer along with asking Ms. Google, but I could not find any definitive answers.
>> 
>> Thank you for your help.
>> 
>> Cody
> 
> Hi Cody,
> 
> Adaptive Ban scans the /var/log/messages file for specific errors, and then block IP addresses.
> When you reboot by default the log files are deleted because they are living a temporary filesystem.
> 
> You can change that, if you set "PERSISTLOG=yes" in your "user.conf" and reboot.
> From that point on the logs are stored in "/mnt/kd/log".
> 
> ## Persistent Logs
> ## If this variable is defined, logs are saved to the keydisk instead of RAM
> PERSISTLOG=yes
> 
> Michael

+1

Cody, if you have a list of bad hosts/nets you can create a "/mnt/kd/blocklists/blocked-hosts.netset" file or may want to use FireHOL blocklists, take a read ...

Firewall External Block List
https://doc.astlinux-project.org/userdoc:tt_firewall_external_block_list

Lonnie

Re: [Astlinux-users] Persistent Host Bans On Full Reboot

[Michael K. <li...@mk...>]

> Am 25.07.2017 um 20:26 schrieb Cody Alderson <ald...@gm...>:
> 
> Hi,
> 
> First time post to the list. I am not a pro by any stretch of the  imagination for Astlinux or Linux or Asterisk for that matter. Fortunately, telephony is a hobby rather than a way to earn a living.
> 
> Anyway, I noticed that Adaptive Ban does not persist with the IP host address ban upon reboot of the Asterisk box. Would you please advise me as to how to make a host ban persistent as I have a couple of IPs consistently sniffing around for a way in. I tried a few searches of the archives for an answer along with asking Ms. Google, but I could not find any definitive answers.
> 
> Thank you for your help.
> 
> Cody

Hi Cody,

Adaptive Ban scans the /var/log/messages file for specific errors, and then block IP addresses.
When you reboot by default the log files are deleted because they are living a temporary filesystem.

You can change that, if you set "PERSISTLOG=yes" in your "user.conf" and reboot.
From that point on the logs are stored in "/mnt/kd/log".

## Persistent Logs
## If this variable is defined, logs are saved to the keydisk instead of RAM
PERSISTLOG=yes

Michael

http://www.mksolutions.info

[Astlinux-users] Persistent Host Bans On Full Reboot

[Cody A. <ald...@gm...>]

Hi,

First time post to the list. I am not a pro by any stretch of the
imagination for Astlinux or Linux or Asterisk for that matter. Fortunately,
telephony is a hobby rather than a way to earn a living.

Anyway, I noticed that Adaptive Ban does not persist with the IP host
address ban upon reboot of the Asterisk box. Would you please advise me as
to how to make a host ban persistent as I have a couple of IPs consistently
sniffing around for a way in. I tried a few searches of the archives for an
answer along with asking Ms. Google, but I could not find any definitive
answers.

Thank you for your help.

Cody

Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13

[Michael K. <mic...@ip...>]

At this stage if I cant get any help from Digium or any other Asterisk guru then I will be reverting to Asterisk 11.
Im a bit annoyed actually. 11 is EoL in a couple of months time and I cant get any reasonable support for a core module in a current LTS release.

Regards
Michael Knill

-----Original Message-----
From: Michael Knill <mic...@ip...>
Reply-To: AstLinux List <ast...@li...>
Date: Friday, 21 July 2017 at 1:44 pm
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13

Hmm so it obviously works in Astlinux! I use chan_sip
Why are your counts so low. Stuffed if I know what is doing it!

Yes I have pulled out all cel, pjsip, hep and ari modules and also the ones you have below.

Still working on it (

Regards
Michael Knill

-----Original Message-----
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Thursday, 20 July 2017 at 5:55 pm
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13

> Am 20.07.2017 um 08:13 schrieb Michael Knill <mic...@ip...>:
> 
> core show taskprocessors
> 
> Processor                                      Processed   In Queue  Max Depth  Low water High water
> subm:ast_channel_topic_all-00000039                 5188          0        631        450        500
> subm:ast_channel_topic_all-cached-00000034          8091          0       1031        450        500
> subm:ast_channel_topic_all-cached-00000036          8090          0       1031        450        500
> 
> Why so many?
> 
> Regards
> Michael Knill

Michael,

are you using PJSIP or chan_sip on the Asterisk 13 box?
I run Asterisk 13 for about a year successfully on my office PBX with chan_sip.

Here is a list of a few modules that I don't load in Asterisk 13:

-----
noload => res_mwi_external.so ; Asterisk 13
noload => res_mwi_external_ami.so ;  Asterisk 13
noload => res_ari_mailboxes.so ; Asterisk 13
noload => res_pjsip*.so ; Asterisk 13
noload => func_pjsip*.so ; Asterisk 13
noload => res_pjsip_phoneprov_provider.so ; Asterisk 13
noload => res_pktccops.so
noload => cel_custom.so
-----

Maybe that changes something.
Otherwise we could compare some configs …

For comparison:

-----
core show taskprocessors

Processor                                      Processed   In Queue  Max Depth  Low water High water
...
...
subm:ast_channel_topic_all-0000007d                 6440          0         15        450        500
subm:ast_channel_topic_all-cached-00000076          9520          0         25        450        500
subm:ast_channel_topic_all-cached-00000078          9519          0         25        450        500
...
...
135 taskprocessors
-----

> -----Original Message-----
> From: Michael Knill <mic...@ip...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 20 July 2017 at 3:52 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13
> 
> Nope removing all those modules didn't fix it. Sigh!
> 
> Regards
> Michael Knill
> 
> -----Original Message-----
> From: Michael Knill <mic...@ip...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 20 July 2017 at 2:50 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13
> 
> No I don't want to stay with 11 as its basically EoS and I want to move forward with the next LTS release.
> We are going to have a big push in the near future to get new systems in and I don't want to be going through this headache with more systems (
> 
> Yes it could be something to do with my configuration. Hmm slow AMI handler. That's a thought!
> From the URL you posted, I also decided I would remove ARI modules as well. I don't see me using it in the near future as I can do everything via AMI.
> 
> Regards
> Michael Knill
> 
> -----Original Message-----
> From: Lonnie Abelbeck <li...@lo...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 20 July 2017 at 1:12 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13
> 
> Michael,
> 
> Is rolling back to Asterisk 11 a possibility for you, or are you using some of the new 13 features ?
> 
> If you are the only person reporting this task processor warning in AstLinux, it may be a configuration issue, slow AMI handler, etc. unique to your setup.
> 
> http://lists.digium.com/pipermail/asterisk-dev/2016-June/075616.html
> 
> Lonnie
> 
> 
> On Jul 19, 2017, at 9:33 PM, Michael Knill <mic...@ip...> wrote:
> 
>> No nothing I could find that actually helped. I really cant see that it is a resource issue.
>> I have posted a message on the forum but Im not hopeful (
>> 
>> In a bit of a pickle as I have a major customer waiting for this release. 
>> 
>> Regards
>> Michael Knill
>> 
>> -----Original Message-----
>> From: Lonnie Abelbeck <li...@lo...>
>> Reply-To: AstLinux List <ast...@li...>
>> Date: Thursday, 20 July 2017 at 10:36 am
>> To: AstLinux List <ast...@li...>
>> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13
>> 
>> Michael,
>> 
>> Is there any pattern to get the warnings, like low RAM or low-end CPU ?
>> 
>> Try googling "task processor queue reached 500 scheduled tasks again" , there are a lot of results related to this.
>> 
>> Lonnie
>> 
>> 
>> On Jul 19, 2017, at 7:06 PM, Michael Knill <mic...@ip...> wrote:
>> 
>>> Ah I am getting it on my non VM sites too. I will try with PJSIP, HEP and CEL modules not loaded.
>>> Its statsis that is complaining but I actually cant work out whether I need it or not? It's the new message bus architecture but is it in place of the old or just a new one you can use?
>>> I use CDR and AMI so I need some form of this messaging architecture!
>>> 
>>> Regards
>>> Michael Knill
>>> 
>>> -----Original Message-----
>>> From: Michael Knill <mic...@ip...>
>>> Reply-To: AstLinux List <ast...@li...>
>>> Date: Thursday, 20 July 2017 at 8:02 am
>>> To: AstLinux List <ast...@li...>
>>> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13
>>> 
>>> Thanks Lonnie. Perfect info. 
>>> I will let you know how I go.
>>> 
>>> Regards
>>> Michael Knill
>>> 
>>> -----Original Message-----
>>> From: Lonnie Abelbeck <li...@lo...>
>>> Reply-To: AstLinux List <ast...@li...>
>>> Date: Wednesday, 19 July 2017 at 10:29 pm
>>> To: AstLinux List <ast...@li...>
>>> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk 13
>>> 
>>> Hi Michael,
>>> 
>>> Not an issue with Asterisk 11 :-)
>>> 
>>> Here is what Digium says about taskprocessors warnings ...
>>> 
>>> Asterisk Task Processor Queue Size Warnings
>>> http://blogs.asterisk.org/2016/07/13/asterisk-task-processor-queue-size-warnings/
>>> 
>>> Is the VM configured with only one CPU or core ?
>>> 
>>> Lonnie
>>> 
>>> 
>>> 
>>> On Jul 19, 2017, at 7:10 AM, Michael Knill <mic...@ip...> wrote:
>>> 
>>>> Hi all
>>>> 
>>>> Im not getting these errors on any other sites I have upgraded including a VM site like this one but here they are:
>>>> 
>>>> Jul 19 14:22:40 3017-Biz_Doctor-CM1 local0.warn asterisk[1107]: WARNING[8574][C-000001aa]: taskprocessor.c:888 in taskprocessor_push: The 'subm:ast_channel_topic_all-cached-00000079' task processor queue reached 500 scheduled tasks again.
>>>> Jul 19 14:22:40 3017-Biz_Doctor-CM1 local0.warn asterisk[1107]: WARNING[8576][C-000001aa]: taskprocessor.c:888 in taskprocessor_push: The 'subm:ast_channel_topic_all-0000007e' task processor queue reached 500 scheduled tasks again.
>>>> Jul 19 14:49:51 3017-Biz_Doctor-CM1 local0.warn asterisk[1107]: WARNING[8787][C-000001b0]: taskprocessor.c:888 in taskprocessor_push: The 'subm:ast_channel_topic_all-cached-0000007b' task processor queue reached 500 scheduled tasks again.
>>>> 
>>>> Im struggling to find what they mean. Any ideas anyone?
>>>> 
>>>> Regards
>>>> Michael Knill

Michael

http://www.mksolutions.info




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Astlinux web interface

[Michael K. <li...@mk...>]

> Am 23.07.2017 um 20:25 schrieb Lonnie Abelbeck <li...@lo...>:
> 
> 
> On Jul 23, 2017, at 12:11 PM, Roberto Rivera <rri...@gm...> wrote:
> 
>> I'm using a Alix board for a pbx. I want to assign it a static up address but I'm can't see the device on my Netgear list of devices. How can I obtain a IP address to be able to log into your web interface.
>> Thanks 
> 
> Roberto,
> 
> If your web browser is on the same subnet as the Alix's (eth0) interface, try 'pbx.local' to use mDNS (Bonjour) zeroconf to access the AstLinux web interface for setup.  This should work with OS-X, Chromebooks, not sure about Windows.
> 
> Better, would be to connect a serial cable to the Alix's serial port (38400 8N1) and after it boots up the IPv4 address will be displayed (if available), or log in with the default credentials and issue "ip a" to determinate the external IPv4 address.
> 
> Also consider you may have plugged the ethernet cable into eth2 and not the default eth0 interface.
> 
> Lonnie

eth0 is next to the USB ports:

https://wiki.openwrt.org/_detail/media/pcengines/box-closed-front2.jpg?id=toh%3Apcengines%3Aalix

Michael

http://www.mksolutions.info

Re: [Astlinux-users] directmedia not working

[Michael K. <li...@mk...>]

> Am 23.07.2017 um 22:15 schrieb Michael Knill <mic...@ip...>:
> 
> Thanks Michael. He has an opposite problem to me. I cant get it to do directmedia.

There are more issues with "directmedia" in the issue list URL …

> I don't really need it at this stage but one day I will have a customer that its going to be an issue for.
> And it should just work anyway! It used to previously. 
> 
> Regards
> Michael Knill
> 
> -----Original Message-----
> From: Michael Keuter <li...@mk...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Sunday, 23 July 2017 at 9:35 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] directmedia not working
> 
>> Am 23.07.2017 um 13:26 schrieb Michael Knill <mic...@ip...>:
>> 
>> Gosh having lots of issues with the new release.
>> 
>> Can anyone think of anything other than the following that would cause directmedia=yes to not work:
>> 	• Compatible codecs
>> 	• Dial Options e.g. T,t ,L etc
>> 	• Video
>> 	• DTMF
>> 
>> Regards
>> Michael Knill
> 
> Hi Michael,
> 
> I never use "directmedia=yes",
> 
> but maybe it is worth looking here:
> 
> https://issues.asterisk.org/jira/browse/ASTERISK-24657?jql=project%20%3D%20ASTERISK%20AND%20text%20~%20%22directmedia%22
> 
> Michael

Michael

http://www.mksolutions.info

Re: [Astlinux-users] directmedia not working

[Michael K. <mic...@ip...>]

Thanks Lonnie. No this is just an extension to extension call.

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Sunday, 23 July 2017 at 10:21 pm
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] directmedia not working


On Jul 23, 2017, at 6:26 AM, Michael Knill <mic...@ip...> wrote:

> Gosh having lots of issues with the new release.
>  
> Can anyone think of anything other than the following that would cause directmedia=yes to not work:
> 	• Compatible codecs
> 	• Dial Options e.g. T,t ,L etc
> 	• Video
> 	• DTMF

Non-transparent network path, ie NAT or SIP ALG's in the path.

I always use "directmedia=no", that also allows asterisk/features.conf to work with Asterisk in the path.

Lonnie


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] directmedia not working

[Michael K. <mic...@ip...>]

Thanks Michael. He has an opposite problem to me. I cant get it to do directmedia.
I don't really need it at this stage but one day I will have a customer that its going to be an issue for.
And it should just work anyway! It used to previously. 

Regards
Michael Knill

-----Original Message-----
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Sunday, 23 July 2017 at 9:35 pm
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] directmedia not working

> Am 23.07.2017 um 13:26 schrieb Michael Knill <mic...@ip...>:
> 
> Gosh having lots of issues with the new release.
>  
> Can anyone think of anything other than the following that would cause directmedia=yes to not work:
> 	• Compatible codecs
> 	• Dial Options e.g. T,t ,L etc
> 	• Video
> 	• DTMF
>  
> Regards
> Michael Knill

Hi Michael,

I never use "directmedia=yes",

but maybe it is worth looking here:

https://issues.asterisk.org/jira/browse/ASTERISK-24657?jql=project%20%3D%20ASTERISK%20AND%20text%20~%20%22directmedia%22

Michael

http://www.mksolutions.info




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Astlinux web interface

[Lonnie A. <li...@lo...>]

On Jul 23, 2017, at 12:11 PM, Roberto Rivera <rri...@gm...> wrote:

> I'm using a Alix board for a pbx. I want to assign it a static up address but I'm can't see the device on my Netgear list of devices. How can I obtain a IP address to be able to log into your web interface.
> Thanks 

Roberto,

If your web browser is on the same subnet as the Alix's (eth0) interface, try 'pbx.local' to use mDNS (Bonjour) zeroconf to access the AstLinux web interface for setup.  This should work with OS-X, Chromebooks, not sure about Windows.

Better, would be to connect a serial cable to the Alix's serial port (38400 8N1) and after it boots up the IPv4 address will be displayed (if available), or log in with the default credentials and issue "ip a" to determinate the external IPv4 address.

Also consider you may have plugged the ethernet cable into eth2 and not the default eth0 interface.

Lonnie

[Astlinux-users] Astlinux web interface

[Roberto R. <rri...@gm...>]

I'm using a Alix board for a pbx. I want to assign it a static up address but I'm can't see the device on my Netgear list of devices. How can I obtain a IP address to be able to log into your web interface.
Thanks 


Sent from my iPhone

Re: [Astlinux-users] directmedia not working

[Lonnie A. <li...@lo...>]

On Jul 23, 2017, at 6:26 AM, Michael Knill <mic...@ip...> wrote:

> Gosh having lots of issues with the new release.
>  
> Can anyone think of anything other than the following that would cause directmedia=yes to not work:
> 	• Compatible codecs
> 	• Dial Options e.g. T,t ,L etc
> 	• Video
> 	• DTMF

Non-transparent network path, ie NAT or SIP ALG's in the path.

I always use "directmedia=no", that also allows asterisk/features.conf to work with Asterisk in the path.

Lonnie

Re: [Astlinux-users] directmedia not working

[Michael K. <li...@mk...>]

> Am 23.07.2017 um 13:26 schrieb Michael Knill <mic...@ip...>:
> 
> Gosh having lots of issues with the new release.
>  
> Can anyone think of anything other than the following that would cause directmedia=yes to not work:
> 	• Compatible codecs
> 	• Dial Options e.g. T,t ,L etc
> 	• Video
> 	• DTMF
>  
> Regards
> Michael Knill

Hi Michael,

I never use "directmedia=yes",

but maybe it is worth looking here:

https://issues.asterisk.org/jira/browse/ASTERISK-24657?jql=project%20%3D%20ASTERISK%20AND%20text%20~%20%22directmedia%22

Michael

http://www.mksolutions.info