[nos-bbs] Encap port number

[Bob Tenty]

it is not a port but a protocol encap is protocol 4 also called IPENCAP
nowadays.

You can also route the 44 addresses over your AXIP link with a simple
route command like

route add  44.163.22.2  your-axip-interface

etc.

No encap necessary.



73,

Bob VE3TOK



On 14-02-13 09:54 PM, Jose Ng Lee wrote:
> I am doing some testing with Encap between my Raspberry Pi Jnos and PC
> Ubuntu Jnos.
>  
> RPI with IP 44.163.22.12
> route addprivate 44.163.22.2/32 encap 200.46.129.3
>  
> PC with IP 44.163.22.2
> route addprivate 44.163.22.12/32 encap 200.46.129.4
>  
> Both machine, I am able to do telnet from outside to the Commercial
> address.   Both machine have an AXIP wormhole link to each other and
> working OK.
>  
> My problem is encap.  I do a Ping from 44.163.22.12 to 44.163.22.2
> machine and viceversa and no response.
>  
> Both machine have Shorewall/Shoreline Firewall with same rules.  When
> I Clear both Firewall (no rules), I am able to Ping one another and
> also telnet one another with the 44 IP.  So, My assumption is that the
> Firewall is blocking the Encap.
>  
> I searched in Google but cannot find if JNOS Encap uses a special port
> or what is the port number so I can habilitate it in the Firewall.  Or
> if in the Shorewall Firewall, Network interfaces options I should
> check some of those options to make the Encap work.
>  
> Thanks,
> José / HP2AT
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20140214/68f216fa/attachment.html>