<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[RSS Feed]]></title><description><![CDATA[RSS Feed]]></description><link>http://direct.ecency.com</link><image><url>http://direct.ecency.com/logo512.png</url><title>RSS Feed</title><link>http://direct.ecency.com</link></image><generator>RSS for Node</generator><lastBuildDate>Tue, 28 Apr 2026 09:43:19 GMT</lastBuildDate><atom:link href="http://direct.ecency.com/created/smartedge/rss.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Smartedge: Intercontext routing dla ipv6]]></title><description><![CDATA[Configuration context local interface first-isis-intf intercontext p2p 1 ipv6 address 10::1/64 interface router-A-id loopback ipv6 address 194::100/128 router isis my-backbone net 47.0001.1111.2222.3333.00]]></description><link>http://direct.ecency.com/smartedge/@kyob/smartedte-intercontext-routing-dla-ipv6</link><guid isPermaLink="true">http://direct.ecency.com/smartedge/@kyob/smartedte-intercontext-routing-dla-ipv6</guid><category><![CDATA[smartedge]]></category><dc:creator><![CDATA[kyob]]></dc:creator><pubDate>Wed, 20 Feb 2019 12:15:48 GMT</pubDate></item><item><title><![CDATA[SSH access protection for SmartEdge]]></title><description><![CDATA[Acl added to interface 2/3 Only the SSH traffic from the 2/3 interface passes from the host 192.168.2.2 All other IP traffic from all hosts / networks is accepted by port 2/3. ! context test ! no ip]]></description><link>http://direct.ecency.com/redback/@kyob/ssh-access-protection-for-smartedge</link><guid isPermaLink="true">http://direct.ecency.com/redback/@kyob/ssh-access-protection-for-smartedge</guid><category><![CDATA[redback]]></category><dc:creator><![CDATA[kyob]]></dc:creator><pubDate>Wed, 20 Feb 2019 12:09:15 GMT</pubDate></item><item><title><![CDATA[SmartEdge: Simple NAPT configuration]]></title><description><![CDATA[Rules – how to apply NAT NAT policy should be apply to incoming traffic IP outgoing interface cannot be used in the NAT pool NAT pool must be on separate subnet (not part of interface subnet) In dynamic]]></description><link>http://direct.ecency.com/redback/@kyob/smartedge-simple-napt-configuration</link><guid isPermaLink="true">http://direct.ecency.com/redback/@kyob/smartedge-simple-napt-configuration</guid><category><![CDATA[redback]]></category><dc:creator><![CDATA[kyob]]></dc:creator><pubDate>Wed, 20 Feb 2019 12:03:48 GMT</pubDate><enclosure url="https://images.ecency.com/p/cyxkEVqiiLy2ofdgrJNxeZC3WCHPBwR7MjUDzY4kBNr81NokzziLPWBhJpsMZMtUriGfw8HeHNPNMH217WKX5GAvMziDm3KxCWoLYM3eUSLh7YGLeSaugeJcXaVnVeDho6n?format=match&amp;mode=fit" length="0" type="false"/></item><item><title><![CDATA[SmartEdge (Redback) - magic command]]></title><description><![CDATA[With this magic command washoutthewash you can get access to extra commands which are default hidden.]]></description><link>http://direct.ecency.com/smartedge/@kyob/smartedge-redback-magic-command</link><guid isPermaLink="true">http://direct.ecency.com/smartedge/@kyob/smartedge-redback-magic-command</guid><category><![CDATA[smartedge]]></category><dc:creator><![CDATA[kyob]]></dc:creator><pubDate>Sat, 12 Jan 2019 18:02:33 GMT</pubDate></item></channel></rss>