Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 11 subscribers
  • Views 27109 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Virgin Media and UTM - no internet

bobcatbird

Hi,

I've got a customer who has Virgin Media Superfast connection using their Superhub 3 router. I've switched this to modem mode, plugged in a laptop and can access the internet absolutely fine. If I connect the SG125 UTM, eth1 and set it as ethernet connection with a dynamic IP, the link/connection shows UP, I get a dynamic IP but cant access anything on the internet, cant even ping 8.8.8.8.

I've set many UTMs so have done the basics of masq rule, dns and know this isnt a simple fix.

So to cut a long story short, it seems other people have the same issue when using Cisco routers with Virgin. The solution is to clear the broadcast flag on the NIC that connects to the Virgin Media router with this command

"ip dhcp client broadcast-flag clear"

or disable broadcast flag on the NIC

My question is, how can this be done on the UTM, if it can? I've done some googling and trawling through these forums but not found anything

Many thanks in advance

 

 



This thread was automatically locked due to age.
Parents
  • 0

    It's been a long time since I was on VM (one of the first users when it was NTL)

    I know then it was mac related. Have you tried rebooting the hub AFTER the UTM is plugged in?

    You can also mimic the MAC Address under the hardware tab if needed.

  • 0 in reply to Louis-M

    Hi,

    Thanks for your response Louis-M.

     

    I've tried rebooting the hub after the UTM has been plugged in and no joy

    I read about the mac and tried the VM router's mac address in eth1 interface virtual MAC and didnt make a difference BUT I didn't reboot either boxes after making that change.

    Its really odd though as its clearly getting an IP address and connecting but in the system logs I see "dns-resolver[4494]: DNS server failed to contact!" even though in the DNS forwarder its picking up VM's DNS. I've tried unticking the forwards from ISP and putting Google, no joy and tried OpenDNS, no joy, have the same errors in system log. 

    What puzzles me is I can plug in a laptop and it works straight away without spoofing the Mac or anything so there is definitely something about how advanced firewalls like Cisco, Watchguard and Sophos UTM handle this.

Reply
  • 0 in reply to Louis-M

    Hi,

    Thanks for your response Louis-M.

     

    I've tried rebooting the hub after the UTM has been plugged in and no joy

    I read about the mac and tried the VM router's mac address in eth1 interface virtual MAC and didnt make a difference BUT I didn't reboot either boxes after making that change.

    Its really odd though as its clearly getting an IP address and connecting but in the system logs I see "dns-resolver[4494]: DNS server failed to contact!" even though in the DNS forwarder its picking up VM's DNS. I've tried unticking the forwards from ISP and putting Google, no joy and tried OpenDNS, no joy, have the same errors in system log. 

    What puzzles me is I can plug in a laptop and it works straight away without spoofing the Mac or anything so there is definitely something about how advanced firewalls like Cisco, Watchguard and Sophos UTM handle this.

Children