cancel
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

Vodafone connect router DHCP settings

mattman
4: Newbie

I have posted this into off topic as I can not see any reference to Vodafone Home phone and Broadband.

I have install the router and all is working but there one thing that is missing from the setting of the VDSL router that being a function to turn off DHCP, I have for the pasted 10 year had my own network running at home with a fully working server that is my DHCP & DNS server but for the first time in history I have just sign up for 18 month and got a bloody router that has no function in the GUI settings pages to turn OFF the DHCP server. So for now I will have to wait for 18 months before I can change ISP. thanks vodafone tech team for missing this one. If there is anyone out there that can offer me a firmware update to give me the function to turn OFF DHCP then please post it.

 

602 REPLIES 602

cardiffjames
4: Newbie
There all full of 💩 Over at Vodafone there the worst service Iv ever seen and it is what we would expect of a kid with a bad attitude there connect router is fit for the bin and there mobile service is a joke do any one know what Vodafone can do well ??

mattman
4: Newbie

tamertheodossy
3: Seeker
3: Seeker
I thought so but wasn't sure if I was missing something. I looked through all the setup and you can't configure the wan port at all.

Any other suggestions other than having to cance VODAFONE broadband completely.

Thanks

tamertheodossy
3: Seeker
3: Seeker
I only have the HH5, I am still within my cooling off period with VODAFONE so realistically might just cancel and move back to BT. Cardiffjames- where did you get the gift card from? Thanks.

cjwalsh
3: Seeker
3: Seeker

+1 on the request for full control over the Vodafone Connect router's settings, as well as being able to discover the broadband login details and use a different router if desired (unsupported).

 

Not to give Voda an easy out, but I doubt it'd be quite as simple as giving us the login details. I know from experience of them screwing up my orginal order that the c onnection is keyed to the serial number of the modem that they use (it can be changed, but they seemed to have a faff doing so.)

 

They'd probably have to reengineer their software/systems to cope. Not sure they'd be willing to pay for it.

Makelo
12: Established
12: Established

It is absolutely that simple.

Many authentication methods have been used over the years, modern routers support all these methods in their latest firmware.

All it requires is Vodafone to release the information required and for the user to enter this information into the relevant section within their choice of router. Other than their terms and conditions, Vodafone do not need to implement any changes at all.

 

I understand why they do this, staff are trained to provide support to known equipment and a specific configuration only.  

That's fine, but rather than excluding you from using your own choice of equipment they could take the approach that they only provide support if you are using their equipment. If you use your own equipment they you are on your own, which I believe everyone would accept. In fact it would be unrealistic to expect anything other than that.

 

 

A normal home setup has changed, it used to be one shared computer connected directly to the internet. Anyone with a 'network' at home was considered a 'BillyNoMates' who stayed up all night, but this has all changed.

Many homes now have complex networks built up over a period of time, adding one device at a time and testing it works. The result is many different devices from many different manufacturers all connected and doing their thing. Media Streamers, Parental controls using DNS filtering, using DDNS so people can login to their CCTV, baby monitors, FTP server, OwnCloud, web server, the list is endless.

Vodafone, or anyone else for that matter, cannot test every possible combination and so cannot guarantee that their equipment will drop in to that network and cause no problems. The poor DLNA implementation of their router is one example of how to screw up someone's finely honed network. The fact it's taken three months and still counting to implement a fix for their dodgy DLNA server is disappointing to say the least.

 

Will Vodafone change this requirement to use their own router?    They should but they probably won't.

 

@Makelo

 

My thoughts exactly regarding the more sophisticated networks people have nowadays and the way they could offer support only for their own router.  I just hope that VF will listen to their customers (but I'm not holding my breath!)

 

If it is of any use to anyone, I found out that some of the various network problems I was having with my ProCurve switches since starting to use the Connect router might be caused by IGMP snooping (which was disabled on my previous router). However, streaming functions (Apple TV, Airplay etc) may benefit by having this enabled. Of course there is no way of knowing how this is configured on the Connect router. Here's some info on the subject,

http://routerguide.net/enable-igmp-snooping-on-or-off/

Cannodale, can i ask what issues you were having with your Procurve switches? I have a managed one in my home setup up and would like to know what to look out for. 

Hi jimborae

My knowledge of network topology is not great but

as far as I have managed to discover, it seems to be an issue with Multicast from the router (for IPTV etc) and IGMP snooping being set "on" as default on the ProCurve (managed) switch. The problem I had was that the multicast streams were not getting through the second switch on my network. There's some explanation from Cisco half way down this page,

 

https://networkengineering.stackexchange.com/questions/28301/inter-switch-igmp-on-a-vlan-with-two-sw...

 

 I realised I did not really need the ProCurve (it was just handy at the time!), so instead of trying to reconfigure it, I just substituted it for an unmanaged switch and things started working again.

So it wasn't really an issue with the Connect router, as such, but not being able to see what the router was doing didn't help when diagnosing the problem.

 

Hope this is of some use 🙂