Re: [44net] Virgin Media in the UK

Hi Steve, I must be one of the lucky one, I have virgin media fibre at 100MB and its been rock solid since it was installed several months ago. Same IP address as well, which does help mostly. I used the online chat from the web site into support, and again must have had a lucky break, the chap spoke to level 2 and 3 to confirm protocol 4 and ipencap were indeed blocked, Even had a laugh with me about trying to request my block of 44 IP's be routed direct by them. I have the super hub 2, everything is disabled fw, upstream adult and virus blocking, port forwarding etc. I had enabled ping (echo reply) and stuck the pi in the dmz. No cigar... I had set this up on BT before and it worked great! I have the raspberry pi in the DMZ and had done plenty of tcp dumps etc to test access and see what was happening out there. As Brain said solution was to create a VPN tunnel from his server to mine. You can test 44.131.176.33 is now up and running. Cheers James. -----Original Message----- From: 44Net [mailto:44net-bounces+j.preece=f5.com@hamradio.ucsd.edu] On Behalf Of Steve Platt Sent: 15 September 2015 14:31 To: 44net(a)hamradio.ucsd.edu Subject: Re: [44net] Virgin Media in the UK (Please trim inclusions from previous messages) _______________________________________________ On 15/09/15 08:23, John Wiseman wrote: Hi John, I think this illustrates more about ISPs' support services than anything else. In my experience contacting VM is slow, expensive and pointless. The support people know less than the tech people (which is precious little), even if you do get through. The answers you get are read off a sheet which simply lists their excuses for not caring a toss. Usually what you are doing is "not supported" and their main concern seems to be giving wild promises of upcoming speed increases in an attempt to retain customers. While the bulk of the ISP business is focussed on gaming and adult entertainment there is no business case for for providing technical fault reports or support calls in the way you get from a professional Internet connection. I think in this case they have confused what IP protocols their cable connection provides with what happens inside their provided "router". The modem/router I have (SuperHub 1?) runs a crippled version of the manufacturers firmware which has some deficiencies and disabled features, perhaps to make it easier to "support". One annoyance, eg, is that not all frames on the wired LAN ports are forwarded to the default wireless network. Most are, but not all. This breaks IPv6 connectivity unless your by-pass their "router". I do this with an old Access Point I had in the junk box but the cleaner solution is to turn off the VM router and use it as a modem-only, buying another router to provide the wired/wireless bridging you expect. I also wonder if the OP had put his IP/IP endpoint in the "DMZ" ... I assume this would be necessary since routers don't usually know how to NAT protocol 4? I had to do that for my IPv6 tunnel endpoint (a Raspberry Pi - hooray!) so I guess the same applies to an IP/IP endpoint? Thanks for the info John, good to hear 44-net is still alive in the UK! Steve G4WSZ _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net