Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 2737 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

ASG Vmware Cable modem OH MY!

adamss
ASG Firmware version:  7.507  HOME img on vmware.
  eth0  Lan  192.168.0.0/16
  eth1 DSL WAN
  eth2 Cable Wan

Vmware 4.0 vsphere/esx
    eth0  Lan 192.168.0.0/16 -- switch 2950-port23
    eth1 trunked to switch 2950-port 24

ATT DSL  modem.  
Comcast cable modem model sb5120
Cisco switches (3750 24 port and 2950)

ASG is running as a gust vm on my esx 4 server. I have a port trunked to my switch int he garage (2950). This interface is ued for all vlans). I have 2 vlans created.  Vlan 7 Edge and Vlan8 Comcast.  
Vlan 7 is used for dsl
Vlan 8 is used for comcast cable.

Now the dsl part works perfect.  The reason for the vlans is that the server currently has only 2 interfaces. 1 interface is ued for management and iscsi. The other is for all vlans. So i can have vm on any network in my house. 

Dsl modem plugged into --- 3750-24 port24----Core 3750----garage 2950---esx4 srver with vms.

Cable modem plugged into -----3750-24 port23----Core 3750---Garage 2950---esx4 server with vms.

Dsl works great. But when I try to use the cable modem it will not connect using the cable wan interface (eth2). So as a test I took the dsl modem and connected it to port23 to see if that works (on same vlan with asg eth2). Still doesn't work. I have both wan interface in asg configured the same.  CLI on asg see eth1 and eth2

it appears when I try to use the eth2 link as anything (dsl or cable) it doesn't work. Vmware see the interface in vm settings. Asg has it added to interfaces as eth2. 
But pppoe never shows anything in logs ecept 

 Filter:  
  Autoscroll 
2010:10:26-17:20:54 fw1 pppoe[9368]: recv (receivePacket): Network is down 
2010:10:26-17:20:59 fw1 pppoe[9368]: Timeout waiting for PADO packets 
2010:10:26-17:22:49 fw1 pppoe[9589]: Timeout waiting for PADO packets 
2010:10:26-17:22:49 fw1 pppoe-sh: Can not connect DSL AC - retry in 5 seconds 
2010:10:26-17:23:09 fw1 pppoe[9630]: Timeout waiting for PADO packets 

Any help would be appreciated.  My goal is to get rid of DSL and use cable because i have higher bandwidth needs. 

Could it be since i have the home virtual appliance i can only have 2 nics? 3rd doesn't work. I cannot bind and ip or anything to it.
What logs would show network card info. I am tried putting the dsl modem on this interface and didn't work. 

UPDATE:
 I configured eth1 for cable modem and it linked but I could not get an ip address.. it was down up on network card info page.
any ideas?


Shawn


This thread was automatically locked due to age.
Parents
  • 0
    Hi, Shawn, and welcome to the User BB!

    I don't know enough about VMWare to comment on it, but it should be easy to compare your configs for the two interfaces in Astaro.

    None of the cable modems I've touched in various family locations (OK, TX, CO, CN, FL) used PPPoE, so you might check on that; I'd think you'd want to use the "Standard ethernet" selection for your cable modem.

    If you decide to replace the eth2 NIC, you will want to choose an identical one - Astaro OS is not plug-n-play, and a reload from ISO is needed if you want to add a different piece of hardware.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    I have the same trouble. Sophos does NOT like to get an IP from cable modems when the modem is plugged into a switch on an access port and that VLAN is then trunked. I can usually play around with the modem and eventually get it to work but it is VERY cumbersome and annoying. Usually takes several reboots of the modem.

    The modem and virtualized (on ESXi) Sophos WAN link are the only connections on that VLAN.

    Sometimes, when it's really bad, I have to plug the modem into a PC, get the IP info, enter that in Sophos as static and save. Interface will then come up, but it will fail to route for some reason. I can then set back to DHCP, and it will get the proper IP. Still won't route though. Finish up by powering off modem for 60sec. Then all will work.

Reply
  • 0 in reply to BAlfson

    I have the same trouble. Sophos does NOT like to get an IP from cable modems when the modem is plugged into a switch on an access port and that VLAN is then trunked. I can usually play around with the modem and eventually get it to work but it is VERY cumbersome and annoying. Usually takes several reboots of the modem.

    The modem and virtualized (on ESXi) Sophos WAN link are the only connections on that VLAN.

    Sometimes, when it's really bad, I have to plug the modem into a PC, get the IP info, enter that in Sophos as static and save. Interface will then come up, but it will fail to route for some reason. I can then set back to DHCP, and it will get the proper IP. Still won't route though. Finish up by powering off modem for 60sec. Then all will work.

Children
No Data
Unfiltered HTML