Mikrotik RouterBoard RB3011-UIAS-RM with Vodafone cable modem

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Mikrotik RouterBoard RB3011-UIAS-RM with Vodafone cable modem

sooperdoopa

3 posts

Wannabe Geek

#211685 6-Apr-2017 22:13

I'm currently on Vodafone cable and have found the ISP supplied HG659 pretty unreliable, often requiring regular reboots so have purchased a Mikrotik RB3011-UIAS-RM but am having issues with obtaining a DHCP address from the Technicolor 4400 modem.

I've followed the guide for IPoE connections from this thread: http://www.geekzone.co.nz/forums.asp?forumid=66&topicid=206084

but for whatever reason, the router fails to obtain a WAN address.

Just wondering if anyone else has recently configured one of these routers with the 4400 modem and if there is anything that I am missing?

I'm going a bit crazy here as have been working on it all day without any success.

Help! :)

michaelmurfy

meow
13580 posts

Uber Geek
+1 received by user: 10912

Moderator

ID Verified

Trusted

Lifetime subscriber

#1757854 6-Apr-2017 23:06

You need to add the VLAN for Vodafone FibreX - I think I missed this (don't use cable so was only really focusing on UFB). Essentially follow through the VLAN stuff but instead of putting PPPoE as the interface type, put your Ethernet port connected to the Technicolour modem.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

sooperdoopa

3 posts

Wannabe Geek

#1757865 6-Apr-2017 23:47

Hey thanks for the reply.

Yep, port 1 is configured to vlan 10 and also tried setting to P1 through the firewall mangle config.

sooperdoopa

3 posts

Wannabe Geek

#1758006 7-Apr-2017 10:25

Okay, got it working in the end.

Vodafone originally advised that I need to set the router to DHCP as the Technicolor still supplies the "static" WAN address via DHCP.

It turns out that information was wrong and specifying the static IP on the Mikrotik has resolved the issue.

Pretty sure I tried all combinations of configurations yesterday but I must have missed something somewhere. I blame the weather