├── .gitignore ├── README.md ├── guides.md ├── guides ├── draytek.md ├── draytek │ ├── kpn.md │ ├── kpn │ │ ├── kpn-internet.md │ │ └── routed-iptv.md │ ├── online.md │ ├── online │ │ └── online-internet-only.md │ ├── solcon.md │ ├── solcon │ │ └── solcon-internet-only.md │ ├── t-mobile.md │ └── t-mobile │ │ └── tmobile-internet-only.md ├── mikrotik.md ├── mikrotik │ ├── code-snippets.md │ ├── code-snippets │ │ ├── block-port-scanners.md │ │ ├── default-firewall-ipv6.md │ │ ├── default-firewall.md │ │ ├── fasttrack.md │ │ ├── set-ntp.md │ │ └── v7-multi-wan.md │ ├── delta.md │ ├── delta │ │ └── Mikrotik-Internet-Only.md │ ├── kpn.md │ ├── kpn │ │ ├── Mikrotik-Internet-only.md │ │ ├── Mikrotik-toevoegen-van-ipv6-aan-internet-only.md │ │ ├── Mikrotik-tv-settings-with-vlan.md │ │ ├── Mikrotik-tv-settings.md │ │ └── Mikrotik-voice-telephony.md │ ├── online.md │ ├── online │ │ └── Mikrotik-Internet-only.md │ ├── solcon.md │ ├── solcon │ │ └── Mikrotik-Internet-only.md │ ├── t-mobile.md │ ├── t-mobile │ │ └── Mikrotik-Internet-only.md │ ├── ziggo.md │ └── ziggo │ │ └── Mikrotik-internet-only.md ├── opnsense.md ├── opnsense │ ├── kpn.md │ ├── kpn │ │ ├── opnsense-with-vlan.md │ │ └── opnsense-without-vlan.md │ ├── online.md │ └── online │ │ └── opnsense-internet-only.md ├── pfsense.md └── pfsense │ ├── kpn.md │ └── kpn │ ├── pfSense-ipv6.md │ ├── pfSense-with-vlan.md │ └── pfSense-without-vlan.md ├── home.md └── images ├── kpn ├── draytek │ ├── fiber1.png │ ├── fiber2.png │ ├── igmp1.png │ ├── igmp2.png │ ├── igmp3.png │ ├── image.png │ ├── routed1.png │ ├── routed2.png │ ├── routed3.png │ ├── routed4.png │ ├── routed5.png │ ├── routediptvondersteuning.png │ ├── vdsl1.png │ └── vdsl2.png ├── opnsense-with-vlan │ ├── assignments.png │ ├── dhcp4.png │ ├── dhcp4additional.png │ ├── dhcp4range.png │ ├── fwiptvwan.png │ ├── fwlan.png │ ├── fwnatoutbound.png │ ├── fwnatoutboundrule.png │ ├── fwupdate.png │ ├── igmpproxy.png │ ├── interfacelaniptv.png │ ├── interfacewan.png │ ├── interfacewaniptv.png │ ├── plugins.png │ └── vlans.png ├── opnsense-without-vlan │ ├── assignments.png │ ├── dhcp4.png │ ├── dhcp4additional.png │ ├── fwiptvwan.png │ ├── fwlan.png │ ├── fwnatoutbound.png │ ├── fwnatoutboundrule.png │ ├── fwupdate.png │ ├── igmpproxy.png │ ├── interfacewan.png │ ├── interfacewaniptv.png │ ├── plugins.png │ └── vlans.png ├── pfsense-ipv6 │ ├── dhcp6clientconfiguration.png │ ├── dhcpv6ra.png │ ├── dhcpv6serverv2.png │ ├── fwlan.png │ ├── fwlanicmp4.png │ ├── fwlanicmp6.png │ ├── fwwan.png │ ├── fwwanicmp.png │ ├── fwwanicmp4.png │ ├── fwwanlinklocal.png │ ├── interfacelan.png │ ├── interfacewan.png │ ├── interfacewan_pppoe.png │ ├── ipv6configtype.png │ ├── ipv6configtypelan.png │ ├── ipv6test.png │ └── trackipv6interface.png ├── pfsense-with-vlan │ ├── allowipoptions.png │ ├── dhcpiptvvlan.png │ ├── dhcpiptvvlanbootp.png │ ├── dhcpiptvvlandns.png │ ├── dhcpiptvvlanother.png │ ├── fwiptvvlan.png │ ├── fwiptvwan.png │ ├── igmp.png │ ├── interfaces.png │ ├── interfacevlaniptv.png │ ├── interfacevlans.png │ ├── leaserequirementsandrequests.png │ ├── natoutbound.png │ ├── natoutboundmappings.png │ └── ppp.png └── pfsense-without-vlan │ ├── additional-bootp-dhcp.png │ ├── assignments.png │ ├── firewalllan.png │ ├── igmpproxy.png │ ├── ipoptions.png │ ├── outbound.png │ ├── ppp.png │ ├── rules-wan.png │ ├── tv_kpn.png │ └── vlans.png ├── online ├── draytek-internet-only │ ├── online1.png │ ├── online2.png │ └── online3.png └── opnsense-internet-only │ ├── gateway.png │ ├── iface_assignments.png │ ├── iface_other_vlan.png │ └── iface_wan.png ├── site ├── 121258543.png ├── dark.png ├── dashboard_pfsense_2.6.0.jpg ├── delta.png ├── draytek.png ├── kpn.jpg ├── mikrotik.png ├── online.png ├── opnsense_dashboard_v16_7b.png ├── solcon.png ├── t-mobile.png └── ziggo.jpg ├── solcon ├── solcon1.png ├── solcon2.png ├── solcon3.png └── solcon4.png └── tmobile ├── tmobile1.png └── tmobile2.png /.gitignore: -------------------------------------------------------------------------------- 1 | .obsidian -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: EIGENROUTER.NL - Table of Content 3 | description: Table of Content for Routers / ISP Guides 4 | published: true 5 | date: 2023-04-22T15:22:27.177Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T14:52:02.218Z 9 | --- 10 | 11 | # EIGENROUTER.NL 12 | 13 | Detailed how-to information about setting up Internet, IPTV & VoIP on your own router from different ISPs. 14 | 15 | We will update this repo with more types of routers to become a central place to find information. 16 | 17 | If you have interest / knowledge in this area and want to help other people, leave a message for us so we can add you as a contributor! 18 | 19 | Join our Discord server @ [https://discord.gg/jfwsQUgU9e](https://discord.gg/jfwsQUgU9e) 20 | 21 | ## TABLE OF CONTENT 22 | 23 | - EIGENROUTER.NL 24 | - [pfSense](#pfsense) 25 | - [KPN](#kpn) 26 | - [Ziggo](#ziggo) 27 | - [T-Mobile](#t-mobile) 28 | - [OPNsense](#opnsense) 29 | - [KPN](#kpn-1) 30 | - [Ziggo](#ziggo-1) 31 | - [T-Mobile](#t-mobile-1) 32 | - [Online](#online) 33 | - [Mikrotik](#mikrotik) 34 | - [code-snippets](#code-snippets) 35 | - [KPN](#kpn-2) 36 | - [Ziggo](#ziggo-2) 37 | - [T-Mobile](#t-mobile-2) 38 | - [Solcon](#solcon) 39 | - [Online](#online-1) 40 | - [Delta](#delta) 41 | - [Draytek](#Draytek) 42 | - [KPN](#kpn-3) 43 | - [T-Mobile](#t-mobile-3) 44 | - [Solcon](#solcon-1) 45 | - [Online](#online-2) 46 | ## pfSense 47 | 48 | ### KPN 49 | * [pfSense without seperate TV VLAN](/guides/pfsense/kpn/pfSense-without-vlan.md) 50 | * [pfSense with seperate TV VLAN](/guides/pfsense/kpn/pfSense-with-vlan.md) 51 | * [pfSense KPN IPv6](/guides/pfsense/kpn/pfSense-ipv6.md) 52 | 53 | ## OPNsense 54 | 55 | ### KPN 56 | * [OPNsense without separate TV VLAN](/guides/opnsense/kpn/opnsense-without-vlan.md) 57 | * [OPNsense with TV VLAN](/guides/opnsense/kpn/opnsense-with-vlan.md) 58 | 59 | ### Online 60 | * [OPNsense internet only configuration](/guides/opnsense/online/opnsense-internet-only.md) 61 | 62 | ## Mikrotik 63 | 64 | ### code-snippets 65 | * [block-port-scanners](/guides/mikrotik/code-snippets/block-port-scanners.md) 66 | * [fasttrack](/guides/mikrotik/code-snippets/fasttrack.md) 67 | * [set-ntp](/guides/mikrotik/code-snippets/set-ntp.md) 68 | * [v7-multi-wan](/guides/mikrotik/code-snippets/v7-multi-wan.md) 69 | * [default firewall](/guides/mikrotik/code-snippets/default-firewall.md) 70 | * [default ipv6 firewall](/guides/mikrotik/code-snippets/default-firewall-ipv6.md) 71 | ### KPN 72 | * [Mikrotik internet only](/guides/mikrotik/kpn/Mikrotik-Internet-only.md) 73 | * [Mikrotik TV configuration](/guides/mikrotik/kpn/Mikrotik-tv-settings.md) 74 | * [Mikrotik TV configuration With Vlan](/guides/mikrotik/kpn/Mikrotik-tv-settings-with-vlan.md) 75 | * [Mikrotik Add IPv6 To Internet](/guides/mikrotik/kpn/Mikrotik-toevoegen-van-ipv6-aan-internet-only.md) 76 | * [Mikrotik voice / telephony](/guides/mikrotik/kpn/Mikrotik-voice-telephony.md) 77 | 78 | ### Ziggo 79 | * [Mikrotik internet only](/guides/mikrotik/ziggo/Mikrotik-internet-only.md) 80 | 81 | ### T-Mobile 82 | * [Mikrotik internet only](/guides/mikrotik/t-mobile/Mikrotik-Internet-only.md) 83 | 84 | ### Solcon 85 | * [Solcon Internet only](/guides/mikrotik/solcon/Mikrotik-Internet-only.md) 86 | 87 | ### Online 88 | * [Online Internet only](/guides/mikrotik/online/Mikrotik-Internet-only.md) 89 | 90 | ### Delta 91 | 92 | * [Delta Internet only](/guides/mikrotik/delta/Mikrotik-Internet-Only.md) 93 | 94 | ## Draytek 95 | 96 | ### KPN 97 | * [Draytek Internet Only](/guides/draytek/kpn/kpn-internet.md) 98 | * [Draytek Routed IPTV KPN](/guides/draytek/kpn/routed-iptv.md) 99 | 100 | ### T-Mobile 101 | * [T-Mobile Internet Only](/guides/draytek/t-mobile/tmobile-internet-only.md) 102 | 103 | ### Solcon 104 | * [Solcon Internet Only](/guides/draytek/solcon/solcon-internet-only.md) 105 | 106 | ### Online 107 | * [Online Internet Only](/guides/draytek/online/online-internet-only.md) 108 | 109 | ## Contributing 110 | 111 | Check this project @ [GitHub.com](https://github.com/Eigenrouter/eigenrouter) to contribute. 112 | 113 | Pull requests, bug fixes, and new features are welcome! 114 | 115 | ``` 116 | Fork the repository 117 | Create your feature branch (git checkout -b my-new-feature) 118 | Add the files ( git add .) 119 | Commit your changes (git commit -a -m 'Add some feature') 120 | Push to the branch (git push origin my-new-feature) 121 | Create new Pull Request on GitHub 122 | ``` 123 | -------------------------------------------------------------------------------- /guides.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: EIGENROUTER - Guides 3 | description: 4 | published: true 5 | date: 2023-04-16T18:56:48.798Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T16:57:26.329Z 9 | --- 10 | 11 | # EIGENROUTER: Guides 12 | Your content here -------------------------------------------------------------------------------- /guides/draytek.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Router - DrayTek 3 | description: Information about Draytek 4 | published: true 5 | date: 2024-06-02T13:03:02.518Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-06-02T13:02:31.030Z 9 | --- 10 | 11 | # Router - DrayTek - draytek.nl 12 | 13 | DrayTek is a network equipment manufacturer of broadband CPE (Customer Premises Equipment), including firewalls, VPN devices, routers, managed switches and wireless LAN devices. The company was founded in 1997. The earliest products included ISDN based solutions, the first being the ISDN Vigor128, a USB terminal adaptor for Windows and Mac OS. This was followed by the ISDN Vigor204 ISDN terminal adaptor/PBX and the Vigor2000, its first router. The head office is located in Hsinchu, Taiwan with regional offices and distributors worldwide. 14 | 15 | DrayTek's products cover a wide solution range such as firewall, VPN, VoIP, xDSL/broadband devices, and management software to meet the market trend, go above and beyond customers' expectations. 16 | 17 | DrayTek was one of the first manufacturers to bring VPN technology to low cost routers, increasing the viability of remote work. In 2004, DrayTek released the first of its VoIP (Voice-Over-IP) products. In 2006, new products for companies debuted, including larger scale firewalls and Unified Threat Management (UTM) firewalls products however the UTM Firewalls did not sell in sufficient volume and the UTM products ceased development and production. 18 | 19 | DrayTek's product line offers business and consumer DSL modems with support for the PPPoA standard compared to the more widely supported PPPoE for use with full-featured home routers and home computers without more expensive ATM hardware. PPPoA is used primarily in the UK for ADSL lines. Most Vigor routers provide a virtual private network (VPN) feature, provides LAN-to-LAN and Remote-Dial-In Connections. In 2011, DrayTek embedded SSL VPN facilities into VigorRouter Series. 20 | 21 | ![draytek.png](/images/site/draytek.png) -------------------------------------------------------------------------------- /guides/draytek/kpn.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - KPN 3 | description: 4 | published: true 5 | date: 2024-06-02T12:56:58.462Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-06-02T12:56:58.462Z 9 | --- 10 | 11 | # Provider: KPN - kpn.com 12 | 13 | KPN is a leading telecommunications and IT provider and market leader in the Netherlands. With our fixed and mobile networks for telephony, data and television, we serve customers at home and abroad. KPN targets both private customers and business users, from small to large. 14 | 15 | ![kpn.jpg](/images/site/kpn.jpg) -------------------------------------------------------------------------------- /guides/draytek/kpn/kpn-internet.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Draytek KPN Internet 3 | description: 4 | published: true 5 | date: 2023-11-30T09:16:49.837Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-11-29T20:48:18.547Z 9 | --- 10 | 11 | # Draytek KPN Internet Only 12 | Type verbinding(en): ADSL, VDSL & Fiber 13 | 14 | ADSL instellingen 15 | Navigeer in het menu van de DrayTek naar “WAN >> General Setup >> WAN 1”. 16 | Zet de VLAN Tag insertion onder het kopje “Customer” op Enable om 17 | vervolgens Tag value 6 op te geven. De Priority kan op 0 blijven staan. 18 | **Particulier ADSL: 19 | PPPoA 20 | VPI: 8 21 | VCI: 48** 22 | **Zakelijk ADSL: 23 | PPPoA 24 | VPI: 2 25 | VCI: 32** 26 | 27 | ![image.png](/images/kpn/draytek/image.png) 28 | 29 | **VDSL instellingen 30 | PPPoE – VLAN tag 6** 31 | Username/password (dit kunt u zelf kiezen, maar dient wel ingevuld te worden) 32 | Dynamic IP 33 | Navigeer in het menu van de DrayTek naar “WAN >> General Setup >> WAN 1”. 34 | Zet de VLAN Tag insertion onder het kopje “Customer” op Enable om 35 | vervolgens Tag value 6 op te geven. De Priority kan op 0 blijven staan. 36 | 37 | ![vdsl1.png](/images/kpn/draytek/vdsl1.png) 38 | 39 | Klik op OK om de instellingen op te slaan. Bij **WAN >> Internet Access** 40 | configureert u de WAN poort als PPPoE. 41 | 42 | ![vdsl2.png](/images/kpn/draytek/vdsl2.png) 43 | 44 | **Fiber instellingen** 45 | **PPPoE – VLAN tag 6** 46 | Username/password (dit kunt u zelf kiezen, maar dient wel ingevuld te worden) 47 | Dynamic IP 48 | 49 | Navigeer in het menu van de DrayTek naar **“WAN >> General Setup >> WAN 1”**. 50 | Zet de VLAN Tag insertion onder het kopje **“Customer”** op Enable om 51 | vervolgens Tag value 6 op te geven. De Priority kan op 0 blijven staan. 52 | 53 | ![fiber1.png](/images/kpn/draytek/fiber1.png) 54 | 55 | Klik op OK om de instellingen op te slaan. Bij **WAN >> Internet Access** 56 | configureert u de WAN poort als PPPoE. 57 | 58 | ![fiber2.png](/images/kpn/draytek/fiber2.png) 59 | 60 | Klik op OK om de instellingen op te slaan. Na deze aanpassing zal internettoegang 61 | op de DrayTek mogelijk moeten zijn. 62 | -------------------------------------------------------------------------------- /guides/draytek/kpn/routed-iptv.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Routed-iptv 3 | description: 4 | published: true 5 | date: 2023-12-01T21:07:18.109Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-12-01T21:07:18.109Z 9 | --- 10 | 11 | # Routed-iptv KPN 12 | 13 | **De volgende modellen zijn geschikt voor routed iptv** 14 | 15 | ![routediptvondersteuning.png](/images/kpn/draytek/routediptvondersteuning.png) 16 | 17 | Zorg er voor dat je Draytek de nieuwste firmware heeft. 18 | Deze kun je [hier downloaden](https://www.draytek.nl/firmware/) 19 | ### **Routed iptv config** 20 | **Belangrijke instellingen:** 21 | - VLAN Tag:4 voor IPTV (Virtual WAN). 22 | - WAN DHCP Option 60:IPTV_RG voor het verkrijgen van een IP-adres aan de WAN 23 | kant. Als dit niet wordt geconfigureerd, kan er **GEEN IP-adres** 24 | worden verkregen. 25 | - IGMP Proxy/Snooping:Inschakelen. 26 | - Hardware Acceleration:Manual voor UDP sessies. 27 | 28 | Navigeer in de webinterface van de DrayTek naar WAN >> Multi-VLAN om een vrije WAN 29 | Channel te selecteren. In dit voorbeeld maken we gebruik van WAN5. Deze dient u in te 30 | schakelen om vervolgens het volgende in te stellen: 31 | 32 | WAN Type: 33 | Deze dient u op ADSL, VDSL of Ethernet (WAN1 of 34 | WAN2) te zetten. (afhankelijk van welke WAN poort er 35 | gebruikt wordt). 36 | VLAN Tag: 37 | Geef hier het VLAN Tag voor IPTV op, bij KPN is 38 | dit VLAN Tag 4. 39 | Open WAN Interface : 40 | Zet deze op Enable en vink IPTV aan, zet de WAN Setup 41 | vervolgens op Static or Dynamic IP. 42 | WAN IP Network Settings: 43 | Vink hier Obtain an IP Address Automatically aan. 44 | 45 | ![routed1.png](/images/kpn/draytek/routed1.png) 46 | 47 | Om een IP-adres te verkrijgen op WAN 5 (Virtual WAN) dient u Option 60 IPTV_RG in te 48 | stellen. Wanneer dit niet is ingesteld, krijgt u ook geen IP-adres op de WAN verbinding. 49 | Navigeer naar WAN >> Internet Access en klik op de knop DHCP Client Option. 50 | 51 | ![routed2.png](/images/kpn/draytek/routed2.png) 52 | 53 | Zet hier een vinkje bij Enable en vul hier het volgende in: 54 | Interface:WAN5 (afhankelijk van de virtuele WAN die gebruikt wordt op pagina 5) 55 | Option:60 56 | DataType:ASCII Character 57 | Data:IPTV_RG 58 | 59 | ![routed3.png](/images/kpn/draytek/routed3.png) 60 | Klik op Add om de betreffende regel toe te voegen aan de DHCP Option lijst. 61 | 62 | Wanneer u op Add hebt geklikt krijgt u de onderstaande regel in de Options List te zien: 63 | ![routed4.png](/images/kpn/draytek/routed4.png) 64 | 65 | Klik op OK om de instellingen op te slaan. 66 | Controleer bij “Online Status >> Virtual WAN” of er een IP adres op de WAN5 interface 67 | wordt verkregen. In het onderstaande voorbeeld kunt u zien dat de WAN5 interface online 68 | is, waarbij een IP adres wordt verkregen van 10.0.0.68 (dit kan ook een ander IP adres zijn). 69 | 70 | ![routed5.png](/images/kpn/draytek/routed5.png) 71 | De WAN5 configuratie is afgerond, vervolgens dient u de onderstaande stappen te volgen 72 | voor het configureren van IGMP Proxy en Snooping. 73 | 74 | ### **IGMP Proxy & IGMP Snooping** 75 | 76 | Om de IPTV pakketten beter te begeleiden dient IGMP Proxy en IGMP Snooping te worden 77 | ingeschakeld. Navigeer in het menu naar Application >> IGMP, schakel zowel IGMP Proxy, 78 | IGMP Snooping als IGMP Fast Leave in. Selecteer bij Interface PVC/VLAN en zorg ervoor 79 | dat de IGMP version op Auto staat. 80 | 81 | ***Let op: Wanneer u meerdere IPTV ontvangers op één enkele LAN poort gebruikt 82 | (bijvoorbeeld door middel van een switch), dient u de optie IGMP Fast Leave uit te 83 | schakelen!*** 84 | 85 | ![igmp1.png](/images/kpn/draytek/igmp1.png) 86 | Klik op OK om de instellingen op te slaan. 87 | 88 | **Hardware Acceleration** 89 | 90 | De Hardware Acceleration moet ingesteld worden (m.u.v. V3910/V2962 serie), zodat 91 | Multicast verkeer door de DrayTek modem/router versneld wordt. Dit heeft als voordeel 92 | dat de processor van de router niet extra belast wordt. 93 | 94 | Navigeer in het hoofdmenu naar Hardware Acceleration. Zet hierbij de Mode op **Enable** 95 | en het NAT Protocol op **UDP**. 96 | 97 | **Opmerking:** Wanneer u een internet abonnement heeft met een snelheid van meer dan 98 | 300Mbps dient u ook het vinkje voor TCP in te schakelen om de maximale snelheden te kunnen 99 | behalen. 100 | 101 | ![igmp2.png](/images/kpn/draytek/igmp2.png) 102 | 103 | De aanwezige IPTV decoder(s) kunt u nu aansluiten op uw DrayTek modem/router. Op 104 | basis van de bovenstaande instellingen zal de IPTV decoder(s) online moeten komen. 105 | 106 | **Software en updates TV decoder** 107 | 108 | Na het opstarten van de TV decoder zal de decoder een software/update proberen te 109 | downloaden vanaf het IPTV platform. Om deze software/updates binnen te kunnen halen, 110 | dient u in de DrayTek te navigeren naar “Applications >> IGMP >> Working status” en 111 | zet u een vinkje bij Unblock achter de betreffende weergegeven IP range. 112 | Klik vervolgens op OK. 113 | 114 | ![igmp3.png](/images/kpn/draytek/igmp3.png) 115 | 116 | **Het kan zijn dat de TV decoder hierna nog één keer opnieuw moet worden opgestart.** 117 | 118 | **Waarom heeft mijn TV stream hakkelig of vastlopend beeld?** 119 | 120 | - Controleer of DoS Defense onder “Firewall >> Defense Setup” uit staat. Wanneer de 121 | functie Enable UDP flood defense aan staat gevinkt, kan dit problemen opleveren met 122 | IPTV. 123 | - Controleer of de Data Flow Monitor uit staat onder “Diagnostics >> Data Flow Monitor”. 124 | Wanneer deze functie aanstaat, zal de Hardware Acceleration (die nodig is om IPTV 125 | pakketjes versneld door te sturen) niet actief worden. 126 | 127 | -------------------------------------------------------------------------------- /guides/draytek/online.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - Online 3 | description: 4 | published: true 5 | date: 2024-06-02T12:57:58.488Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-06-02T12:57:58.488Z 9 | --- 10 | 11 | # Provider: Online - online.nl 12 | 13 | It's a nice idea when your provider has the knowledge and experience to let you enjoy everything the internet has to offer without worry. Online.nl is one of the first providers in the Netherlands. We have been around since 1994, back then under the name Euronet. Together with other pioneers, we connected the Netherlands to the web and we were even the very first provider to sell internet access in shops. 14 | 15 | Our 1994 installation manual stated: 'The internet is expected to develop into the communication tool of the future.' Now, almost 30 years later, we work, learn, play and create online. We shop, talk and meet online. We watch our TV series and movies online. The internet has become not just the means of communication, but a necessity of life. For everyone, from young to old. 16 | 17 | We have been providing reliable and affordable internet services since 1994 and our professional staff are ready to help you. With us, you get it all as standard: with fibre-optic internet, low-cost call rates and interactive TV from Canal Digitaal. With more than 80 TV channels, CANAL+ Films & Series and Film1 as standard in your TV package. We offer 100% installation guarantee, free switching service, a free WiFi modem and much more. With no hidden costs and no worries. 18 | 19 | We have never lost our pioneering spirit. Thus, together with our partner Canal Digitaal, we are still at the forefront of the interactive television revolution and we believe that fast internet and affordable calling should be available to everyone. We work with the latest technology, such as fibre optics, and we challenge the market by offering just a bit more for the same money. 20 | 21 | We can no longer imagine a world without internet. Yet this is only the beginning. As in 1994, we dare to predict that it will become much bigger than it already is. That everything will be connected to everything. From our cities, roads, houses and cars to our refrigerators, doorbells and clothes. We work online, we learn online and even for our health we increasingly rely on the internet. In short: the future is online, just like us. 22 | 23 | ![online.png](/images/site/online.png) -------------------------------------------------------------------------------- /guides/draytek/online/online-internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Online Internet Only 3 | description: 4 | published: true 5 | date: 2023-12-02T18:07:32.070Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-12-02T18:07:32.070Z 9 | --- 10 | 11 | # ONLINE Internet Only 12 | 13 | **Type verbinding: ADSL &VDSL** 14 | 15 | **ADSL instellingen** 16 | VPI: 8 17 | VCI: 35 18 | DHCP / MPoA 19 | 20 | Bij WAN >> Internet Access kunt u de WAN poort configureren als MPoA / Static 21 | or Dynamic IP. Belangrijk is hierbij het aanvinken van ‘Enable’ en ‘Obtain an IP 22 | address automatically’. Geef daarnaast de juiste VPI en VCI waardes. 23 | 24 | ![online1.png](/images/online/draytek-internet-only/online1.png) 25 | 26 | **VDSL instellingen** 27 | DHCP – VLAN tag 100 28 | 29 | Navigeer in het menu van de DrayTek naar “WAN >> General Setup >> WAN 1”. 30 | Zet de VLAN Tag insertion onder het kopje “Customer” op Enable om 31 | vervolgens Tag value 1001 op te geven. De Priority kan op 0 blijven staan. 32 | 33 | ![online2.png](/images/online/draytek-internet-only/online2.png) 34 | 35 | Bij WAN >> Internet Access kunt u de WAN poort verder configureren als DHCP 36 | client. Belangrijk is hierbij het aanvinken van ‘Enable’ en ‘Obtain an IP address 37 | automatically’. 38 | 39 | ![online3.png](/images/online/draytek-internet-only/online3.png) 40 | 41 | Je verbinding zou nu moeten werken! 42 | 43 | **Weet jij de instellingen voor Fiber? Laat het ons weten ;)** -------------------------------------------------------------------------------- /guides/draytek/solcon.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - Solcon 3 | description: 4 | published: true 5 | date: 2024-06-02T12:56:34.730Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-06-02T12:56:34.730Z 9 | --- 10 | 11 | # Provider: Solcon 12 | 13 | Solcon's ambition is to make more secure and manageable internet available to everyone in the Netherlands. Founded in 1996, provider Solcon focuses on consumer and small business SME customer groups. 14 | 15 | Solcon believes that everyone should be able to enjoy the advantages of this digital world to the fullest and face as few disadvantages as possible. Solcon does this by providing customers with practical innovative tools and knowledge. In this way, customers can benefit from digital media in the most responsible and personal way possible. 16 | 17 | Solcon offers a wide range of services, fully ISO27001-certified (consumer and business): from quad play (internet, television, telephony and mobile) to hosting. At Solcon, customers will find the most advanced filters and secure data storage. It also protects customers against internet crime such as malware, phishing and ransomware. 18 | 19 | Nationwide, Solcon uses KPN's quality network. In fibre-optic outlying areas, Solcon operates different networks. In doing so, it deploys the latest technologies, such as GPON technology. 20 | 21 | Solcon believes in the power of real contact. The customer care staff like to take the time for customers. No time pressure and interview protocols. And... Solcon is only satisfied when customers are. It wants to give customers the attention and service they deserve. 22 | 23 | ![solcon.png](/images/site/solcon.png) -------------------------------------------------------------------------------- /guides/draytek/solcon/solcon-internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: SOLCON Internet Only 3 | description: 4 | published: true 5 | date: 2023-12-02T18:21:26.941Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-12-02T18:21:26.941Z 9 | --- 10 | 11 | # SOLCON Internet Only 12 | 13 | **Solcon 14 | Type verbinding: ADSL, VDSL & Fiber** 15 | 16 | ADSL instellingen 17 | VPI: 0 18 | VCI: 36 19 | PPPoA met PPP credentials (gebruikersnaam / wachtwoord) 20 | 21 | *Gebruikersnaam en wachtwoord zijn bekend bij je provider* 22 | 23 | Navigeer in het menu van de DrayTek router naar WAN >> Internet Access om 24 | hier de WAN poort als PPPoE / PPPoA te configureren. 25 | 26 | ![solcon1.png](/images/solcon/solcon1.png) 27 | 28 | **VDSL instellingen** 29 | PPPoE – VLAN tag 6 30 | Gebruikersnaam / wachtwoord *(bekend bij provider)* 31 | Dynamic IP 32 | 33 | Navigeer in het menu van de DrayTek naar “WAN >> General Setup >> WAN 1”. 34 | Zet de VLAN Tag insertion onder het kopje “Customer” op Enable om 35 | vervolgens Tag value 6 op te geven. De Priority kan op 0 blijven staan. 36 | 37 | ![solcon2.png](/images/solcon/solcon2.png) 38 | 39 | Klik op OK om de instellingen op te slaan. Bij WAN >> Internet Access 40 | configureert u de WAN poort als PPPoE. 41 | 42 | ![solcon3.png](/images/solcon/solcon3.png) 43 | 44 | 45 | **Fiber instellingen** 46 | DHCP – Untagged 47 | Dynamic IP 48 | 49 | Bij WAN >> Internet Access kunt u de WAN poort configureren als DHCP client. 50 | Belangrijk is hierbij het aanvinken van ‘Enable’ en ‘Obtain an IP address 51 | automatically’. 52 | 53 | ![solcon4.png](/images/solcon/solcon4.png) 54 | 55 | -------------------------------------------------------------------------------- /guides/draytek/t-mobile.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - T-Mobile 3 | description: 4 | published: true 5 | date: 2024-06-02T12:57:31.142Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-06-02T12:57:31.142Z 9 | --- 10 | 11 | # Provider: T-Mobile 12 | T-Mobile is the brand name used by some of the mobile communications subsidiaries of the German telecommunications company Deutsche Telekom AG in the Czech Republic (T-Mobile Czech Republic), Poland (T-Mobile Polska), the United States (T-Mobile US) and by the former subsidiary in the Netherlands (T-Mobile Netherlands). 13 | 14 | The T-Mobile brand was introduced in 1996 and the name was previously used by subsidiaries in other countries, including Austria (now Magenta), Croatia (now Hrvatski Telekom), Germany (now Deutsche Telekom), Hungary (now Magyar Telekom), Montenegro (now Crnogorski Telekom), North Macedonia (now Makedonski Telekom), Romania (now Telekom România), Slovakia (now Slovak Telekom), and the United Kingdom (now EE Limited). 15 | 16 | In 1999, Deutsche Telekom formed the holding company T-Mobile International AG for its mobile communications subsidiaries. From 2003 to 2007, T-Mobile International was one of Deutsche Telekom's services, in addition to "Broadband/Fixnet", "Business Customers" and "Group HQ and Shared Services". In 2009, Deutsche Telekom transformed its structure to adopt a regional setup (Germany, Europe, US). By combining its previously separated fixed and mobile subsidiaries to form integrated local businesses, T-Mobile International itself was merged into Deutsche Telekom AG. 17 | 18 | When T-Mobile International AG existed, the holding company was based in Bonn, Germany, and its subsidiaries operated GSM-, UMTS- and LTE-based cellular networks in Europe, the United States, Puerto Rico and the U.S. Virgin Islands. The company had financial stakes in mobile operators in both Central and Eastern Europe. Globally, T-Mobile International's subsidiaries had a combined total of approximately 230 million subscribers. It was the world's thirteenth-largest mobile-phone service provider by subscribers, and the fourth-largest multinational after the UK's Vodafone, India's Airtel, and Spain's Telefónica. 19 | 20 | ## History 21 | 22 | On 1 July 1989, West Germany reorganized Deutsche Bundespost and consolidated telecommunications into a new unit, Deutsche Bundespost Telekom. On 1 July 1992, it began to operate Germany's first GSM network, along with the C-Netz, as its DeTeMobil subsidiary. The GSM 900 MHz frequency band was referred to as the "D-Netz", and Telekom named its service D1; the private consortium awarded the second license (now Vodafone Germany) chose the name D2. Deutsche Bundespost Telekom was renamed Deutsche Telekom AG on 1 January 1995 as part of phase two of the German communications reform. This process of deregulation continued in November 1996, when DT was privatized and had the largest European IPO at the time, with the stock abbreviation 'DT 1'. 23 | 24 | In December 1999, T-Mobile International AG & Co. KG holding company was founded (later renamed T-Mobile International AG). In 2002, as DT consolidated its international operations, it anglicized the T-Mobil name to T-Mobile. 25 | 26 | On 5 July 2005 Deutsche Telekom transformed its structure and adopted a regional setup (Germany, Europe, US). Where available, the local mobile businesses were combined with the respective local wireline businesses to follow the integrated business approach. In 2009 T-Mobile International AG was merged into Deutsche Telekom AG. 27 | 28 | On 16 August 2021, T-Mobile announced that a hacker had illegally accessed more than 76 million Americans’ private data, with an American hacker named John Binns later claiming responsibility. Several class action lawsuits have been filed in relation to the data breach. In July 2022, T-mobile agreed to a $350 million settlement during the company's hearing at Missouri federal court, in relation to the data breech and subsequent class action litigation. The $350 million settlement will include $25,000 in reimbursement for the losses to organisations, compensation to the victims of the data breech of $25 per hour and to provide two-year subscriptions to identity theft services and $150 million on improving data security. 29 | 30 | On 19 January 2023, T-Mobile said it first identified a bad actor had obtained the data of 37 million customers via an unauthorized API (starting on or around 25 November 2022). The data included the name, billing address, email, phone number, date of birth, T-Mobile account number, and information such as the number of lines on the account and plan features. 31 | ![t-mobile.png](/images/site/t-mobile.png) -------------------------------------------------------------------------------- /guides/draytek/t-mobile/tmobile-internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: T-mobile Internet Only 3 | description: 4 | published: true 5 | date: 2023-12-02T18:27:58.980Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-12-02T18:27:58.980Z 9 | --- 10 | 11 | # T-Mobile Internet Only 12 | 13 | **T-Mobile 14 | Type verbinding(en): VDSL & Fiber** 15 | 16 | VDSL & Fiber instellingen 17 | DHCP – VLAN tag 300 18 | 19 | Navigeer in het menu van de DrayTek naar “WAN >> General Setup >> WAN 1”. 20 | Zet de VLAN Tag insertion onder het kopje “Customer” op Enable om 21 | vervolgens Tag value 300 op te geven. De Priority kan op 0 blijven staan. 22 | 23 | ![tmobile1.png](/images/tmobile/tmobile1.png) 24 | 25 | Bij WAN Internet Access kunt u de WAN poort verder configureren als DHCP 26 | client. Belangrijk is hierbij het aanvinken van ‘Enable’ en ‘Obtain an IP address 27 | automatically’. 28 | 29 | ![tmobile2.png](/images/tmobile/tmobile2.png) 30 | 31 | Klik op OK om de instellingen op te slaan. Na deze aanpassing zal internettoegang 32 | op de DrayTek mogelijk moeten zijn. 33 | 34 | -------------------------------------------------------------------------------- /guides/mikrotik.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Router - Mikrotik 3 | description: Information about Mikrotik 4 | published: true 5 | date: 2023-04-16T19:09:19.405Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:49:55.768Z 9 | --- 10 | 11 | # Router - Mikrotik - mikrotik.com 12 | 13 | MikroTik (officially SIA "Mikrotīkls") is a Latvian network equipment manufacturer. The company develops and sells wired and wireless network routers, network switches, access points, as well as operating systems and auxiliary software. The company was founded in 1996, and as of August 2019, the company website reported an estimated 280 employees. In 2021, with a value of EUR 1.24B, Mikrotik was the 3rd largest company in Latvia and the first private company to surpass EUR 1B value in Latvia. 14 | 15 | ## History 16 | MikroTik was founded in 1996 by John Tully and Arnis Riekstiņš in Riga, Latvia, developing networking software for x86 PC hardware that would develop into a product called RouterOS. The earliest versions of RouterOS were based on Linux 2.2. In 2002, MikroTik began producing their own networking-focused low-power single-board computers, branded RouterBoard, that ran RouterOS. These early SBCs could be expanded and/or used as components of other systems, but as time passed, this RouterBoard/RouterOS platform would develop into a full line network equipment. 17 | 18 | ![mikrotik.png](/images/site/mikrotik.png) -------------------------------------------------------------------------------- /guides/mikrotik/code-snippets.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Router - Mikroti 3 | description: Information about Mikrotik 4 | published: true 5 | date: 2024-06-02T12:47:49.129Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-06-02T12:47:49.129Z 9 | --- 10 | 11 | # Router - Mikrotik - mikrotik.com 12 | 13 | MikroTik (officially SIA "Mikrotīkls") is a Latvian network equipment manufacturer. The company develops and sells wired and wireless network routers, network switches, access points, as well as operating systems and auxiliary software. The company was founded in 1996, and as of August 2019, the company website reported an estimated 280 employees. In 2021, with a value of EUR 1.24B, Mikrotik was the 3rd largest company in Latvia and the first private company to surpass EUR 1B value in Latvia. 14 | 15 | ## History 16 | MikroTik was founded in 1996 by John Tully and Arnis Riekstiņš in Riga, Latvia, developing networking software for x86 PC hardware that would develop into a product called RouterOS. The earliest versions of RouterOS were based on Linux 2.2. In 2002, MikroTik began producing their own networking-focused low-power single-board computers, branded RouterBoard, that ran RouterOS. These early SBCs could be expanded and/or used as components of other systems, but as time passed, this RouterBoard/RouterOS platform would develop into a full line network equipment. 17 | 18 | ![mikrotik.png](/images/site/mikrotik.png) -------------------------------------------------------------------------------- /guides/mikrotik/code-snippets/block-port-scanners.md: -------------------------------------------------------------------------------- 1 | Code snippet for detection and blocking of port scanning software: 2 | 3 | ``` 4 | /ip firewall filter 5 | add chain=input protocol=tcp psd=21,3s,3,1 action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w comment="Port scanners to list " disabled=no 6 | add chain=input protocol=tcp tcp-flags=fin,!syn,!rst,!psh,!ack,!urg action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w comment="NMAP FIN Stealth scan" 7 | add chain=input protocol=tcp tcp-flags=fin,syn action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w comment="SYN/FIN scan" 8 | add chain=input protocol=tcp tcp-flags=syn,rst action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w comment="SYN/RST scan" 9 | add chain=input protocol=tcp tcp-flags=fin,psh,urg,!syn,!rst,!ack action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w comment="FIN/PSH/URG scan" 10 | add chain=input protocol=tcp tcp-flags=fin,syn,rst,psh,ack,urg action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w comment="ALL/ALL scan" 11 | add chain=input protocol=tcp tcp-flags=!fin,!syn,!rst,!psh,!ack,!urg action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w comment="NMAP NULL scan" 12 | /ip firewall raw 13 | add chain=prerouting src-address-list="port scanners" action=drop comment="dropping port scanners" disabled=no 14 | ``` 15 | -------------------------------------------------------------------------------- /guides/mikrotik/code-snippets/default-firewall-ipv6.md: -------------------------------------------------------------------------------- 1 | Code snippet default firewall ipv6 2 | ``` 3 | /ipv6 firewall { 4 | address-list add list=bad_ipv6 address=::/128 comment="defconf: unspecified address" 5 | address-list add list=bad_ipv6 address=::1 comment="defconf: lo" 6 | address-list add list=bad_ipv6 address=fec0::/10 comment="defconf: site-local" 7 | address-list add list=bad_ipv6 address=::ffff:0:0/96 comment="defconf: ipv4-mapped" 8 | address-list add list=bad_ipv6 address=::/96 comment="defconf: ipv4 compat" 9 | address-list add list=bad_ipv6 address=100::/64 comment="defconf: discard only " 10 | address-list add list=bad_ipv6 address=2001:db8::/32 comment="defconf: documentation" 11 | address-list add list=bad_ipv6 address=2001:10::/28 comment="defconf: ORCHID" 12 | address-list add list=bad_ipv6 address=3ffe::/16 comment="defconf: 6bone" 13 | address-list add list=bad_ipv6 address=::224.0.0.0/100 comment="defconf: other" 14 | address-list add list=bad_ipv6 address=::127.0.0.0/104 comment="defconf: other" 15 | address-list add list=bad_ipv6 address=::/104 comment="defconf: other" 16 | address-list add list=bad_ipv6 address=::255.0.0.0/104 comment="defconf: other" 17 | filter add chain=input action=accept connection-state=established,related,untracked comment="defconf: accept established,related,untracked" 18 | filter add chain=input action=drop connection-state=invalid comment="defconf: drop invalid" 19 | filter add chain=input action=accept protocol=icmpv6 comment="defconf: accept ICMPv6" 20 | filter add chain=input action=accept protocol=udp port=33434-33534 comment="defconf: accept UDP traceroute" 21 | filter add chain=input action=accept protocol=udp dst-port=546 src-address=fe80::/10 comment="defconf: accept DHCPv6-Client prefix delegation." 22 | filter add chain=input action=accept protocol=udp dst-port=500,4500 comment="defconf: accept IKE" 23 | filter add chain=input action=accept protocol=ipsec-ah comment="defconf: accept ipsec AH" 24 | filter add chain=input action=accept protocol=ipsec-esp comment="defconf: accept ipsec ESP" 25 | filter add chain=input action=accept ipsec-policy=in,ipsec comment="defconf: accept all that matches ipsec policy" 26 | filter add chain=input action=drop in-interface-list=!LAN comment="defconf: drop everything else not coming from LAN" 27 | filter add chain=forward action=accept connection-state=established,related,untracked comment="defconf: accept established,related,untracked" 28 | filter add chain=forward action=drop connection-state=invalid comment="defconf: drop invalid" 29 | filter add chain=forward action=drop src-address-list=bad_ipv6 comment="defconf: drop packets with bad src ipv6" 30 | filter add chain=forward action=drop dst-address-list=bad_ipv6 comment="defconf: drop packets with bad dst ipv6" 31 | filter add chain=forward action=drop protocol=icmpv6 hop-limit=equal:1 comment="defconf: rfc4890 drop hop-limit=1" 32 | filter add chain=forward action=accept protocol=icmpv6 comment="defconf: accept ICMPv6" 33 | filter add chain=forward action=accept protocol=139 comment="defconf: accept HIP" 34 | filter add chain=forward action=accept protocol=udp dst-port=500,4500 comment="defconf: accept IKE" 35 | filter add chain=forward action=accept protocol=ipsec-ah comment="defconf: accept ipsec AH" 36 | filter add chain=forward action=accept protocol=ipsec-esp comment="defconf: accept ipsec ESP" 37 | filter add chain=forward action=accept ipsec-policy=in,ipsec comment="defconf: accept all that matches ipsec policy" 38 | filter add chain=forward action=drop in-interface-list=!LAN comment="defconf: drop everything else not coming from LAN" 39 | } 40 | ``` 41 | -------------------------------------------------------------------------------- /guides/mikrotik/code-snippets/default-firewall.md: -------------------------------------------------------------------------------- 1 | Code snippet default firewall 2 | ``` 3 | /ip firewall filter 4 | add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp 5 | add action=accept chain=input comment="defconf: accept established,related" \ 6 | connection-state=established,related 7 | add action=drop chain=input comment="defconf: drop all from WAN" \ 8 | in-interface=ether1 9 | add action=fasttrack-connection chain=forward comment="defconf: fasttrack" \ 10 | connection-state=established,related 11 | add action=accept chain=forward comment="defconf: accept established,related" \ 12 | connection-state=established,related 13 | add action=drop chain=forward comment="defconf: drop invalid" \ 14 | connection-state=invalid 15 | add action=drop chain=forward comment=\ 16 | "defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat \ 17 | connection-state=new in-interface=ether1 18 | /ip firewall nat 19 | add action=masquerade chain=srcnat comment="defconf: masquerade" \ 20 | out-interface=ether1 21 | ``` 22 | -------------------------------------------------------------------------------- /guides/mikrotik/code-snippets/fasttrack.md: -------------------------------------------------------------------------------- 1 | Code snippet to enable fasttrack: 2 | 3 | ``` 4 | /ip firewall filter add chain=forward action=fasttrack-connection connection-state=established,related 5 | /ip firewall filter add chain=forward action=accept connection-state=established,related 6 | ``` 7 | -------------------------------------------------------------------------------- /guides/mikrotik/code-snippets/set-ntp.md: -------------------------------------------------------------------------------- 1 | Code snippet to set NTP: 2 | 3 | ``` 4 | /system clock 5 | set time-zone-name=Europe/Amsterdam 6 | /system ntp client set enabled=yes servers=1.pool.ntp.org,2.pool.ntp.org 7 | ``` 8 | -------------------------------------------------------------------------------- /guides/mikrotik/code-snippets/v7-multi-wan.md: -------------------------------------------------------------------------------- 1 | Code snippet to make more than one internet connection individually usable (active-active): 2 | 3 | Create new routing tables: 4 | ``` 5 | /routing table 6 | add disabled=no fib name=ROS>WAN1 7 | add disabled=no fib name=ROS>WAN2 8 | ``` 9 | 10 | Add mangle rules that use the new routing tables: 11 | ``` 12 | /ip firewall mangle 13 | add action=mark-connection chain=input in-interface=sfp-sfpplus1 new-connection-mark=WAN1>ROS passthrough=yes 14 | add action=mark-connection chain=input in-interface=sfp-sfpplus2 new-connection-mark=WAN2>ROS passthrough=yes 15 | add action=mark-routing chain=output connection-mark=WAN1>ROS new-routing-mark=ROS>WAN1 passthrough=yes 16 | add action=mark-routing chain=output connection-mark=WAN2>ROS new-routing-mark=ROS>WAN2 passthrough=yes 17 | ``` 18 | 19 | Add routes for the new routing tables: 20 | ``` 21 | /ip route 22 | add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=sfp-sfpplus1 routing-table=ROS>WAN1 23 | add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=sfp-sfpplus2 routing-table=ROS>WAN2 24 | ``` 25 | 26 | Add more tables/rules/routes based on the counting mechanism above if needed. 27 | -------------------------------------------------------------------------------- /guides/mikrotik/delta.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - DELTA 3 | description: 4 | published: true 5 | date: 2024-06-02T12:54:29.829Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-06-02T12:52:52.522Z 9 | --- 10 | 11 | # Provider: DELTA - delta.nl 12 | 13 | DELTA Fiber is een Nederlandse telecomaanbieder voor consumenten en ondernemers. DELTA Fiber legt glasvezel aan voor snel internet, exploiteert het netwerk en levert via dit netwerk ook diensten aan, zoals interactieve televisie, telefonie en mobiele diensten. Het is een open netwerk, dat wil zeggen dat het open staat voor gebruik door andere aanbieders. Het bedrijf is na KPN Netwerk de grootste exploitant van glasvezelnetwerken in Nederland. Een andere concurrent is Open Dutch Fiber. 14 | 15 | Het bedrijf is actief onder de merknamen DELTA, DELTA Netwerk, DELTA Zakelijk (voorheen CBizz), DELTA Fiber Netwerk (voorheen Glasvezel buitenaf), ZeelandNet en Caiway. Het bedrijf is eigendom van het Zweedse investeringsfonds EQT en het Amerikaanse investeringsfonds Stonepeak. 16 | 17 | ![delta.png](/images/site/delta.png) -------------------------------------------------------------------------------- /guides/mikrotik/delta/Mikrotik-Internet-Only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik-Internet-Only 3 | description: How to Setup Delta Internet Only on Mikrotik 4 | published: true 5 | date: 2024-06-02T12:55:10.140Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2024-05-06T07:51:35.881Z 9 | --- 10 | 11 | # Mikrotik internet only 12 | 13 | This guide is based on a Mikrotik device with at least two Ethernet ports. We start with a completely empty configuration. To wipe your configuration, connect to your Mikrotik device via Winbox or Webfig (HTTP) and navigate to System > Reset Configuration. Tick “No Default Configuration” and reset the device via the “Reset Configuration” button. The device will now restart. 14 | 15 | After wiping the configuration, you can connect to the Mikrotik via MAC-Winbox on Windows or via Wine. We recommend configuring a management network on an Ethernet interface that you will not use for the network that we will create in this guide. The simplest way to do this is to set a unique IP address on for example ether3 (as ether3 will not be used in this guide) and to connect to the device via IP on ether3. Refer to the IP Address section in the steps below to see how to do this. 16 | 17 | You can download Winbox here: [ MikroTik Routers and Wireless - Software](https://mikrotik.com/download) 18 | 19 | The default login credentials are “admin” with no password. If you are running the latest version of Routeros 6 or 7, you will be prompted to change the password on first login. 20 | 21 | This guide will give you commands to enter in the Mikrotik Terminal. You can do this either via SSH or in the Terminal that is included in the Winbox application. 22 | 23 | 24 | We will build the WAN connection on ether1, and the LAN connection on ether2. Ether2 will be configured as slave interface of a bridge interface. 25 | If you intend to use an SFP(+) port, replace all 'ether1' values with the name of your SFP(+) interface, for example 'sfp-sfpplus1'. You will need to do this if you intend to use an SFP(+) module like the Zaram ZXOS11NPI. 26 | 27 | Add the following: 28 | ``` 29 | /interface vlan 30 | add interface=ether1 name=vlan1.100 vlan-id=100 31 | ``` 32 | Now we configure the DHCP client on VLAN 100 33 | ``` 34 | /ip dhcp-client 35 | add interface=vlan1.100 add-default-route=yes disabled=no use-peer-dns=no use-peer-ntp=no 36 | ``` 37 | We will now add the bridge interface for the LAN 38 | ``` 39 | /interface bridge 40 | add name=local arp=proxy-arp 41 | ``` 42 | Add the necessary ports to your bridge 43 | ``` 44 | /interface bridge port 45 | add bridge=local interface=ether2 46 | ``` 47 | Set the gateway address for the LAN. You can change this to your needs. 48 | ``` 49 | /ip address 50 | add address=10.0.0.1/24 interface=local 51 | ``` 52 | Set DNS forwarders. In this example we will be using Google DNS. We will also use the Mikrotik as DNS server for the LAN. 53 | ``` 54 | /ip dns 55 | set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4 56 | ``` 57 | Configure a basic firewall. For proper hardening, refer to this Mikrotik article: [Building Advanced Firewall](https://help.mikrotik.com/docs/display/ROS/Building+Advanced+Firewall). The following filter rules only cover the input chain on the WAN-VLAN interface. This means the LAN side is not hardened. 58 | ``` 59 | /ip firewall filter 60 | add action=accept chain=input in-interface=vlan1.100 protocol=icmp 61 | add action=accept chain=input connection-state=established,related 62 | add action=drop chain=input in-interface=vlan1.100 63 | ``` 64 | Configure outbound NAT 65 | ``` 66 | /ip firewall nat 67 | add action=masquerade chain=srcnat out-interface=vlan1.100 68 | ``` 69 | Configure a DHCP server for the LAN. If you changed anything in the IP Address section above, also change the values here to match. 70 | ``` 71 | /ip pool 72 | add name=thuisnetwerk ranges=10.0.0.10-10.0.0.254 73 | /ip dhcp-server 74 | add address-pool=thuisnetwerk authoritative=yes interface=local \ 75 | lease-time=8h name=dhcp-home 76 | /ip dhcp-server network 77 | add address=10.0.0.0/24 dns-server=10.0.0.1 domain=home.local gateway=\ 78 | 10.0.0.1 79 | ``` 80 | Now, if you connect your device to ether2, you should get an IP address via DHCP in the 10.0.0.0/24 range, and you will have internet access. We recommend updating the Mikrotik device to the latest Stable version of Routeros 6 or 7. You can do this at System > Packages > Check for Updates. Also update the firmware at System > RouterBOARD > Upgrade. Both updates require a restart. 81 | -------------------------------------------------------------------------------- /guides/mikrotik/kpn.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - KPN 3 | description: 4 | published: true 5 | date: 2023-04-16T18:55:59.655Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:50:47.659Z 9 | --- 10 | 11 | # Provider: KPN - kpn.com 12 | 13 | KPN is a leading telecommunications and IT provider and market leader in the Netherlands. With our fixed and mobile networks for telephony, data and television, we serve customers at home and abroad. KPN targets both private customers and business users, from small to large. 14 | 15 | ![kpn.jpg](/images/site/kpn.jpg) -------------------------------------------------------------------------------- /guides/mikrotik/kpn/Mikrotik-Internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik Internet Only 3 | description: How to Setup KPN Internet Only on Mikrotik 4 | published: true 5 | date: 2023-04-23T15:54:22.743Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:27:19.359Z 9 | --- 10 | 11 | # Mikrotik internet only 12 | 13 | This guide is based on a Mikrotik device with at least two Ethernet ports. We start with a completely empty configuration. To wipe your configuration, connect to your Mikrotik device via Winbox or Webfig (HTTP) and navigate to System > Reset Configuration. Tick “No Default Configuration” and reset the device via the “Reset Configuration” button. The device will now restart. 14 | 15 | After wiping the configuration, you can connect to the Mikrotik via MAC-Winbox on Windows or via Wine. We recommend configuring a management network on an Ethernet interface that you will not use for the network that we will create in this guide. The simplest way to do this is to set a unique IP address on for example ether3 (as ether3 will not be used in this guide) and to connect to the device via IP on ether3. Refer to the IP Address section in the steps below to see how to do this. 16 | 17 | You can download Winbox here: [ MikroTik Routers and Wireless - Software](https://mikrotik.com/download) 18 | 19 | This guide requires that you install the ‘multicast’ package for Routeros version 6. If you’re running Routeros 7, skip this step. 20 | 21 | The default login credentials are “admin” with no password. If you are running the latest version of Routeros 6 or 7, you will be prompted to change the password on first login. 22 | 23 | This guide will give you commands to enter in the Mikrotik Terminal. You can do this either via SSH or in the Terminal that is included in the Winbox application. 24 | 25 | 26 | We will build the WAN connection on ether1, and the LAN connection on ether2. Ether2 will be configured as slave interface of a bridge interface. Add the following: 27 | ``` 28 | /interface vlan 29 | add interface=ether1 name=vlan1.6 vlan-id=6 30 | ``` 31 | Now we make the pppoe connection with KPN 32 | ``` 33 | /interface pppoe-client 34 | add add-default-route=yes allow=pap disabled=no interface=vlan1.6 \ 35 | keepalive-timeout=20 max-mru=1500 max-mtu=1500 name=pppoe-client \ 36 | password=kpn profile=default user=kpn 37 | ``` 38 | We will now add the bridge interface for the LAN 39 | ``` 40 | /interface bridge 41 | add name=local arp=proxy-arp 42 | ``` 43 | Add the necessary ports to your bridge 44 | ``` 45 | /interface bridge port 46 | add bridge=local interface=ether2 47 | ``` 48 | Set the gateway address for the LAN. You can change this to your needs. 49 | ``` 50 | /ip address 51 | add address=10.0.0.1/24 interface=local 52 | ``` 53 | Set DNS forwarders. In this example we will be using Google DNS. We will also use the Mikrotik as DNS server for the LAN. 54 | ``` 55 | /ip dns 56 | set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4 57 | ``` 58 | Configure a basic firewall. For proper hardening, refer to this Mikrotik article: [Building Advanced Firewall](https://help.mikrotik.com/docs/display/ROS/Building+Advanced+Firewall). The following filter rules only cover the input chain on the pppoe-client. This means the LAN side is not hardened. 59 | ``` 60 | /ip firewall filter 61 | add action=accept chain=input in-interface=pppoe-client protocol=icmp 62 | add action=accept chain=input connection-state=established,related 63 | add action=drop chain=input in-interface=pppoe-client 64 | ``` 65 | Configure outbound NAT 66 | ``` 67 | /ip firewall nat 68 | add action=masquerade chain=srcnat out-interface=pppoe-client 69 | ``` 70 | Configure a DHCP server for the LAN. If you changed anything in the IP Address section above, also change the values here to match. 71 | ``` 72 | /ip pool 73 | add name=thuisnetwerk ranges=10.0.0.10-10.0.0.254 74 | /ip dhcp-server 75 | add address-pool=thuisnetwerk authoritative=yes interface=local \ 76 | lease-time=8h name=dhcp-home 77 | /ip dhcp-server network 78 | add address=10.0.0.0/24 dns-server=10.0.0.1 domain=home.local gateway=\ 79 | 10.0.0.1 80 | ``` 81 | Now, if you connect your device to ether2, you should get an IP address via DHCP in the 10.0.0.0/24 range, and you will have internet access. We recommend updating the Mikrotik device to the latest Stable version of Routeros 6 or 7. You can do this at System > Packages > Check for Updates. Also update the firmware at System > RouterBOARD > Upgrade. Both updates require a restart. 82 | -------------------------------------------------------------------------------- /guides/mikrotik/kpn/Mikrotik-toevoegen-van-ipv6-aan-internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik IPv6 with Internet Only 3 | description: How to Setup KPN IPv6 in Mikrotik 4 | published: true 5 | date: 2023-09-09T18:35:19.181Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:39:04.633Z 9 | --- 10 | 11 | # Mikrotik - Adding ipv6 to internet only 12 | 13 | You can download Winbox here: [ MikroTik Routers and Wireless - Software](https://mikrotik.com/download) 14 | 15 | This guide will give you commands to enter in the Mikrotik Terminal. You can do this either via SSH or in the Terminal that is included in the Winbox application. 16 | 17 | This guide will only work if you have installed this guide [Mikrotik-Internet-only](/guides/mikrotik/kpn/Mikrotik-Internet-only) 18 | 19 | On RouterOS version 6, make sure to enable/install the IPv6 package. On RouterOS version 7 this package is included. 20 | 21 | Create a PPP profile for ipv6 22 | 23 | ``` 24 | /ppp profile 25 | add name=default-ipv6 only-one=yes remote-ipv6-prefix-pool=*0 use-compression=yes use-upnp=no 26 | ``` 27 | Now we make the pppoe connection with KPN (REMOVE YOUR OLD PPPOE CONNECTION) 28 | or on your existing pppoe client change profile to default-ipv6 29 | 30 | ``` 31 | /interface pppoe-client 32 | add add-default-route=yes allow=pap disabled=no interface=vlan1.6 keepalive-timeout=20 max-mru=auto max-mtu=auto name="pppoe-client" profile=default-ipv6 user=kpn@kpn 33 | ``` 34 | 35 | Add the DHCPv6 client 36 | 37 | ``` 38 | /ipv6 dhcp-client 39 | add add-default-route=yes interface=pppoe-client pool-name=*0 pool-prefix-length=48 request=prefix use-peer-dns=no 40 | ``` 41 | 42 | Add basic firewall 43 | 44 | ``` 45 | /ipv6 firewall filter 46 | add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked 47 | add action=accept chain=input comment="defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=udp src-address=fe80::/10 48 | add action=drop chain=input comment="drop everything else" 49 | ``` 50 | 51 | Configure ND Settings 52 | 53 | ``` 54 | /ipv6 nd 55 | add advertise-mac-address=no hop-limit=64 interface=local 56 | ``` 57 | 58 | Add LAN Address 59 | 60 | ``` 61 | /ipv6 address 62 | add from-pool=*0 interface=local 63 | ``` 64 | 65 | Now you have added ipv6 to your Mikrotik device. We recommend updating the Mikrotik device to the latest Stable version of Routeros 6 or 7. You can do this at System > Packages > Check for Updates. Also update the firmware at System > RouterBOARD > Upgrade. Both updates require a restart. -------------------------------------------------------------------------------- /guides/mikrotik/kpn/Mikrotik-tv-settings-with-vlan.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik TV configuration With VLAN 3 | description: How to Setup KPN on Mikrotik with a seperate TV VLAN 4 | published: true 5 | date: 2023-04-23T15:53:40.253Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:32:48.816Z 9 | --- 10 | 11 | ## Mikrotik tv settings 12 | 13 | This guide explains how to add KPN IPTV to your router configuration. Note that we are assuming that you followed our tutorial on how to set up internet on your Mikrotik. If your configuration differs, change the settings below to match your configuration. If you are unsure how to do this, feel free to ask about it in our Discord server. The reference internet configuration can be found here: [Mikrotik-Internet-only](/guides/mikrotik/kpn/Mikrotik-Internet-only.md) 14 | 15 | Before you begin, if you are running Routeros 6, make sure the extra "multicast" package is installed. If you are running Routeros 7, skip this step. Routeros 6 does not include the IGMP Proxy by default. 16 | 17 | Add a VLAN interface with VLAN id 4 and add it to ether1. We are assuming that ether1 is the port that connects to your NTU or (bridged) Modem. We will also add a VLAN interface to our bridge (that we created in the internet-only guide), which will be used for our IPTV devices. 18 | 19 | ```text 20 | /interface vlan 21 | add comment=TV interface=ether1 name=vlan1.4 vlan-id=4 22 | add comment=tv-lan interface=local name=Vlan3 vlan-id=3 23 | ``` 24 | 25 | Turn on *igmp-snooping* on the bridge interface. The command below adds a bridge. If you already have a bridge that you want to use for this, only set igmp-snooping on it to yes. We will also complete the bridge vlan table and assign an ethernet interface to vlan 3 via PVID. 26 | 27 | ```text 28 | /interface bridge 29 | add arp=proxy-arp igmp-snooping=yes name=local protocol-mode=none vlan-filtering=yes 30 | 31 | /interface bridge vlan 32 | add bridge=local tagged=local vlan-ids=3 33 | 34 | /interface bridge port 35 | add bridge=local interface=ether3 pvid=3 36 | ``` 37 | 38 | Set Ip Address for tv-lan network 39 | 40 | ```text 41 | /ip pool 42 | add name=tv-lan ranges=10.0.3.20-10.0.3.254 43 | 44 | /ip dhcp-server 45 | add address-pool=tv-lan interface=Vlan3 lease-time=30m name=tv-lan 46 | 47 | /ip address 48 | add address=10.0.3.1/24 comment="tv-lan (vlan3)" interface=Vlan3 network=10.0.3.0 49 | 50 | /ip dhcp-server network 51 | add address=10.0.3.0/24 dns-server=195.121.1.34,195.121.1.66 domain=tv-lan.local gateway=10.0.3.1 52 | ``` 53 | 54 | Add DHCP Options 55 | 56 | ```text 57 | /ip dhcp-server option 58 | add code=60 name=option60-vendorclass value="'IPTV_RG'" 59 | add code=28 name=option28-broadcast value="'10.0.3.255'" 60 | 61 | /ip dhcp-server option sets 62 | add name=IPTV options=option60-vendorclass,option28-broadcast 63 | ``` 64 | 65 | Configure the dhcp client and its options 66 | 67 | ```text 68 | /ip dhcp-client option 69 | add code=60 name=option60-vendorclass value="'IPTV_RG'" 70 | /ip dhcp-client 71 | add add-default-route=special-classless default-route-distance=210 dhcp-options=option60-vendorclass disabled=no interface=vlan1.4 use-peer-dns=no use-peer-ntp=no 72 | ``` 73 | 74 | Configure the IGMP Proxy 75 | 76 | ```text 77 | /routing igmp-proxy interface 78 | add alternative-subnets=0.0.0.0/0 interface=vlan1.4 upstream=yes 79 | add interface=Vlan3 80 | 81 | /routing igmp-proxy 82 | set quick-leave=yes 83 | ``` 84 | 85 | Add firewall rules 86 | 87 | ```text 88 | /ip firewall nat 89 | add action=masquerade chain=srcnat comment="IPTV" dst-address=213.75.0.0/16 out-interface=vlan1.4 90 | add action=masquerade chain=srcnat comment="IPTV" dst-address=217.166.0.0/16 out-interface=vlan1.4 91 | add action=masquerade chain=srcnat comment="IPTV" dst-address=10.207.0.0/20 out-interface=vlan1.4 92 | 93 | /ip firewall filter 94 | add action=accept chain=input comment="IPTV IGMP" dst-address=224.0.0.0/4 in-interface=vlan1.4 protocol=igmp 95 | ``` 96 | 97 | Set Dhcp-option for tv 98 | 99 | ```text 100 | /ip dhcp-server 101 | network set numbers=1 dhcp-option-set=IPTV 102 | ``` 103 | 104 | The DHCP options for the existing DHCP Server don't "just work", you have to select them in the DHCP Network. See IP > DHCP Server > Networks and double click your existing network. Add the option set to it with the dropdown menu. 105 | 106 | Note that IPTV will only work on ports that you add to the bridge interface "local" in Bridge > Ports. Not on switches behind the Mikrotik router. Keep this in mind when budgetting interfaces to client devices or switches or any other device that might need an ethernet connection. 107 | -------------------------------------------------------------------------------- /guides/mikrotik/kpn/Mikrotik-tv-settings.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik TV configuration 3 | description: How to Setup KPN IPTV on Mikrotik 4 | published: true 5 | date: 2023-04-23T15:53:57.024Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:30:49.328Z 9 | --- 10 | 11 | # Mikrotik tv settings 12 | 13 | This guide explains how to add KPN IPTV to your router configuration. Note that we are assuming that you followed our tutorial on how to set up internet on your Mikrotik. If your configuration differs, change the settings below to match your configuration. If you are unsure how to do this, feel free to ask about it in our Discord server. The reference internet configuration can be found here: [Mikrotik-Internet-only](/guides/mikrotik/kpn/Mikrotik-Internet-only.md) 14 | 15 | Before you begin, if you are running Routeros 6, make sure the extra "multicast" package is installed. If you are running Routeros 7, skip this step. Routeros 6 does not include the IGMP Proxy by default. 16 | 17 | Add a VLAN interface with VLAN id 4 and add it to ether1. We are assuming that ether1 is the port that connects to your NTU or (bridged) Modem. 18 | ``` 19 | /interface vlan 20 | add interface=ether1 name=vlan1.4 vlan-id=4 21 | ``` 22 | 23 | Turn on *igmp-snooping* on the bridge interface. The command below adds a bridge. If you already have a bridge that you want to use for this, only set igmp-snooping on it to yes. 24 | ``` 25 | /interface bridge 26 | add arp=proxy-arp igmp-snooping=yes name=local protocol-mode=none 27 | ``` 28 | 29 | Add DHCP Options 30 | ``` 31 | /ip dhcp-server option 32 | add code=60 name=option60-vendorclass value="'IPTV_RG'" 33 | add code=28 name=option28-broadcast value="'10.0.0.255'" 34 | 35 | /ip dhcp-server option sets 36 | add name=IPTV options=option60-vendorclass,option28-broadcast 37 | ``` 38 | 39 | Configure the dhcp client and its options 40 | ``` 41 | /ip dhcp-client option 42 | add code=60 name=option60-vendorclass value="'IPTV_RG'" 43 | /ip dhcp-client 44 | add add-default-route=special-classless default-route-distance=210 dhcp-options=option60-vendorclass disabled=no \ 45 | interface=vlan1.4 use-peer-dns=no use-peer-ntp=no 46 | ``` 47 | 48 | Configure the IGMP Proxy 49 | ``` 50 | /routing igmp-proxy interface 51 | add alternative-subnets=0.0.0.0/0 interface=vlan1.4 upstream=yes 52 | add interface=local 53 | 54 | /routing igmp-proxy 55 | set quick-leave=yes 56 | ``` 57 | 58 | Add firewall rules 59 | ``` 60 | /ip firewall nat 61 | add action=masquerade chain=srcnat comment="IPTV" dst-address=213.75.0.0/16 out-interface=vlan1.4 62 | add action=masquerade chain=srcnat comment="IPTV" dst-address=217.166.0.0/16 out-interface=vlan1.4 63 | add action=masquerade chain=srcnat comment="IPTV" dst-address=10.207.0.0/20 out-interface=vlan1.4 64 | 65 | /ip firewall filter 66 | add action=accept chain=input comment="IPTV IGMP" dst-address=224.0.0.0/4 in-interface=vlan1.4 protocol=igmp 67 | ``` 68 | 69 | The DHCP options for the existing DHCP Server don't "just work", you have to select them in the DHCP Network. See IP > DHCP Server > Networks and double click your existing network. Add the option set to it with the dropdown menu. 70 | 71 | Note that IPTV will only work on ports that you add to the bridge interface "local" in Bridge > Ports. Not on switches behind the Mikrotik router. Keep this in mind when budgetting interfaces to client devices or switches or any other device that might need an ethernet connection. -------------------------------------------------------------------------------- /guides/mikrotik/kpn/Mikrotik-voice-telephony.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik Voice / Telephony 3 | description: How to Setup KPN Voice / Telephony in Mikrotik 4 | published: true 5 | date: 2023-04-23T15:52:54.054Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:44:28.220Z 9 | --- 10 | 11 | # Mikrotik Voice / Telephony 12 | 13 | There is little configuration required to get third party VoIP products to work with KPN SIP. Nowadays you can easily find the required information in Mijn KPN. You will need the Mijn KPN account, because the SIP password for your account is only visible there. We will assume that you know how to set up VoIP equipment. If not, feel free to ask about this in our Discord server. 14 | 15 | Previously it was necessary to add VLAN 7 to the WAN interface in order to register SIP accounts. This is no longer the case. VLAN 6 now carries the required connections. You will already have VLAN 6 in use after setting up internet access. 16 | 17 | You may have to disable the 'sip' service in /ip firewall service-ports. Generally it depends on the equipment used. If you experience problems like one-way audio or not being able to register your SIP account, disable this service. 18 | 19 | ``` 20 | /ip firewall service-port set disabled=yes sip 21 | ``` 22 | -------------------------------------------------------------------------------- /guides/mikrotik/online.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - Online 3 | description: 4 | published: true 5 | date: 2023-04-22T14:55:01.550Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T14:51:58.461Z 9 | --- 10 | 11 | # Provider: Online - online.nl 12 | 13 | It's a nice idea when your provider has the knowledge and experience to let you enjoy everything the internet has to offer without worry. Online.nl is one of the first providers in the Netherlands. We have been around since 1994, back then under the name Euronet. Together with other pioneers, we connected the Netherlands to the web and we were even the very first provider to sell internet access in shops. 14 | 15 | Our 1994 installation manual stated: 'The internet is expected to develop into the communication tool of the future.' Now, almost 30 years later, we work, learn, play and create online. We shop, talk and meet online. We watch our TV series and movies online. The internet has become not just the means of communication, but a necessity of life. For everyone, from young to old. 16 | 17 | We have been providing reliable and affordable internet services since 1994 and our professional staff are ready to help you. With us, you get it all as standard: with fibre-optic internet, low-cost call rates and interactive TV from Canal Digitaal. With more than 80 TV channels, CANAL+ Films & Series and Film1 as standard in your TV package. We offer 100% installation guarantee, free switching service, a free WiFi modem and much more. With no hidden costs and no worries. 18 | 19 | We have never lost our pioneering spirit. Thus, together with our partner Canal Digitaal, we are still at the forefront of the interactive television revolution and we believe that fast internet and affordable calling should be available to everyone. We work with the latest technology, such as fibre optics, and we challenge the market by offering just a bit more for the same money. 20 | 21 | We can no longer imagine a world without internet. Yet this is only the beginning. As in 1994, we dare to predict that it will become much bigger than it already is. That everything will be connected to everything. From our cities, roads, houses and cars to our refrigerators, doorbells and clothes. We work online, we learn online and even for our health we increasingly rely on the internet. In short: the future is online, just like us. 22 | 23 | ![online.png](/images/site/online.png) -------------------------------------------------------------------------------- /guides/mikrotik/online/Mikrotik-Internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik internet only Online 3 | description: How to Setup Online Internet Only on Mikrotik 4 | published: true 5 | date: 2023-04-23T15:52:10.291Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T14:47:44.714Z 9 | --- 10 | 11 | # Online internet only 12 | 13 | This guide is based on a Mikrotik device with at least two Ethernet ports. We start with a completely empty configuration. To wipe your configuration, connect to your Mikrotik device via Winbox or Webfig (HTTP) and navigate to System > Reset Configuration. Tick “No Default Configuration” and reset the device via the “Reset Configuration” button. The device will now restart. 14 | 15 | After wiping the configuration, you can connect to the Mikrotik via MAC-Winbox on Windows or via Wine. We recommend configuring a management network on an Ethernet interface that you will not use for the network that we will create in this guide. The simplest way to do this is to set a unique IP address on for example ether3 (as ether3 will not be used in this guide) and to connect to the device via IP on ether3. Refer to the IP Address section in the steps below to see how to do this. 16 | 17 | You can download Winbox here: [ MikroTik Routers and Wireless - Software](https://mikrotik.com/download) 18 | 19 | This guide requires that you install the ‘multicast’ package for Routeros version 6. If you’re running Routeros 7, skip this step. 20 | 21 | The default login credentials are “admin” with no password. If you are running the latest version of Routeros 6 or 7, you will be prompted to change the password on first login. 22 | 23 | This guide will give you commands to enter in the Mikrotik Terminal. You can do this either via SSH or in the Terminal that is included in the Winbox application. 24 | 25 | 26 | We will build the WAN connection on ether1, and the LAN connection on ether2. Ether2 will be configured as slave interface of a bridge interface. Add the following: 27 | ``` 28 | /interface vlan 29 | add interface=ether1 name=vlan1.1001 vlan-id=1001 30 | ``` 31 | Now we configure the DHCP client on VLAN 1001 32 | ``` 33 | /ip dhcp-client 34 | add interface=vlan1.1001 add-default-route=yes disabled=no use-peer-dns=no use-peer-ntp=no 35 | ``` 36 | We will now add the bridge interface for the LAN 37 | ``` 38 | /interface bridge 39 | add name=local arp=proxy-arp 40 | ``` 41 | Add the necessary ports to your bridge 42 | ``` 43 | /interface bridge port 44 | add bridge=local interface=ether2 45 | ``` 46 | Set the gateway address for the LAN. You can change this to your needs. 47 | ``` 48 | /ip address 49 | add address=10.0.0.1/24 interface=local 50 | ``` 51 | Set DNS forwarders. In this example we will be using Google DNS. We will also use the Mikrotik as DNS server for the LAN. 52 | ``` 53 | /ip dns 54 | set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4 55 | ``` 56 | Configure a basic firewall. For proper hardening, refer to this Mikrotik article: [Building Advanced Firewall](https://help.mikrotik.com/docs/display/ROS/Building+Advanced+Firewall). The following filter rules only cover the input chain on the WAN-VLAN interface. This means the LAN side is not hardened. 57 | ``` 58 | /ip firewall filter 59 | add action=accept chain=input in-interface=vlan1.1001 protocol=icmp 60 | add action=accept chain=input connection-state=established,related 61 | add action=drop chain=input in-interface=vlan1.1001 62 | ``` 63 | Configure outbound NAT 64 | ``` 65 | /ip firewall nat 66 | add action=masquerade chain=srcnat out-interface=vlan1.1001 67 | ``` 68 | Configure a DHCP server for the LAN. If you changed anything in the IP Address section above, also change the values here to match. 69 | ``` 70 | /ip pool 71 | add name=thuisnetwerk ranges=10.0.0.10-10.0.0.254 72 | /ip dhcp-server 73 | add address-pool=thuisnetwerk authoritative=yes interface=local \ 74 | lease-time=8h name=dhcp-home 75 | /ip dhcp-server network 76 | add address=10.0.0.0/24 dns-server=10.0.0.1 domain=home.local gateway=\ 77 | 10.0.0.1 78 | ``` 79 | Now, if you connect your device to ether2, you should get an IP address via DHCP in the 10.0.0.0/24 range, and you will have internet access. We recommend updating the Mikrotik device to the latest Stable version of Routeros 6 or 7. You can do this at System > Packages > Check for Updates. Also update the firmware at System > RouterBOARD > Upgrade. Both updates require a restart. 80 | -------------------------------------------------------------------------------- /guides/mikrotik/solcon.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - Solcon 3 | description: 4 | published: true 5 | date: 2023-04-22T15:07:06.228Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T15:07:06.228Z 9 | --- 10 | 11 | # Provider: Solcon 12 | 13 | Solcon's ambition is to make more secure and manageable internet available to everyone in the Netherlands. Founded in 1996, provider Solcon focuses on consumer and small business SME customer groups. 14 | 15 | Solcon believes that everyone should be able to enjoy the advantages of this digital world to the fullest and face as few disadvantages as possible. Solcon does this by providing customers with practical innovative tools and knowledge. In this way, customers can benefit from digital media in the most responsible and personal way possible. 16 | 17 | Solcon offers a wide range of services, fully ISO27001-certified (consumer and business): from quad play (internet, television, telephony and mobile) to hosting. At Solcon, customers will find the most advanced filters and secure data storage. It also protects customers against internet crime such as malware, phishing and ransomware. 18 | 19 | Nationwide, Solcon uses KPN's quality network. In fibre-optic outlying areas, Solcon operates different networks. In doing so, it deploys the latest technologies, such as GPON technology. 20 | 21 | Solcon believes in the power of real contact. The customer care staff like to take the time for customers. No time pressure and interview protocols. And... Solcon is only satisfied when customers are. It wants to give customers the attention and service they deserve. 22 | 23 | ![solcon.png](/images/site/solcon.png) -------------------------------------------------------------------------------- /guides/mikrotik/solcon/Mikrotik-Internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik internet only Solcon 3 | description: How to Setup Solcon Internet Only on Mikrotik 4 | published: true 5 | date: 2023-04-23T15:51:48.352Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T14:46:31.545Z 9 | --- 10 | 11 | # Solcon internet only 12 | 13 | This guide is based on a Mikrotik device with at least two Ethernet ports. We start with a completely empty configuration. To wipe your configuration, connect to your Mikrotik device via Winbox or Webfig (HTTP) and navigate to System > Reset Configuration. Tick “No Default Configuration” and reset the device via the “Reset Configuration” button. The device will now restart. 14 | 15 | After wiping the configuration, you can connect to the Mikrotik via MAC-Winbox on Windows or via Wine. We recommend configuring a management network on an Ethernet interface that you will not use for the network that we will create in this guide. The simplest way to do this is to set a unique IP address on for example ether3 (as ether3 will not be used in this guide) and to connect to the device via IP on ether3. Refer to the IP Address section in the steps below to see how to do this. 16 | 17 | You can download Winbox here: [ MikroTik Routers and Wireless - Software](https://mikrotik.com/download) 18 | 19 | This guide requires that you install the ‘multicast’ package for Routeros version 6. If you’re running Routeros 7, skip this step. 20 | 21 | The default login credentials are “admin” with no password. If you are running the latest version of Routeros 6 or 7, you will be prompted to change the password on first login. 22 | 23 | This guide will give you commands to enter in the Mikrotik Terminal. You can do this either via SSH or in the Terminal that is included in the Winbox application. 24 | 25 | 26 | 27 | We will build the WAN connection on ether1, and the LAN connection on ether2. Ether2 will be configured as slave interface of a bridge interface. Add the following: 28 | 29 | Now we configure the DHCP client on ether1 30 | ``` 31 | /ip dhcp-client 32 | add interface=ether1 add-default-route=yes disabled=no use-peer-dns=no use-peer-ntp=no 33 | ``` 34 | We will now add the bridge interface for the LAN 35 | ``` 36 | /interface bridge 37 | add name=local arp=proxy-arp 38 | ``` 39 | Add the necessary ports to your bridge 40 | ``` 41 | /interface bridge port 42 | add bridge=local interface=ether2 43 | ``` 44 | Set the gateway address for the LAN. You can change this to your needs. 45 | ``` 46 | /ip address 47 | add address=10.0.0.1/24 interface=local 48 | ``` 49 | Set DNS forwarders. In this example we will be using Google DNS. We will also use the Mikrotik as DNS server for the LAN. 50 | ``` 51 | /ip dns 52 | set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4 53 | ``` 54 | Configure a basic firewall. For proper hardening, refer to this Mikrotik article: [Building Advanced Firewall](https://help.mikrotik.com/docs/display/ROS/Building+Advanced+Firewall). The following filter rules only cover the input chain on the WAN-VLAN interface. This means the LAN side is not hardened. 55 | ``` 56 | /ip firewall filter 57 | add action=accept chain=input in-interface=ether1 protocol=icmp 58 | add action=accept chain=input connection-state=established,related 59 | add action=drop chain=input in-interface=ether1 60 | ``` 61 | Configure outbound NAT 62 | ``` 63 | /ip firewall nat 64 | add action=masquerade chain=srcnat out-interface=ether1 65 | ``` 66 | Configure a DHCP server for the LAN. If you changed anything in the IP Address section above, also change the values here to match. 67 | ``` 68 | /ip pool 69 | add name=thuisnetwerk ranges=10.0.0.10-10.0.0.254 70 | /ip dhcp-server 71 | add address-pool=thuisnetwerk authoritative=yes interface=local \ 72 | lease-time=8h name=dhcp-home 73 | /ip dhcp-server network 74 | add address=10.0.0.0/24 dns-server=10.0.0.1 domain=home.local gateway=\ 75 | 10.0.0.1 76 | ``` 77 | 78 | Now, if you connect your device to ether2, you should get an IP address via DHCP in the 10.0.0.0/24 range, and you will have internet access. We recommend updating the Mikrotik device to the latest Stable version of Routeros 6 or 7. You can do this at System > Packages > Check for Updates. Also update the firmware at System > RouterBOARD > Upgrade. Both updates require a restart. 79 | -------------------------------------------------------------------------------- /guides/mikrotik/t-mobile.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - T-Mobile 3 | description: 4 | published: true 5 | date: 2023-04-22T15:04:35.218Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T15:04:35.218Z 9 | --- 10 | 11 | # Provider: T-Mobile 12 | T-Mobile is the brand name used by some of the mobile communications subsidiaries of the German telecommunications company Deutsche Telekom AG in the Czech Republic (T-Mobile Czech Republic), Poland (T-Mobile Polska), the United States (T-Mobile US) and by the former subsidiary in the Netherlands (T-Mobile Netherlands). 13 | 14 | The T-Mobile brand was introduced in 1996 and the name was previously used by subsidiaries in other countries, including Austria (now Magenta), Croatia (now Hrvatski Telekom), Germany (now Deutsche Telekom), Hungary (now Magyar Telekom), Montenegro (now Crnogorski Telekom), North Macedonia (now Makedonski Telekom), Romania (now Telekom România), Slovakia (now Slovak Telekom), and the United Kingdom (now EE Limited). 15 | 16 | In 1999, Deutsche Telekom formed the holding company T-Mobile International AG for its mobile communications subsidiaries. From 2003 to 2007, T-Mobile International was one of Deutsche Telekom's services, in addition to "Broadband/Fixnet", "Business Customers" and "Group HQ and Shared Services". In 2009, Deutsche Telekom transformed its structure to adopt a regional setup (Germany, Europe, US). By combining its previously separated fixed and mobile subsidiaries to form integrated local businesses, T-Mobile International itself was merged into Deutsche Telekom AG. 17 | 18 | When T-Mobile International AG existed, the holding company was based in Bonn, Germany, and its subsidiaries operated GSM-, UMTS- and LTE-based cellular networks in Europe, the United States, Puerto Rico and the U.S. Virgin Islands. The company had financial stakes in mobile operators in both Central and Eastern Europe. Globally, T-Mobile International's subsidiaries had a combined total of approximately 230 million subscribers. It was the world's thirteenth-largest mobile-phone service provider by subscribers, and the fourth-largest multinational after the UK's Vodafone, India's Airtel, and Spain's Telefónica. 19 | 20 | ## History 21 | 22 | On 1 July 1989, West Germany reorganized Deutsche Bundespost and consolidated telecommunications into a new unit, Deutsche Bundespost Telekom. On 1 July 1992, it began to operate Germany's first GSM network, along with the C-Netz, as its DeTeMobil subsidiary. The GSM 900 MHz frequency band was referred to as the "D-Netz", and Telekom named its service D1; the private consortium awarded the second license (now Vodafone Germany) chose the name D2. Deutsche Bundespost Telekom was renamed Deutsche Telekom AG on 1 January 1995 as part of phase two of the German communications reform. This process of deregulation continued in November 1996, when DT was privatized and had the largest European IPO at the time, with the stock abbreviation 'DT 1'. 23 | 24 | In December 1999, T-Mobile International AG & Co. KG holding company was founded (later renamed T-Mobile International AG). In 2002, as DT consolidated its international operations, it anglicized the T-Mobil name to T-Mobile. 25 | 26 | On 5 July 2005 Deutsche Telekom transformed its structure and adopted a regional setup (Germany, Europe, US). Where available, the local mobile businesses were combined with the respective local wireline businesses to follow the integrated business approach. In 2009 T-Mobile International AG was merged into Deutsche Telekom AG. 27 | 28 | On 16 August 2021, T-Mobile announced that a hacker had illegally accessed more than 76 million Americans’ private data, with an American hacker named John Binns later claiming responsibility. Several class action lawsuits have been filed in relation to the data breach. In July 2022, T-mobile agreed to a $350 million settlement during the company's hearing at Missouri federal court, in relation to the data breech and subsequent class action litigation. The $350 million settlement will include $25,000 in reimbursement for the losses to organisations, compensation to the victims of the data breech of $25 per hour and to provide two-year subscriptions to identity theft services and $150 million on improving data security. 29 | 30 | On 19 January 2023, T-Mobile said it first identified a bad actor had obtained the data of 37 million customers via an unauthorized API (starting on or around 25 November 2022). The data included the name, billing address, email, phone number, date of birth, T-Mobile account number, and information such as the number of lines on the account and plan features. 31 | ![t-mobile.png](/images/site/t-mobile.png) -------------------------------------------------------------------------------- /guides/mikrotik/t-mobile/Mikrotik-Internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik internet only T-mobile 3 | description: How to Setup T-Mobile Internet Only on Mikrotik 4 | published: true 5 | date: 2023-04-23T15:51:04.137Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T14:44:00.017Z 9 | --- 10 | 11 | # Mikrotik internet only 12 | 13 | This guide is based on a Mikrotik device with at least two Ethernet ports. We start with a completely empty configuration. To wipe your configuration, connect to your Mikrotik device via Winbox or Webfig (HTTP) and navigate to System > Reset Configuration. Tick “No Default Configuration” and reset the device via the “Reset Configuration” button. The device will now restart. 14 | 15 | After wiping the configuration, you can connect to the Mikrotik via MAC-Winbox on Windows or via Wine. We recommend configuring a management network on an Ethernet interface that you will not use for the network that we will create in this guide. The simplest way to do this is to set a unique IP address on for example ether3 (as ether3 will not be used in this guide) and to connect to the device via IP on ether3. Refer to the IP Address section in the steps below to see how to do this. 16 | 17 | You can download Winbox here: [ MikroTik Routers and Wireless - Software](https://mikrotik.com/download) 18 | 19 | This guide requires that you install the ‘multicast’ package for Routeros version 6. If you’re running Routeros 7, skip this step. 20 | 21 | The default login credentials are “admin” with no password. If you are running the latest version of Routeros 6 or 7, you will be prompted to change the password on first login. 22 | 23 | This guide will give you commands to enter in the Mikrotik Terminal. You can do this either via SSH or in the Terminal that is included in the Winbox application. 24 | 25 | 26 | We will build the WAN connection on ether1, and the LAN connection on ether2. Ether2 will be configured as slave interface of a bridge interface. Add the following: 27 | ``` 28 | /interface vlan 29 | add interface=ether1 name=vlan1.300 vlan-id=300 30 | ``` 31 | Now we configure the DHCP client on VLAN 300 32 | ``` 33 | /ip dhcp-client 34 | add interface=vlan1.300 add-default-route=yes disabled=no use-peer-dns=no use-peer-ntp=no 35 | ``` 36 | We will now add the bridge interface for the LAN 37 | ``` 38 | /interface bridge 39 | add name=local arp=proxy-arp 40 | ``` 41 | Add the necessary ports to your bridge 42 | ``` 43 | /interface bridge port 44 | add bridge=local interface=ether2 45 | ``` 46 | Set the gateway address for the LAN. You can change this to your needs. 47 | ``` 48 | /ip address 49 | add address=10.0.0.1/24 interface=local 50 | ``` 51 | Set DNS forwarders. In this example we will be using Google DNS. We will also use the Mikrotik as DNS server for the LAN. 52 | ``` 53 | /ip dns 54 | set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4 55 | ``` 56 | Configure a basic firewall. For proper hardening, refer to this Mikrotik article: [Building Advanced Firewall](https://help.mikrotik.com/docs/display/ROS/Building+Advanced+Firewall). The following filter rules only cover the input chain on the WAN-VLAN interface. This means the LAN side is not hardened. 57 | ``` 58 | /ip firewall filter 59 | add action=accept chain=input in-interface=vlan1.300 protocol=icmp 60 | add action=accept chain=input connection-state=established,related 61 | add action=drop chain=input in-interface=vlan1.300 62 | ``` 63 | Configure outbound NAT 64 | ``` 65 | /ip firewall nat 66 | add action=masquerade chain=srcnat out-interface=vlan1.300 67 | ``` 68 | Configure a DHCP server for the LAN. If you changed anything in the IP Address section above, also change the values here to match. 69 | ``` 70 | /ip pool 71 | add name=thuisnetwerk ranges=10.0.0.10-10.0.0.254 72 | /ip dhcp-server 73 | add address-pool=thuisnetwerk authoritative=yes interface=local \ 74 | lease-time=8h name=dhcp-home 75 | /ip dhcp-server network 76 | add address=10.0.0.0/24 dns-server=10.0.0.1 domain=home.local gateway=\ 77 | 10.0.0.1 78 | ``` 79 | Now, if you connect your device to ether2, you should get an IP address via DHCP in the 10.0.0.0/24 range, and you will have internet access. We recommend updating the Mikrotik device to the latest Stable version of Routeros 6 or 7. You can do this at System > Packages > Check for Updates. Also update the firmware at System > RouterBOARD > Upgrade. Both updates require a restart. 80 | -------------------------------------------------------------------------------- /guides/mikrotik/ziggo.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - Ziggo 3 | description: 4 | published: true 5 | date: 2023-04-22T15:00:45.592Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T15:00:45.592Z 9 | --- 10 | 11 | # Provider: Ziggo - ziggo.nl 12 | 13 | Ziggo Holding B.V. is the largest cable operator in the Netherlands, providing digital cable television, Internet, and telephone service to both residential and commercial customers. 14 | 15 | ## History 16 | The company is the result of the merger between Multikabel, @Home, and Casema and launched officially on 16 May 2008. Later followed by a merger with UPC Nederland in the first quarter of 2015, at that time the second largest cable company in the Netherlands. It kept the brand name Ziggo. Its main competitors are KPN and CanalDigitaal. 17 | 18 | Most of the share capital was up to 2012 held by holding companies of two private equity firms: Cinven and Warburg Pincus. 19 | 20 | On 21 March 2012, Ziggo was listed on the NYSE Euronext stock exchange and later incorporated into the midcap equity AMX index. Additionally, there are options traded on the Ziggo share. 21 | 22 | Cinven and Warburg Pincus started to reduce their stake in Ziggo and exited Ziggo in April 2013. 23 | 24 | In March 2013, Liberty Global acquired a 12.65% stake in Ziggo. This grew to 15% in April and 28.5% in July. 25 | 26 | On 27 January 2014, Liberty Global announced that it would be acquiring all remaining shares in Ziggo for €10 billion. The takeover was subject to regulatory approval and was expected to close by the second quarter of 2014, when Ziggo was expected to merge with UPC Nederland. In May 2014, the European Commission announced opening an in-depth investigation to assess whether the proposed acquisition of Ziggo by Liberty Global is in line with the EU Merger Regulation. The opening of an in-depth inquiry does not prejudge the outcome of the investigation. In November 2014, Liberty Global took over Ziggo. In December 2014, the shares of Ziggo N.V. were delisted from Euronext Amsterdam as Ziggo was converted into the Dutch private limited company (besloten vennootschap) Ziggo Holding B.V. 27 | 28 | On 5 January 2015, Ziggo started to harmonize its cable network with the UPC Nederland cable network. The name UPC was finally phased out in favor of Ziggo on 13 April 2015. 29 | 30 | On 15 February 2016, British telecommunications company Vodafone announced the merger of their Dutch operations Vodafone Netherlands with Liberty Global, the owner of Ziggo. The deal was closed on 31 December, creating a new parent company for both Ziggo and Vodafone, called VodafoneZiggo, with a 50/50 joint ownership by Liberty Global and Vodafone. 31 | 32 | ![ziggo.jpg](/images/site/ziggo.jpg) -------------------------------------------------------------------------------- /guides/mikrotik/ziggo/Mikrotik-internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mikrotik internet only Ziggo 3 | description: How to Setup Ziggo Internet Only on Mikrotik 4 | published: true 5 | date: 2023-04-23T15:49:56.452Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T14:42:42.798Z 9 | --- 10 | 11 | # Mikrotik internet only 12 | 13 | This guide is based on a Mikrotik device with at least two Ethernet ports. We start with a completely empty configuration. To wipe your configuration, connect to your Mikrotik device via Winbox or Webfig (HTTP) and navigate to System > Reset Configuration. Tick “No Default Configuration” and reset the device via the “Reset Configuration” button. The device will now restart. 14 | 15 | After wiping the configuration, you can connect to the Mikrotik via MAC-Winbox on Windows or via Wine. We recommend configuring a management network on an Ethernet interface that you will not use for the network that we will create in this guide. The simplest way to do this is to set a unique IP address on for example ether3 (as ether3 will not be used in this guide) and to connect to the device via IP on ether3. Refer to the IP Address section in the steps below to see how to do this. 16 | 17 | You can download Winbox here: [ MikroTik Routers and Wireless - Software](https://mikrotik.com/download) 18 | 19 | This guide requires that you install the ‘multicast’ package for Routeros version 6. If you’re running Routeros 7, skip this step. 20 | 21 | The default login credentials are “admin” with no password. If you are running the latest version of Routeros 6 or 7, you will be prompted to change the password on first login. 22 | 23 | This guide will give you commands to enter in the Mikrotik Terminal. You can do this either via SSH or in the Terminal that is included in the Winbox application. 24 | 25 | Note: make sure your Ziggo modem is set to Bridge mode. You may need to call Ziggo to make this change. 26 | 27 | We will build the WAN connection on ether1, and the LAN connection on ether2. Ether2 will be configured as slave interface of a bridge interface. Add the following: 28 | ``` 29 | /ip dhcp-client 30 | add interface=ether1 add-default-route=yes disabled=no use-peer-dns=no use-peer-ntp=no 31 | ``` 32 | We will now add the bridge interface for the LAN 33 | ``` 34 | /interface bridge 35 | add name=local arp=proxy-arp 36 | ``` 37 | Add the necessary ports to your bridge 38 | ``` 39 | /interface bridge port 40 | add bridge=local interface=ether2 41 | ``` 42 | Set the gateway address for the LAN. You can change this to your needs. 43 | ``` 44 | /ip address 45 | add address=10.0.0.1/24 interface=local 46 | ``` 47 | Set DNS forwarders. In this example we will be using Google DNS. We will also use the Mikrotik as DNS server for the LAN. 48 | ``` 49 | /ip dns 50 | set allow-remote-requests=yes servers=8.8.8.8,8.8.4.4 51 | ``` 52 | Configure a basic firewall. For proper hardening, refer to this Mikrotik article: [Building Advanced Firewall](https://help.mikrotik.com/docs/display/ROS/Building+Advanced+Firewall). The following filter rules only cover the input chain on the WAN interface. This means the LAN side is not hardened. 53 | ``` 54 | /ip firewall filter 55 | add action=accept chain=input in-interface=ether1 protocol=icmp 56 | add action=accept chain=input connection-state=established,related 57 | add action=drop chain=input in-interface=ether1 58 | ``` 59 | Configure outbound NAT 60 | ``` 61 | /ip firewall nat 62 | add action=masquerade chain=srcnat out-interface=ether1 63 | ``` 64 | Configure a DHCP server for the LAN. If you changed anything in the IP Address section above, also change the values here to match. 65 | ``` 66 | /ip pool 67 | add name=thuisnetwerk ranges=10.0.0.10-10.0.0.254 68 | /ip dhcp-server 69 | add address-pool=thuisnetwerk authoritative=yes interface=local \ 70 | lease-time=8h name=dhcp-home 71 | /ip dhcp-server network 72 | add address=10.0.0.0/24 dns-server=10.0.0.1 domain=home.local gateway=\ 73 | 10.0.0.1 74 | ``` 75 | Now, if you connect your device to ether2, you should get an IP address via DHCP in the 10.0.0.0/24 range, and you will have internet access. We recommend updating the Mikrotik device to the latest Stable version of Routeros 6 or 7. You can do this at System > Packages > Check for Updates. Also update the firmware at System > RouterBOARD > Upgrade. Both updates require a restart. 76 | -------------------------------------------------------------------------------- /guides/opnsense.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Router - OPNsense 3 | description: Information about OPNsense 4 | published: true 5 | date: 2023-04-16T18:48:33.691Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T18:18:51.711Z 9 | --- 10 | 11 | # Router - OPNsense - opnsense.org 12 | 13 | OPNsense is an open source, FreeBSD-based firewall and routing software developed by Deciso, a company in the Netherlands that makes hardware and sells support packages for OPNsense. It is a fork of pfSense, which in turn was forked from m0n0wall built on FreeBSD. It was launched in January 2015. When m0n0wall closed down in February 2015 its creator, Manuel Kasper, referred its developer community to OPNsense. 14 | 15 | OPNsense has a web-based interface and can be used on the x86-64 platform. Along with acting as a firewall, it has traffic shaping, load balancing, and virtual private network capabilities, and others can be added via plugins. OPNsense offers next-generation firewall capabilities utilizing Zenarmor, a NGFW plugin developed by OPNsense partner Sunny Valley Networks. 16 | 17 | ## History 18 | In November 2017, a World Intellectual Property Organization panel found Netgate, the copyright holder of pfSense, used the domain opnsense.com in bad faith to discredit OPNsense, and obligated Netgate to transfer domain ownership to Deciso. 19 | 20 | ![opnsense_dashboard_v16_7b.png](/images/site/opnsense_dashboard_v16_7b.png) -------------------------------------------------------------------------------- /guides/opnsense/kpn.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - KPN 3 | description: 4 | published: true 5 | date: 2023-04-16T18:55:31.584Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T18:26:36.257Z 9 | --- 10 | 11 | # Provider: KPN - kpn.com 12 | 13 | KPN is a leading telecommunications and IT provider and market leader in the Netherlands. With our fixed and mobile networks for telephony, data and television, we serve customers at home and abroad. KPN targets both private customers and business users, from small to large. 14 | 15 | ![kpn.jpg](/images/site/kpn.jpg) -------------------------------------------------------------------------------- /guides/opnsense/kpn/opnsense-with-vlan.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: OPNsense with seperate TV VLAN 3 | description: How to Setup KPN on OPNsense with a seperate TV VLAN 4 | published: true 5 | date: 2024-01-04T17:45:21.291Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T19:14:23.766Z 9 | --- 10 | 11 | # How to Setup KPN on OPNsense with seperate TV VLAN 12 | 13 | In this How-To we are going to setup KPN on OPNsense on with iTV. 14 | 15 | We are going to use ```VLAN89``` as our seperate TV VLAN, you can choose to use your own VLAN number. 16 | 17 | ### Step. 1 18 | 19 | After install OPNsense go to 20 | 21 | ``` 22 | System > Firmware > Status 23 | ``` 24 | 25 | ![FWupdate](/images/kpn/opnsense-with-vlan/fwupdate.png) 26 | 27 | Click ```Check for updates``` if there are updates available scroll down the page and install them. 28 | 29 | ### Step. 2 30 | 31 | Go to 32 | 33 | ``` 34 | Interfaces > Other Types > VLAN 35 | ``` 36 | 37 | ![VLANs](/images/kpn/opnsense-with-vlan/vlans.png) 38 | 39 | Create 2 VLANs on your WAN interface: 40 | 41 | ```VLAN6``` 42 | 43 | ```VLAN4``` 44 | 45 | Create 1 VLAN on your LAN interface: 46 | 47 | ```VLAN89``` 48 | 49 | 50 | ### Step. 3 51 | 52 | Go to 53 | 54 | ``` 55 | Interfaces > Assignments 56 | ``` 57 | 58 | ![Assignments](/images/kpn/opnsense-with-vlan/assignments.png) 59 | 60 | Create a interface with VLAN tag: ```Parent: vtnet0 (wan), Tag: 4``` name it ```IPTV_WAN``` 61 | 62 | Create a interface with VLAN tag: ```Parent: vtnet1 (lan), Tag: 89``` name it ```IPTV_LAN``` 63 | 64 | Change the WAN interface to ```Parent: vtnet0 (wan), Tag: 6``` 65 | 66 | Save now. 67 | 68 | ### Step. 4 69 | 70 | Go to 71 | 72 | ``` 73 | Interfaces > WAN 74 | ``` 75 | 76 | ![InterfaceWAN](/images/kpn/opnsense-with-vlan/interfacewan.png) 77 | 78 | **Generic configuration** 79 | 80 | Set IPv4 Configuration Type: ```PPPoE``` 81 | 82 | Set IPv6 Configuration Type: ```DHCPv6``` 83 | 84 | Set MTU: ```1492``` 85 | 86 | **PPPoE configuration** 87 | 88 | Set Username: ```kpn@internet``` 89 | 90 | Set Password: ```kpn``` 91 | 92 | **DHCPv6 client configuration** 93 | 94 | Set Request only an IPv6 prefix: ```True``` 95 | 96 | Set Prefix delegation size: ```48``` 97 | 98 | Set Send IPv6 prefix hint: ```False``` 99 | 100 | Set Use IPv4 connectivity: ```True``` 101 | 102 | Set Use VLAN priority: ```Disabled``` 103 | 104 | ### Step. 5 105 | 106 | Go to 107 | 108 | ``` 109 | Interfaces > IPTV_WAN 110 | ``` 111 | 112 | ![InterfaceWANIPTV](/images/kpn/opnsense-with-vlan/interfacewaniptv.png) 113 | 114 | **Basic configuration** 115 | 116 | Set Enable: ```True``` Enable Interface 117 | 118 | Set Description: ```IPTV_WAN``` 119 | 120 | **Generic configuration** 121 | 122 | Set IPv4 Configuration Type: ```DHCP``` 123 | 124 | **DHCP client configuration** 125 | 126 | Set Configuration Mode: ```Advanced``` 127 | 128 | Set Override MTU: ```True``` 129 | 130 | Set Lease Requirements / Send Options: ```dhcp-class-identifier "IPTV_RG"``` 131 | 132 | Set Lease Requirements / Request Options: ```subnet-mask, routers, broadcast-address, classless-routes``` 133 | 134 | ### Step. 6 135 | 136 | Go to 137 | 138 | ``` 139 | Interfaces > IPTV_LAN 140 | ``` 141 | 142 | ![InterfaceLANIPTV](/images/kpn/opnsense-with-vlan/interfacelaniptv.png) 143 | 144 | **Basic configuration** 145 | 146 | Set Enable: ```True``` Enable Interface 147 | 148 | Set Description: ```IPTV_LAN``` 149 | 150 | **Generic configuration** 151 | 152 | Set IPv4 Configuration Type: ```Static IPv4``` 153 | 154 | **Static IPv4 configuration** 155 | 156 | Set IPv4 address: ```192.168.89.1 / 24``` 157 | 158 | ### Step. 7 159 | 160 | Go to 161 | 162 | ``` 163 | System > Firmware > Plugins 164 | ``` 165 | 166 | ![Plugins](/images/kpn/opnsense-with-vlan/plugins.png) 167 | 168 | Install ```os-igmp-proxy``` 169 | 170 | After installation of ```os-igmp-proxy``` refresh the page. 171 | 172 | ### Step. 8 173 | 174 | Go to 175 | 176 | ``` 177 | Services > IGMP Proxy 178 | ``` 179 | 180 | ![IGMPproxy](/images/kpn/opnsense-with-vlan/igmpproxy.png) 181 | 182 | Here we are going to add 2 streams (Upstream and Downstream) 183 | 184 | **Add Upstream** 185 | 186 | Set Interface: ```IPTV_WAN``` 187 | 188 | Set Type: ```Upstream Interface``` 189 | 190 | Create 2 networks: ```0.0.0.0 / 1``` & ```128.0.0.0 / 1``` 191 | 192 | **Add Downstream** 193 | 194 | Set Interface: ```IPTV_LAN``` 195 | 196 | Set Type: ```Downstream Interface``` 197 | 198 | Create 1 networks: ```192.168.89.0 / 24``` 199 | 200 | ### Step. 9 201 | 202 | Go to 203 | 204 | ``` 205 | Services > DHCPv4 > IPTV_LAN 206 | ``` 207 | 208 | ![DHCPv4](/images/kpn/opnsense-with-vlan/dhcp4.png) 209 | 210 | ![DHCPv4](/images/kpn/opnsense-with-vlan/dhcp4range.png) 211 | 212 | Set Enable ```True``` Enable DHCP server on the IPTV_LAN interface 213 | 214 | Set Range ```192.168.89.10 / 192.168.89.245``` 215 | 216 | Set DNS Servers: 217 | ```195.121.1.34``` 218 | ```195.121.1.66``` 219 | 220 | Set Domain name: ```kpn.home``` 221 | 222 | ![DHCPv4](/images/kpn/opnsense-with-vlan/dhcp4additional.png) 223 | 224 | Set Additional Options 225 | ``` 226 | 60 / Text / IPTV_RG 227 | ``` 228 | ``` 229 | 28 / IP address or host / 192.168.89.255 230 | ``` 231 | 232 | ### Step. 10 233 | 234 | Go to 235 | 236 | ``` 237 | Firewall > NAT > Outbound 238 | ``` 239 | 240 | ![FWNATOutbound](/images/kpn/opnsense-with-vlan/fwnatoutbound.png) 241 | 242 | Set Mode: ```Hybrid outbound NAT rule generation (automatically generated rules are applied after manual rules)``` 243 | 244 | ![FWNATOutboundRule](/images/kpn/opnsense-with-vlan/fwnatoutboundrule.png) 245 | 246 | Create Rule: ```IPTV_WAN IPTV_LAN net * * * IPTV_WAN address * NO``` 247 | 248 | ### Step. 11 249 | 250 | Go to 251 | 252 | ``` 253 | Firewall > Rules > IPTV_WAN 254 | ``` 255 | 256 | ![FWIPTVWAN](/images/kpn/opnsense-with-vlan/fwiptvwan.png) 257 | 258 | 259 | Create 3 rules 260 | 261 | **Rule 1:** 262 | 263 | Set Action: ```Pass``` 264 | 265 | Set Quick: ```True``` 266 | 267 | Set Interface: ```IPTV_WAN``` 268 | 269 | Set Direction: ```in``` 270 | 271 | Set TCP/IP Version: ```IPv4``` 272 | 273 | Set Protocol: ```IGMP``` 274 | 275 | Set Source: ```any``` 276 | 277 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 278 | 279 | Set Advanced Option: ``Show`` 280 | 281 | Set allow options: ```True``` 282 | 283 | **Rule 2:** 284 | 285 | Set Action: ```Pass``` 286 | 287 | Set Quick: ```True``` 288 | 289 | Set Interface: ```IPTV_WAN``` 290 | 291 | Set Direction: ```out``` 292 | 293 | Set TCP/IP Version: ```IPv4``` 294 | 295 | Set Protocol: ```IGMP``` 296 | 297 | Set Source: ```any``` 298 | 299 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 300 | 301 | Set Advanced Option: ``Show`` 302 | 303 | Set allow options: ```True``` 304 | 305 | **Rule 3:** 306 | 307 | Set Action: ```Pass``` 308 | 309 | Set Quick: ```True``` 310 | 311 | Set Interface: ```IPTV_WAN``` 312 | 313 | Set Direction: ```in``` 314 | 315 | Set TCP/IP Version: ```IPv4``` 316 | 317 | Set Protocol: ```*``` 318 | 319 | Set Source: ```any``` 320 | 321 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 322 | 323 | ### Step. 12 324 | 325 | Go to 326 | 327 | ``` 328 | Firewall > Rules > IPTV_LAN 329 | ``` 330 | 331 | ![FWLAN](/images/kpn/opnsense-with-vlan/fwlan.png) 332 | 333 | Create 3 rules at top of the exisiting ones. 334 | 335 | **Rule 1:** 336 | 337 | Set Action: ```Pass``` 338 | 339 | Set Quick: ```True``` 340 | 341 | Set Interface: ```IPTV_LAN``` 342 | 343 | Set Direction: ```in``` 344 | 345 | Set TCP/IP Version: ```IPv4``` 346 | 347 | Set Protocol: ```IGMP``` 348 | 349 | Set Source: ```IPTV_LAN net``` 350 | 351 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 352 | 353 | Set Advanced Option: ``Show`` 354 | 355 | Set allow options: ```True``` 356 | 357 | **Rule 2:** 358 | 359 | Set Action: ```Pass``` 360 | 361 | Set Quick: ```True``` 362 | 363 | Set Interface: ```IPTV_LAN``` 364 | 365 | Set Direction: ```in``` 366 | 367 | Set TCP/IP Version: ```IPv4``` 368 | 369 | Set Protocol: ```any``` 370 | 371 | Set Source: ```IPTV_LAN net``` 372 | 373 | Set Destination: ```Single host or Network``` ```213.75.112.0 / 21``` 374 | 375 | **Rule 3:** 376 | 377 | Set Action: ```Pass``` 378 | 379 | Set Quick: ```True``` 380 | 381 | Set Interface: ```IPTV_LAN``` 382 | 383 | Set Direction: ```in``` 384 | 385 | Set TCP/IP Version: ```IPv4``` 386 | 387 | Set Protocol: ```any``` 388 | 389 | Set Source: ```IPTV_LAN net``` 390 | 391 | Set Destination: ```any``` 392 | -------------------------------------------------------------------------------- /guides/opnsense/kpn/opnsense-without-vlan.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: OPNsense without seperate TV VLAN 3 | description: How to Setup KPN on OPNsense without a seperate TV VLAN 4 | published: true 5 | date: 2024-01-04T17:27:20.729Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T18:13:46.292Z 9 | --- 10 | 11 | # How to Setup KPN on OPNsense with seperate TV VLAN 12 | 13 | In this How-To we are going to setup KPN on OPNsense on with iTV on the LAN interface. 14 | 15 | Where we use ```192.168.2.0/24``` as our network, OPNsense admin can be visited on ```192.168.2.1```. 16 | 17 | ### Step. 1 18 | 19 | After install OPNsense go to 20 | 21 | ``` 22 | System > Firmware > Status 23 | ``` 24 | 25 | ![FWupdate](/images/kpn/opnsense-without-vlan/fwupdate.png) 26 | 27 | Click ```Check for updates``` if there are updates available scroll down the page and install them. 28 | 29 | ### Step. 2 30 | 31 | Go to 32 | 33 | ``` 34 | Interfaces > Other Types > VLAN 35 | ``` 36 | 37 | ![VLANs](/images/kpn/opnsense-without-vlan/vlans.png) 38 | 39 | Create 2 VLANs on your WAN interface: 40 | 41 | ```VLAN6``` 42 | 43 | ```VLAN4``` 44 | 45 | 46 | ### Step. 3 47 | Go to 48 | 49 | ``` 50 | Interfaces > Assignments 51 | ``` 52 | 53 | ![Assignments](/images/kpn/opnsense-without-vlan/assignments.png) 54 | 55 | Create a interface with VLAN tag: ```Parent: vtnet0 (wan), Tag: 4``` call it ```IPTV_WAN``` 56 | 57 | Change the WAN interface to ```Parent: vtnet0 (wan), Tag: 6``` 58 | 59 | Save now. 60 | 61 | ### Step. 4 62 | 63 | Go to 64 | 65 | ``` 66 | Interfaces > WAN 67 | ``` 68 | 69 | ![InterfaceWAN](/images/kpn/opnsense-without-vlan/interfacewan.png) 70 | 71 | **Generic configuration** 72 | 73 | Set IPv4 Configuration Type: ```PPPoE``` 74 | 75 | Set IPv6 Configuration Type: ```DHCPv6``` 76 | 77 | Set MTU: ```1492``` 78 | 79 | **PPPoE configuration** 80 | 81 | Set Username: ```kpn@internet``` 82 | 83 | Set Password: ```kpn``` 84 | 85 | **DHCPv6 client configuration** 86 | 87 | Set Request only an IPv6 prefix: ```True``` 88 | 89 | Set Prefix delegation size: ```48``` 90 | 91 | Set Send IPv6 prefix hint: ```False``` 92 | 93 | Set Use IPv4 connectivity: ```True``` 94 | 95 | Set Use VLAN priority: ```Disabled``` 96 | 97 | ### Step. 5 98 | 99 | Go to 100 | 101 | ``` 102 | Interfaces > IPTV_WAN 103 | ``` 104 | 105 | ![InterfaceWANIPTV](/images/kpn/opnsense-without-vlan/interfacewaniptv.png) 106 | 107 | **Basic configuration** 108 | 109 | Set Enable: ```True``` Enable Interface 110 | 111 | Set Description: ```IPTV_WAN``` 112 | 113 | **Generic configuration** 114 | 115 | Set IPv4 Configuration Type: ```DHCP``` 116 | 117 | **DHCP client configuration** 118 | 119 | Set Configuration Mode: ```Advanced``` 120 | 121 | Set Override MTU: ```True``` 122 | 123 | Set Lease Requirements / Send Options: ```dhcp-class-identifier "IPTV_RG"``` 124 | 125 | Set Lease Requirements / Request Options: ```subnet-mask, routers, broadcast-address, classless-routes``` 126 | 127 | ### Step. 6 128 | 129 | Go to 130 | 131 | ``` 132 | System > Firmware > Plugins 133 | ``` 134 | 135 | ![Plugins](/images/kpn/opnsense-without-vlan/plugins.png) 136 | 137 | Install ```os-igmp-proxy``` 138 | 139 | After installation of ```os-igmp-proxy``` refresh the page. 140 | 141 | ### Step. 7 142 | 143 | Go to 144 | 145 | ``` 146 | Services > IGMP Proxy 147 | ``` 148 | 149 | ![IGMPproxy](/images/kpn/opnsense-without-vlan/igmpproxy.png) 150 | 151 | Here we are going to add 2 streams (Upstream and Downstream) 152 | 153 | **Add Upstream** 154 | 155 | Set Interface: ```IPTV_WAN``` 156 | 157 | Set Type: ```Upstream Interface``` 158 | 159 | Create 2 networks: ```0.0.0.0 / 1``` & ```128.0.0.0 / 1``` 160 | 161 | **Add Downstream** 162 | 163 | Set Interface: ```LAN``` 164 | 165 | Set Type: ```Downstream Interface``` 166 | 167 | Create 1 networks: ```192.168.2.0 / 24``` 168 | 169 | ### Step. 8 170 | 171 | Go to 172 | 173 | ``` 174 | Services > DHCPv4 175 | ``` 176 | 177 | ![DHCPv4](/images/kpn/opnsense-without-vlan/dhcp4.png) 178 | 179 | ![DHCPv4](/images/kpn/opnsense-without-vlan/dhcp4additional.png) 180 | 181 | Set Additional Options 182 | ``` 183 | 60 / Text / IPTV_RG 184 | ``` 185 | ``` 186 | 28 / IP address or host / 192.168.2.255 187 | ``` 188 | 189 | ### Step. 9 190 | 191 | Go to 192 | 193 | ``` 194 | Firewall > NAT > Outbound 195 | ``` 196 | 197 | ![FWNATOutbound](/images/kpn/opnsense-without-vlan/fwnatoutbound.png) 198 | 199 | Set Mode: ```Hybrid outbound NAT rule generation (automatically generated rules are applied after manual rules)``` 200 | 201 | ![FWNATOutboundRule](/images/kpn/opnsense-without-vlan/fwnatoutboundrule.png) 202 | 203 | Create Rule: ```IPTV_WAN LAN net * * * IPTV_WAN address * NO``` 204 | 205 | ### Step. 10 206 | 207 | Go to 208 | 209 | ``` 210 | Firewall > Rules > IPTV_WAN 211 | ``` 212 | ![FWIPTVWAN](/images/kpn/opnsense-without-vlan/fwiptvwan.png) 213 | 214 | Create 3 rules 215 | 216 | **Rule 1:** 217 | 218 | Set Action: ```Pass``` 219 | 220 | Set Quick: ```True``` 221 | 222 | Set Interface: ```IPTV_WAN``` 223 | 224 | Set Direction: ```in``` 225 | 226 | Set TCP/IP Version: ```IPv4``` 227 | 228 | Set Protocol: ```IGMP``` 229 | 230 | Set Source: ```any``` 231 | 232 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 233 | 234 | Set Advanced Option: ``Show`` 235 | 236 | Set allow options: ```True``` 237 | 238 | **Rule 2:** 239 | 240 | Set Action: ```Pass``` 241 | 242 | Set Quick: ```True``` 243 | 244 | Set Interface: ```IPTV_WAN``` 245 | 246 | Set Direction: ```out``` 247 | 248 | Set TCP/IP Version: ```IPv4``` 249 | 250 | Set Protocol: ```IGMP``` 251 | 252 | Set Source: ```any``` 253 | 254 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 255 | 256 | Set Advanced Option: ``Show`` 257 | 258 | Set allow options: ```True``` 259 | 260 | **Rule 3:** 261 | 262 | Set Action: ```Pass``` 263 | 264 | Set Quick: ```True``` 265 | 266 | Set Interface: ```IPTV_WAN``` 267 | 268 | Set Direction: ```in``` 269 | 270 | Set TCP/IP Version: ```IPv4``` 271 | 272 | Set Protocol: ```*``` 273 | 274 | Set Source: ```any``` 275 | 276 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 277 | 278 | ### Step. 11 279 | 280 | Go to 281 | 282 | ``` 283 | Firewall > Rules > LAN 284 | ``` 285 | 286 | ![FWLAN](/images/kpn/opnsense-without-vlan/fwlan.png) 287 | 288 | Create 2 rules at top of the exisiting ones. 289 | 290 | **Rule 1:** 291 | 292 | Set Action: ```Pass``` 293 | 294 | Set Quick: ```True``` 295 | 296 | Set Interface: ```LAN``` 297 | 298 | Set Direction: ```in``` 299 | 300 | Set TCP/IP Version: ```IPv4``` 301 | 302 | Set Protocol: ```IGMP``` 303 | 304 | Set Source: ```LAN net``` 305 | 306 | Set Destination: ```Single host or Network``` ```224.0.0.0 / 4``` 307 | 308 | Set Advanced Option: ``Show`` 309 | 310 | Set allow options: ```True``` 311 | 312 | **Rule 2:** 313 | 314 | Set Action: ```Pass``` 315 | 316 | Set Quick: ```True``` 317 | 318 | Set Interface: ```LAN``` 319 | 320 | Set Direction: ```in``` 321 | 322 | Set TCP/IP Version: ```IPv4``` 323 | 324 | Set Protocol: ```any``` 325 | 326 | Set Source: ```LAN net``` 327 | 328 | Set Destination: ```Single host or Network``` ```213.75.112.0 / 21``` 329 | -------------------------------------------------------------------------------- /guides/opnsense/online.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - Online 3 | description: 4 | published: true 5 | date: 2023-04-22T14:54:42.438Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T14:40:38.692Z 9 | --- 10 | 11 | # Provider: Online - online.nl 12 | 13 | It's a nice idea when your provider has the knowledge and experience to let you enjoy everything the internet has to offer without worry. Online.nl is one of the first providers in the Netherlands. We have been around since 1994, back then under the name Euronet. Together with other pioneers, we connected the Netherlands to the web and we were even the very first provider to sell internet access in shops. 14 | 15 | Our 1994 installation manual stated: 'The internet is expected to develop into the communication tool of the future.' Now, almost 30 years later, we work, learn, play and create online. We shop, talk and meet online. We watch our TV series and movies online. The internet has become not just the means of communication, but a necessity of life. For everyone, from young to old. 16 | 17 | We have been providing reliable and affordable internet services since 1994 and our professional staff are ready to help you. With us, you get it all as standard: with fibre-optic internet, low-cost call rates and interactive TV from Canal Digitaal. With more than 80 TV channels, CANAL+ Films & Series and Film1 as standard in your TV package. We offer 100% installation guarantee, free switching service, a free WiFi modem and much more. With no hidden costs and no worries. 18 | 19 | We have never lost our pioneering spirit. Thus, together with our partner Canal Digitaal, we are still at the forefront of the interactive television revolution and we believe that fast internet and affordable calling should be available to everyone. We work with the latest technology, such as fibre optics, and we challenge the market by offering just a bit more for the same money. 20 | 21 | We can no longer imagine a world without internet. Yet this is only the beginning. As in 1994, we dare to predict that it will become much bigger than it already is. That everything will be connected to everything. From our cities, roads, houses and cars to our refrigerators, doorbells and clothes. We work online, we learn online and even for our health we increasingly rely on the internet. In short: the future is online, just like us. 22 | 23 | ![online.png](/images/site/online.png) -------------------------------------------------------------------------------- /guides/opnsense/online/opnsense-internet-only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: OPNsense internet only 3 | description: OPNsense internet only with Online 4 | published: true 5 | date: 2023-04-23T15:54:56.595Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-22T14:37:56.205Z 9 | --- 10 | 11 | # How to Setup Online.nl on OPNsense [Internet only] 12 | 13 | In this How-To we are going to setup Online.nl on OPNsense 14 | 15 | ### Step. 1 16 | 17 | Go to 18 | 19 | ``` 20 | Interfaces > Other Types > VLAN 21 | ``` 22 | 23 | ![VLANs](/images/online/opnsense-internet-only/iface_other_vlan.png) 24 | 25 | Create VLAN 1001 on your WAN interface and press Save. 26 | 27 | ### Step. 2 28 | Go to 29 | 30 | ``` 31 | Interfaces > Assignments 32 | ``` 33 | 34 | ![Assignments](/images/online/opnsense-internet-only/iface_assignments.png) 35 | 36 | Change the WAN interface to ```Parent: [wan-interface], Tag: 1001``` 37 | 38 | And press Save. 39 | 40 | ### Step. 3 41 | Go to 42 | 43 | ``` 44 | Interfaces > WAN 45 | ``` 46 | 47 | ![InterfaceWAN](/images/online/opnsense-internet-only/iface_wan.png) 48 | 49 | **Generic configuration** 50 | 51 | Set IPv4 Configuration Type: ```DHCP``` 52 | 53 | Set IPv6 Configuration Type: ```DHCPv6``` 54 | Or None. So far i have not seen IPv6 on this connection. 55 | 56 | Finish these settings my pressing save. 57 | 58 | ### Step. 4 59 | If you go back to: 60 | ``` 61 | Lobby > Dashboard 62 | ``` 63 | 64 | ![Gateway](/images/online/opnsense-internet-only/gateway.png) 65 | 66 | You should see that the gateway should be up. 67 | Next thing to do.... Go fast! -------------------------------------------------------------------------------- /guides/pfsense.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Router - pfSense 3 | description: Information about pfSense 4 | published: true 5 | date: 2023-04-16T19:08:30.389Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T16:56:15.123Z 9 | --- 10 | 11 | # Router - pfSense - pfsense.org 12 | 13 | pfSense is a firewall/router computer software distribution based on FreeBSD. The open source pfSense Community Edition (CE) and pfSense Plus is installed on a physical computer or a virtual machine to make a dedicated firewall/router for a network. It can be configured and upgraded through a web-based interface, and requires no knowledge of the underlying FreeBSD system to manage. 14 | 15 | ## History 16 | The pfSense project began in 2004 as a fork of the m0n0wall project by Chris Buechler and Scott Ullrich. Its first release was in October 2006. The name derives from the fact that the software uses the packet-filtering tool, PF. 17 | 18 | Notable functions of pfSense include traffic shaping, VPNs using IPsec or PPTP, captive portal, stateful firewall, network address translation, 802.1q support for VLANs, and dynamic DNS.[9] pfSense can be installed on hardware with an x86-64 processor architecture. It can also be installed on embedded hardware using Compact Flash or SD cards, or as a virtual machine. 19 | 20 | WireGuard protocol support 21 | In February 2021, pfSense CE 2.5.0 and pfSense Plus 21.02 added support for a kernel WireGuard implementation. Support for WireGuard was temporarily removed in March 2021 after implementation issues were discovered by WireGuard founder Jason Donenfeld.The July 2021 release of pfSense CE 2.5.2 version re-included WireGuard. 22 | 23 | ![dashboard_pfsense_2.6.0.jpg](/images/site/dashboard_pfsense_2.6.0.jpg) -------------------------------------------------------------------------------- /guides/pfsense/kpn.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Provider - KPN 3 | description: 4 | published: true 5 | date: 2023-04-16T18:54:57.507Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T16:55:24.881Z 9 | --- 10 | 11 | # Provider: KPN - kpn.com 12 | 13 | KPN is a leading telecommunications and IT provider and market leader in the Netherlands. With our fixed and mobile networks for telephony, data and television, we serve customers at home and abroad. KPN targets both private customers and business users, from small to large. 14 | 15 | ![kpn.jpg](/images/site/kpn.jpg) -------------------------------------------------------------------------------- /guides/pfsense/kpn/pfSense-ipv6.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: KPN IPv6 pfSense 3 | description: How to Setup KPN IPv6 in pfSense 4 | published: true 5 | date: 2023-04-23T15:58:28.501Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T17:17:42.919Z 9 | --- 10 | 11 | # How to Setup KPN IPv6 in pfSense 12 | 13 | In this How-To we are going to setup IPv6 for KPN in pfSense 14 | 15 | ### Step. 1 16 | 17 | In order to do this follow you should have followed one of the pfSense guides about Internet & iTV 18 | 19 | * [pfSense without seperate TV VLAN](/guides/pfsense/kpn/pfSense-without-vlan.md) 20 | * [pfSense with seperate TV VLAN](/guides/pfsense/kpn/pfSense-with-vlan.md) 21 | 22 | Go to 23 | 24 | ``` 25 | Interface > WAN 26 | ``` 27 | ![interfaceWAN](/images/kpn/pfsense-ipv6/interfacewan.png) 28 | 29 | ![InterfaceWanPPPoE](/images/kpn/pfsense-ipv6/interfacewan_pppoe.png) 30 | 31 | Make sure the MTU size is set to 1500 and the MSS is set to 1492. 32 | 33 | 34 | ![ipv6configtype](/images/kpn/pfsense-ipv6/ipv6configtype.png) 35 | 36 | Set IPv6 Configuration Type: ```DHCP6``` 37 | 38 | ![dhcp6clientconfiguration](/images/kpn/pfsense-ipv6/dhcp6clientconfiguration.png) 39 | 40 | Set Use IPv4 connectivity as parent interface: ```True``` 41 | 42 | Set Request only an IPv6 prefix: ```True``` 43 | 44 | Set DHCPv6 Prefix Delegation size: ```48``` 45 | 46 | Set Send IPv6 prefix hint: ```True``` 47 | 48 | Set Do not wait for a RA: ```True``` 49 | 50 | ### Step. 2 51 | 52 | Go to 53 | 54 | ``` 55 | Interface > LAN 56 | ``` 57 | 58 | ![interfacelan](/images/kpn/pfsense-ipv6/interfacelan.png) 59 | 60 | ![ipv6configtypelan](/images/kpn/pfsense-ipv6/ipv6configtypelan.png) 61 | 62 | Set IPv6 Configuration Type: ```Track Interface``` 63 | 64 | ![trackipv6interface](/images/kpn/pfsense-ipv6/trackipv6interface.png) 65 | 66 | Set IPv6 Interface: ```WAN``` 67 | 68 | Set IPv6 Prefix ID: ```1``` (* can be something between (hexadecimal from 0 to ffff)) 69 | 70 | ### Step. 3 71 | 72 | Go to 73 | 74 | ``` 75 | Services > DHCPv6 & RA 76 | ``` 77 | 78 | Go to tab 79 | ``` 80 | LAN > DHCPv6 Server 81 | ``` 82 | 83 | ![dhcpv6server](/images/kpn/pfsense-ipv6/dhcpv6serverv2.png) 84 | 85 | Set DHCPv6 Server: ```True``` 86 | 87 | Set Range: ```::1000 / ::2000``` 88 | 89 | Set Prefix Delegation Size: ```56``` 90 | 91 | Go to tab 92 | ``` 93 | LAN > Router Advertisements 94 | ``` 95 | 96 | ![dhcpv6ra](/images/kpn/pfsense-ipv6/dhcpv6ra.png) 97 | 98 | Set Router mode: ```Assisted - RA Flags [managed, other stateful], Prefix Flags [onlink, auto, router]``` 99 | 100 | ### Step. 4 101 | 102 | Go to 103 | 104 | ``` 105 | Firewall > Rules > WAN 106 | ``` 107 | 108 | ![fwwan](/images/kpn/pfsense-ipv6/fwwan.png) 109 | 110 | ![fwwanicmp4](/images/kpn/pfsense-ipv6/fwwanicmp4.png) 111 | 112 | IPv4 ICMP 113 | 114 | Set Address Family: ```IPv4``` 115 | 116 | Set Protocol: ```ICMP``` 117 | 118 | Set ICMP Subtypes: ```Echo request``` 119 | 120 | Set Source: ```any``` 121 | 122 | Set Destination: ```any``` 123 | 124 | ![fwwanlinklocal](/images/kpn/pfsense-ipv6/fwwanlinklocal.png) 125 | 126 | IPv6 Link-Local 127 | 128 | Set Address Family: ```IPv6``` 129 | 130 | Set Protocol: ```UDP``` 131 | 132 | Set Source: ```Network``` ```fe80::/10``` 133 | 134 | Set Destination: ```Any``` 135 | 136 | Set Destination Port Range: ```Any``` ```Any``` 137 | 138 | ![fwwanicmp6](/images/kpn/pfsense-ipv6/fwwanicmp.png) 139 | 140 | IPv6 ICMP 141 | 142 | Set Address Family: ```IPv6``` 143 | 144 | Set Protocol: ```ICMP``` 145 | 146 | Set ICMP Subtypes: ```Echo request``` 147 | 148 | Set Source: ```any``` 149 | 150 | Set Destination: ```any``` 151 | 152 | ### Step. 5 153 | 154 | ``` 155 | Firewall > Rules > LAN 156 | ``` 157 | 158 | ![fwlan](/images/kpn/pfsense-ipv6/fwlan.png) 159 | 160 | ![fwlanicmp4](/images/kpn/pfsense-ipv6/fwlanicmp4.png) 161 | 162 | IPv4 ICMP 163 | 164 | Set Address Family: ```IPv4``` 165 | 166 | Set Protocol: ```ICMP``` 167 | 168 | Set ICMP Subtypes: ```Echo request``` 169 | 170 | Set Source: ```LAN net``` 171 | 172 | Set Destination: ```any``` 173 | 174 | ![fwlanicmp6](/images/kpn/pfsense-ipv6/fwlanicmp6.png) 175 | 176 | IPv6 ICMP 177 | 178 | Set Address Family: ```IPv6``` 179 | 180 | Set Protocol: ```ICMP``` 181 | 182 | Set ICMP Subtypes: ```Echo request``` 183 | 184 | Set Source: ```LAN net``` 185 | 186 | Set Destination: ```any``` 187 | 188 | ### Step. 6 189 | 190 | Reboot your router now! 191 | 192 | Go to 193 | 194 | ``` 195 | Diagnostics > Reboot 196 | ``` 197 | 198 | ### Step. 7 199 | 200 | Now IPv6 should be configured for your pfSense. 201 | 202 | You can check if its working at one of the following sites. 203 | 204 | * [ipv6-test.com](https://ipv6-test.com/) 205 | * [test-ipv6.com](https://test-ipv6.com/) 206 | * [ipv6test.google.com](https://ipv6test.google.com/) 207 | 208 | ![ipv6testcom](/images/kpn/pfsense-ipv6/ipv6test.png) 209 | 210 | If you are getting 18/20 and ICMP says filtered on ipv6-test.com try to visit it on your mobile. 211 | 212 | Windows Defender Firewall is the issue, you can disable Windows Defender Firewall to test it. 213 | 214 | ``` 215 | But we don't recommend to keep your Windows Defender Firewall disabled!!! 216 | ``` -------------------------------------------------------------------------------- /guides/pfsense/kpn/pfSense-with-vlan.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: KPN with seperate TV VLAN 3 | description: How to Setup KPN on pfSense with seperate TV VLAN 4 | published: true 5 | date: 2024-01-04T17:37:06.394Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T16:46:07.042Z 9 | --- 10 | 11 | # How to Setup KPN on pfSense with seperate TV VLAN 12 | 13 | In this How-To we are going to use ```VLAN89``` as our seperate TV VLAN, you can choose to use your own VLAN number. 14 | 15 | ### Step. 1 16 | 17 | After install pfSense go to 18 | 19 | ``` 20 | Interface > Assignments > VLANs 21 | ``` 22 | 23 | ![vlan](/images/kpn/pfsense-with-vlan/interfacevlans.png) 24 | 25 | Create 2 VLANs on your WAN interface: 26 | ```VLAN6``` 27 | ```VLAN4``` 28 | 29 | Create 1 VLAN on your LAN interface: 30 | ```VLAN89``` 31 | 32 | ### Step. 2 33 | 34 | Go to 35 | 36 | ``` 37 | Interface > Assignments > PPPs 38 | ``` 39 | 40 | Add a new interface and link it with your WAN port 41 | 42 | ![ppps](/images/kpn/pfsense-with-vlan/ppp.png) 43 | 44 | Username 45 | ```kpn@internet``` 46 | 47 | Password 48 | ```kpn``` 49 | 50 | ### Step. 3 51 | 52 | Go to 53 | 54 | ``` 55 | Interface > Assignments 56 | ``` 57 | 58 | ![interfaces](/images/kpn/pfsense-with-vlan/interfaces.png) 59 | 60 | Set Interface WAN to PPPOE0 61 | 62 | Add ```VLAN4``` for ```IPTV_WAN``` 63 | 64 | Add ```VLAN89``` for ```IPTV_VLAN89 ``` 65 | 66 | ### Step. 4 67 | 68 | Edit Interface IPTV_WAN 69 | 70 | ![vlan89_1](/images/kpn/pfsense-with-vlan/leaserequirementsandrequests.png) 71 | 72 | Set Send options: 73 | ``` 74 | dhcp-class-identifier "IPTV_RG" 75 | ``` 76 | 77 | Set Request options: 78 | ``` 79 | subnet-mask, routers, broadcast-address, classless-routes 80 | ``` 81 | 82 | ### Step. 5 83 | 84 | Edit Interface IPTV_VLAN89 85 | 86 | ![vlan89_1](/images/kpn/pfsense-with-vlan/interfacevlaniptv.png) 87 | 88 | IPv4 Configuration Type: 89 | ```Static IPv4``` 90 | 91 | IPv4 Address: 92 | ```192.168.89.1``` 93 | 94 | ### Step. 6 95 | 96 | Go to 97 | 98 | ``` 99 | Services > DHCP Server > IPTV_VLAN89 100 | ``` 101 | 102 | ![dhcpvlan89](/images/kpn/pfsense-with-vlan/dhcpiptvvlan.png) 103 | 104 | Set Range: 105 | ```192.168.89.10 / 192.168.89.245``` 106 | (*Or use your own range) 107 | 108 | ![dhcpvlan89dns](/images/kpn/pfsense-with-vlan/dhcpiptvvlandns.png) 109 | 110 | Set DNS Servers: 111 | ```195.121.1.34``` 112 | ```195.121.1.66``` 113 | 114 | ![dhcpvlan89other](/images/kpn/pfsense-with-vlan/dhcpiptvvlanother.png) 115 | 116 | Set Domain name: 117 | ```kpn.home``` 118 | 119 | ![dhcpvlan89bootp](/images/kpn/pfsense-with-vlan/dhcpiptvvlanbootp.png) 120 | 121 | Set BOOTP/DHCP Options 122 | ``` 123 | 60 / Text / IPTV_RG 124 | ``` 125 | ``` 126 | 28 / IP address or host / 192.168.89.255 127 | ``` 128 | 129 | ### Step. 7 130 | 131 | Go to 132 | 133 | ``` 134 | Services > IGMP Proxy 135 | ``` 136 | 137 | ![igmp](/images/kpn/pfsense-with-vlan/igmp.png) 138 | 139 | Here we are going to add 2 streams (Upstream and Downstream) 140 | 141 | ``` 142 | Add Upstream 143 | ``` 144 | 145 | Set Interface: ```IPTV_WAN``` 146 | 147 | Set Type: ```Upstream Interface``` 148 | 149 | Create 2 networks: ```0.0.0.0 / 1 ``` ```128.0.0.0 / 1``` 150 | 151 | 152 | 153 | ``` 154 | Add Downstream 155 | ``` 156 | Set Interface: ```IPTV_VLAN89``` 157 | 158 | Set Type: ```Downstream Interface``` 159 | 160 | Create 1 networks: ```192.168.89.0 / 24``` 161 | 162 | ### Step. 8 163 | 164 | Go to 165 | 166 | ``` 167 | Firewall > NAT > Outbound 168 | ``` 169 | 170 | ![natoutbound](/images/kpn/pfsense-with-vlan/natoutbound.png) 171 | 172 | Set to Hybrid Outbound NAT 173 | 174 | Create a Mapping 175 | 176 | ![natoutboundmapping](/images/kpn/pfsense-with-vlan/natoutboundmappings.png) 177 | 178 | ### Step. 9 179 | 180 | Go to 181 | 182 | ``` 183 | Firewall > Rules > IPTV_WAN 184 | ``` 185 | 186 | Add the following rules 187 | 188 | ![fwiptvwan](/images/kpn/pfsense-with-vlan/fwiptvwan.png) 189 | 190 | On the IPv4 IGMP rule enable the following line. 191 | 192 | ![allowipoptions](/images/kpn/pfsense-with-vlan/allowipoptions.png) 193 | 194 | ### Step. 10 195 | 196 | Go to 197 | 198 | ``` 199 | Firewall > Rules > IPTV_VLAN89 200 | ``` 201 | 202 | Add the following rules 203 | 204 | ![fwiptv89](/images/kpn/pfsense-with-vlan/fwiptvvlan.png) 205 | 206 | On the IPv4 IGMP rule enable the following line. 207 | 208 | ![allowipoptions](/images/kpn/pfsense-with-vlan/allowipoptions.png) -------------------------------------------------------------------------------- /guides/pfsense/kpn/pfSense-without-vlan.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: KPN without seperate TV VLAN 3 | description: How to Setup KPN on pfSense without a seperate TV VLAN 4 | published: true 5 | date: 2023-04-23T15:59:38.302Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-16T14:54:09.153Z 9 | --- 10 | 11 | # How to Setup KPN on pfSense without a seperate TV VLAN 12 | 13 | After installing pfSense go to: 14 | 15 | ``` 16 | Interface > Assignments > Vlans 17 | ``` 18 | ![vlans](/images/kpn/pfsense-without-vlan/vlans.png) 19 | 20 | Create 2 VLANs *vlan6* & *vlan4* on your WAN interface, then go to: 21 | 22 | ``` 23 | Interface > Assignments > PPP 24 | ``` 25 | 26 | Add a new interface and link it to you WAN port. 27 | 28 | ![PPP](/images/kpn/pfsense-without-vlan/ppp.png) 29 | 30 | Then go to: 31 | 32 | ``` 33 | Interface > Assignments 34 | ``` 35 | ![assignments](/images/kpn/pfsense-without-vlan/assignments.png) 36 | 37 | This is where you set your PPPOE interface as WAN. 38 | Set Lan as your lan interface and assign a new interface (Vlan4) to KPN tv 39 | 40 | Then go to: 41 | 42 | ``` 43 | Interface > TV_KPN 44 | ``` 45 | set this at _Send options_ 46 | ``` 47 | dhcp-class-identifier "IPTV_RG" 48 | ``` 49 | and set this at _Request options_ 50 | ``` 51 | subnet-mask,routers,classless-routes 52 | ``` 53 | 54 | Save the settings and go to: 55 | 56 | ``` 57 | Services > IGMP Proxy 58 | ``` 59 | 60 | ![igmpproxy](/images/kpn/pfsense-without-vlan/igmpproxy.png) 61 | 62 | Enable IGMP 63 | 64 | Add an upstream and downstream proxy. The upstream proxy takes the default route: 0.0.0.0/0 (or on pfSense: 0.0.0.0/1 , 128.0.0.0/1) 65 | Add your LAN network to the downstream proxy. 66 | 67 | Then go to: 68 | 69 | ``` 70 | Services > DHCP Server > LAN 71 | ``` 72 | 73 | Scroll to the bottom and open *Additional BOOTP/DHCP Options* 74 | and enter the following lines 75 | 76 | ![bootp](/images/kpn/pfsense-without-vlan/additional-bootp-dhcp.png) 77 | 78 | In this example is the broadcast adress 10.0.0.255 set here your own broadcast address 79 | 80 | Then go to: 81 | 82 | ``` 83 | Firewall > NAT > Outbound 84 | ``` 85 | 86 | ![bootp](/images/kpn/pfsense-without-vlan/outbound.png) 87 | 88 | And add the line above under mappings 89 | 90 | Then go to 91 | 92 | ``` 93 | Firewall > Rules > WAN 94 | ``` 95 | 96 | Add the following lines 97 | 98 | ![ruleswan](/images/kpn/pfsense-without-vlan/rules-wan.png) 99 | 100 | On the IPv4 IGMP rule enable the following line. 101 | _Allow IP options_ 102 | 103 | ![ipoptions](/images/kpn/pfsense-without-vlan/ipoptions.png) 104 | 105 | Then go to: 106 | 107 | ``` 108 | Firewall Rules LAN 109 | ``` 110 | 111 | and add the following lines 112 | 113 | ![fwlan](/images/kpn/pfsense-without-vlan/firewalllan.png) 114 | 115 | On the IPv4 IGMP rule _Allow IP options_ 116 | 117 | ![ipoptions](/images/kpn/pfsense-without-vlan/ipoptions.png) 118 | 119 | The _213.75.112.0/21_ is the ip/subnet from kpn itv 120 | 121 | Then go to: 122 | 123 | ``` 124 | Firewall > Rules > TV_KPN 125 | ``` 126 | 127 | And add the following lines 128 | 129 | ![tvkpn](/images/kpn/pfsense-without-vlan/tv_kpn.png) 130 | 131 | On the IPv4 IGMP rule _Allow IP options_ 132 | 133 | ![ipoptions](/images/kpn/pfsense-without-vlan/ipoptions.png) -------------------------------------------------------------------------------- /home.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: EIGENROUTER.NL 3 | description: Detailed how-to information about setting up Internet, IPTV & VoIP on your own router from different ISPs. 4 | published: true 5 | date: 2024-05-09T17:30:50.192Z 6 | tags: 7 | editor: markdown 8 | dateCreated: 2023-04-15T18:58:11.325Z 9 | --- 10 | 11 | # Welcome @ EIGENROUTER.NL 12 | 13 | Detailed how-to information about setting up Internet, IPTV & VoIP on your own router from different ISPs. 14 | We will update this website with more types of routers to become a central place to find information. 15 | If you have interest / knowledge in this area and want to help other people, leave a message for us so we can add you as a contributor! 16 | 17 | We started this project because we think everyone should be able to use their own router. 18 | Our goal is to create a central place for people to find router configurations and to keep it up-to-date with the latest changes. 19 | 20 | Currently, we already have guides ready for the following ISP's and Routers. 21 | 22 | ## Routers 23 | - pfSense 24 | - OPNsense 25 | - Mikrotik 26 | - Draytek 27 | 28 | ## ISP's 29 | - KPN 30 | - T-Mobile 31 | - Solcon 32 | - Ziggo 33 | - Online 34 | - Delta 35 | 36 | ## Work in progress 37 | - Ziggo (pfSense & OPNsense) 38 | 39 | 40 | --- 41 | The list of routers and ISP's will grow during time! 42 | Keep watching this website or visit our GitHub at https://github.com/Eigenrouter/eigenrouter 43 | 44 | ## Join us at Discord! 45 | 46 | Join our Discord server @ [https://discord.gg/jfwsQUgU9e](https://discord.gg/jfwsQUgU9e) -------------------------------------------------------------------------------- /images/kpn/draytek/fiber1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/fiber1.png -------------------------------------------------------------------------------- /images/kpn/draytek/fiber2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/fiber2.png -------------------------------------------------------------------------------- /images/kpn/draytek/igmp1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/igmp1.png -------------------------------------------------------------------------------- /images/kpn/draytek/igmp2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/igmp2.png -------------------------------------------------------------------------------- /images/kpn/draytek/igmp3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/igmp3.png -------------------------------------------------------------------------------- /images/kpn/draytek/image.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/image.png -------------------------------------------------------------------------------- /images/kpn/draytek/routed1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/routed1.png -------------------------------------------------------------------------------- /images/kpn/draytek/routed2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/routed2.png -------------------------------------------------------------------------------- /images/kpn/draytek/routed3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/routed3.png -------------------------------------------------------------------------------- /images/kpn/draytek/routed4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/routed4.png -------------------------------------------------------------------------------- /images/kpn/draytek/routed5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/routed5.png -------------------------------------------------------------------------------- /images/kpn/draytek/routediptvondersteuning.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/routediptvondersteuning.png -------------------------------------------------------------------------------- /images/kpn/draytek/vdsl1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/vdsl1.png -------------------------------------------------------------------------------- /images/kpn/draytek/vdsl2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/draytek/vdsl2.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/assignments.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/assignments.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/dhcp4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/dhcp4.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/dhcp4additional.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/dhcp4additional.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/dhcp4range.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/dhcp4range.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/fwiptvwan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/fwiptvwan.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/fwlan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/fwlan.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/fwnatoutbound.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/fwnatoutbound.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/fwnatoutboundrule.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/fwnatoutboundrule.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/fwupdate.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/fwupdate.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/igmpproxy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/igmpproxy.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/interfacelaniptv.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/interfacelaniptv.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/interfacewan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/interfacewan.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/interfacewaniptv.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/interfacewaniptv.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/plugins.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/plugins.png -------------------------------------------------------------------------------- /images/kpn/opnsense-with-vlan/vlans.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-with-vlan/vlans.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/assignments.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/assignments.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/dhcp4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/dhcp4.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/dhcp4additional.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/dhcp4additional.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/fwiptvwan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/fwiptvwan.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/fwlan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/fwlan.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/fwnatoutbound.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/fwnatoutbound.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/fwnatoutboundrule.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/fwnatoutboundrule.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/fwupdate.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/fwupdate.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/igmpproxy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/igmpproxy.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/interfacewan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/interfacewan.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/interfacewaniptv.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/interfacewaniptv.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/plugins.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/plugins.png -------------------------------------------------------------------------------- /images/kpn/opnsense-without-vlan/vlans.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/opnsense-without-vlan/vlans.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/dhcp6clientconfiguration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/dhcp6clientconfiguration.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/dhcpv6ra.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/dhcpv6ra.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/dhcpv6serverv2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/dhcpv6serverv2.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/fwlan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/fwlan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/fwlanicmp4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/fwlanicmp4.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/fwlanicmp6.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/fwlanicmp6.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/fwwan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/fwwan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/fwwanicmp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/fwwanicmp.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/fwwanicmp4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/fwwanicmp4.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/fwwanlinklocal.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/fwwanlinklocal.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/interfacelan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/interfacelan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/interfacewan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/interfacewan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/interfacewan_pppoe.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/interfacewan_pppoe.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/ipv6configtype.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/ipv6configtype.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/ipv6configtypelan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/ipv6configtypelan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/ipv6test.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/ipv6test.png -------------------------------------------------------------------------------- /images/kpn/pfsense-ipv6/trackipv6interface.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-ipv6/trackipv6interface.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/allowipoptions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/allowipoptions.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/dhcpiptvvlan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/dhcpiptvvlan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/dhcpiptvvlanbootp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/dhcpiptvvlanbootp.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/dhcpiptvvlandns.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/dhcpiptvvlandns.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/dhcpiptvvlanother.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/dhcpiptvvlanother.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/fwiptvvlan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/fwiptvvlan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/fwiptvwan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/fwiptvwan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/igmp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/igmp.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/interfaces.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/interfaces.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/interfacevlaniptv.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/interfacevlaniptv.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/interfacevlans.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/interfacevlans.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/leaserequirementsandrequests.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/leaserequirementsandrequests.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/natoutbound.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/natoutbound.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/natoutboundmappings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/natoutboundmappings.png -------------------------------------------------------------------------------- /images/kpn/pfsense-with-vlan/ppp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-with-vlan/ppp.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/additional-bootp-dhcp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/additional-bootp-dhcp.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/assignments.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/assignments.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/firewalllan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/firewalllan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/igmpproxy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/igmpproxy.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/ipoptions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/ipoptions.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/outbound.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/outbound.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/ppp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/ppp.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/rules-wan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/rules-wan.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/tv_kpn.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/tv_kpn.png -------------------------------------------------------------------------------- /images/kpn/pfsense-without-vlan/vlans.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/kpn/pfsense-without-vlan/vlans.png -------------------------------------------------------------------------------- /images/online/draytek-internet-only/online1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/online/draytek-internet-only/online1.png -------------------------------------------------------------------------------- /images/online/draytek-internet-only/online2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/online/draytek-internet-only/online2.png -------------------------------------------------------------------------------- /images/online/draytek-internet-only/online3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/online/draytek-internet-only/online3.png -------------------------------------------------------------------------------- /images/online/opnsense-internet-only/gateway.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/online/opnsense-internet-only/gateway.png -------------------------------------------------------------------------------- /images/online/opnsense-internet-only/iface_assignments.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/online/opnsense-internet-only/iface_assignments.png -------------------------------------------------------------------------------- /images/online/opnsense-internet-only/iface_other_vlan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/online/opnsense-internet-only/iface_other_vlan.png -------------------------------------------------------------------------------- /images/online/opnsense-internet-only/iface_wan.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/online/opnsense-internet-only/iface_wan.png -------------------------------------------------------------------------------- /images/site/121258543.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/121258543.png -------------------------------------------------------------------------------- /images/site/dark.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/dark.png -------------------------------------------------------------------------------- /images/site/dashboard_pfsense_2.6.0.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/dashboard_pfsense_2.6.0.jpg -------------------------------------------------------------------------------- /images/site/delta.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/delta.png -------------------------------------------------------------------------------- /images/site/draytek.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/draytek.png -------------------------------------------------------------------------------- /images/site/kpn.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/kpn.jpg -------------------------------------------------------------------------------- /images/site/mikrotik.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/mikrotik.png -------------------------------------------------------------------------------- /images/site/online.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/online.png -------------------------------------------------------------------------------- /images/site/opnsense_dashboard_v16_7b.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/opnsense_dashboard_v16_7b.png -------------------------------------------------------------------------------- /images/site/solcon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/solcon.png -------------------------------------------------------------------------------- /images/site/t-mobile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/t-mobile.png -------------------------------------------------------------------------------- /images/site/ziggo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/site/ziggo.jpg -------------------------------------------------------------------------------- /images/solcon/solcon1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/solcon/solcon1.png -------------------------------------------------------------------------------- /images/solcon/solcon2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/solcon/solcon2.png -------------------------------------------------------------------------------- /images/solcon/solcon3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/solcon/solcon3.png -------------------------------------------------------------------------------- /images/solcon/solcon4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/solcon/solcon4.png -------------------------------------------------------------------------------- /images/tmobile/tmobile1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/tmobile/tmobile1.png -------------------------------------------------------------------------------- /images/tmobile/tmobile2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Eigenrouter/eigenrouter/affa27f685a83843a7f51c0f1646cd0982b82eef/images/tmobile/tmobile2.png --------------------------------------------------------------------------------