I am new to the OpenWRT world and I would like to ask the community for some help.
I do have very limited knowledge of IT (I can connect to the router of SSH and I can run basic commands on it), just so you know how to approach me
So, here is my situation. I live in Germany and I do have M-NET as an ISP. They do provide their own Fritzbox router with their own custom firmware which is driving me nuts... So I thought I can give OpenWRT a try, maybe I can make the WAN connection working.
I purchased a GL-S1300 router which comes with OpenWRT installed by default. https://www.gl-inet.com/products/gl-s1300/
For the last 2 days, I am trying to make my WAN connection to work without success.
According to the M-NET forum posts (in german) https://forum.m-net.de/viewtopic.php?f=23&t=12865&sid=65dafede4f70dfa6326f25100ea4cc94 this connection should work.
I have IPV6 DualStack with the VLAN ID: 40.
Somehow I believe I am not doing something right with the VLAN IDs - as I said I am not an expert on the topic.
Any help which leads to solving this frustrating issue will be rewarded with
The router has OpenWrt Chaos Calmer 15.05.1 r48067
And when I try to connect to the WAN PPPOE I get the following error:
Sun Apr 26 13:34:27 2020 daemon.warn pppd: Timeout waiting for PADO packets
Sun Apr 26 13:34:27 2020 daemon.err pppd: Unable to complete PPPoE Discovery
Sun Apr 26 13:34:27 2020 daemon.info pppd: Exit.
Sun Apr 26 13:34:27 2020 daemon.notice netifd: Interface 'wan' is now down
Sun Apr 26 13:34:27 2020 daemon.notice netifd: Interface 'wan' is setting up now
Sun Apr 26 13:34:27 2020 daemon.info pppd: Plugin rp-pppoe.so loaded.
Sun Apr 26 13:34:27 2020 daemon.info pppd: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
I tried to debug a bit and here are some extra information:
so I guess I will pack the GL.iNet router and back to Amazon
lucky I can return it within 30 days with no questions asked.
Now, I would still like to buy another router which supports OpenWrt.
Here are my requirements, maybe you can recommend me something.
I have my wifi running on EERO in bridge mode - is doing a pretty good job as a mesh network and I am not planning to change it.
I need a router which can handle a VPN Server / client - I want to do this so that some devices on my network (e.g. the smart TV) will go through the VPN to US or UK. This was one of the reasons why I selected GL.iNet - the ease of running a VPN.
I was indeed considering using Fritxbox 4040 also with openWRT (as some of you suggested) but from what I read on the AVM forums they have an issue with VPN server/client because of the fritzbox hardware?(maybe) https://vpn-anbieter-vergleich-test.de/fritzbox-mit-vpn-verbinden/ But I believe I will give it a try to see if I can make it work.
VPN doesn't have to do with hardware. Only the hardware crypto acceleration part could boost the throughput.
I think what they say is that the protocols some VPN providers use is not supported by the stock firmware.
OpenWrt supports a lot of different protocols (almost all I can think of).
I have to admit I have no idea what I am doing here with the VLAN ID... so have mercy
I am trying to follow the instructions here: https://openwrt.org/toh/avm/avm_fritz_box_4040
If I apply these settings it means that I will have to connect WAN Cable to LAN1? And I can use LAN2 or 3 on the Fritzbox to connect my switch?
Since packets to the ISP need to be tagged, you would set LAN1 tagged in VLAN 40. VLAN 40 contains only the CPU and the ISP, both tagged. The LAN1 port should be off in the other VLAN(s) since it is for the WAN only.
The default is to untag eth0 and use it only for LAN, you need to change that so it is tagged for LAN (in VLAN x, where x is something other than 40, and probably should not be 1 or 2) as well as WAN on VLAN 40.
That requires changing the LAN physical interface to eth0.x Also set the wan network physical interface to eth0.40. No interfaces should be attached to plain eth0.
It is good to log in by wifi while doing this, so that if the Ethernet is misconfigured you still have control.
To use the now unused eth1 port as an extra LAN connection, bring it into the lan network bridge.