I want to connect Turris as my main box and remove my provider box.
I have done all the homework to find the hidden value that I needed , username and password were sniffed too.
Then I have been following a post in Cz but currently it still does not work.
It looks like this:
Just combine these two interfaces (the pppoe-one and WAN) and it should work - why did you divide them?
Regarding your homework - VLAN-ID 80 is correct for your ISP?
I did it this way because I tried to follow this post (but i am following in a foggy nightâŚ)
At first I did only one (but with wrong login pw), and I did not know how to set VLAN either.
VLAN settings was in clear in the hidden menu of ISP router, so I think I am fine. I tried to confirm in the sniffing capture but I did not find it.
Canât tell why they chose two interfaces in one firewall zone - because when bridging them anyways you can also just create one single interface.
Just try and remove the pppoe-interface and enter the VLAN and credentials directly to your WAN.
Try deleting the terminator-pppoe interface and (much more important!) move WAN interface to WAN firewall zone
ps: doing that stuff is much more easy via ssh (if you are familiar to this, please show the output of âvi /etc/config/networkâ).
Yes, it definitely has
But it depends on your TurrisOS version. With TOS v5.x and later it has to be eth2.80, not eth1.80. Please do a
cat /etc/turris-version
via ssh to see what version you are using to be sure.
As a short explanation: eth0, eth1 and eth2 represent the physical ethernet interfaces on your TO. To create a VLAN on an interface, you append a â.[VLAN-ID]â to the respective physical interface.
For the firewall: assign interface WAN to the firewall zone WAN.
Then I have tried eth2.80 and eth0.80 (and eth1.80). Some reboots. It is strange like one blink max to the wan port, is it even trying? I have also done a reboot to the âponâ.
If my VLAN is wrong (but damn it was in the super hidden settings), is there some kind of script to check vlan like 0 to 100?
I am feeling that there is only one more hiccup to fixâŚ
Yes, please update to latest TurrisOS version.
To do that run
pkgupdate
from ssh. Unfortunately I cannot help with the VLAN-ID, because that is completely up to your ISP (but one ISP will normally only use a single ID) and thereâs no automatic way of trying that.
Maybe reset everything and start from scratch (but this time Iâd clearly recommend only using ssh to change the values), itâs normally very small things one misses.
The good part is that I am starting to better understand the ssh and other things but I am still extremely weak.
The auto update is failing to download and it gets me crazy as the url is perfectly fine. May be it is trying to download through wan??? Why doesnt it work from the lan port?
And so far no luck as to force an offline update.
Well I have found something interesting. After an hard reset and offline my isp box shows vlan80. But in normal use with sniffed admin password it is vlan100. So be it!
Eth0.100 get my WAN to connect! Hurray! I can ping 8.8.8.8 but I canât ping google so I guess I have at least a DNS issue.
Well in the end nothing much in common with the terminator setup. I have a fiber contract of symmetric 100mb. And I am doing 120/120mb before and after. I have heard that the upload might jump (to 600) but it didnât. I have tidied up the hardware setup, it is looking better but still not the best place for the wifi spot. But thatâs a good feeling anyway having it the way I wanted.