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

problems with WAN INTERFACE

Hi there,

since some days I really have trouble with my WAN-INTERFACE on my ASG120 rev4 (9.004-33). I lost the connection very often, the problem is not the DSL-Connection (there is a transfer-network to the router)

Here the log:

2012:12:16-22:50:14  kernel: [95995.477821] ADDRCONF(NETDEV_UP): eth2: link is not ready
2012:12:16-22:50:14  kernel: [95995.477832] 8021q: adding VLAN 0 to HW filter on device eth2
2012:12:16-22:50:16  kernel: [95997.213550] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
2012:12:16-22:50:16  kernel: [95997.213564] e1000e 0000:03:00.0: eth2: 10/100 speed: disabling TSO
2012:12:16-22:50:16  kernel: [95997.214589] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
2012:12:16-22:50:30  kernel: [96011.180247] e1000e: eth2 NIC Link is Down
2012:12:16-22:50:32 alphavil-1 kernel: [96013.809749] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
2012:12:16-22:50:32  kernel: [96013.809771] e1000e 0000:03:00.0: eth2: 10/100 speed: disabling TSO
2012:12:16-22:50:38  kernel: [96019.936225] e1000e: eth0 NIC Link is Down
2012:12:16-22:50:51 alphavil-1 kernel: [96032.253363] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2012:12:16-22:53:00  kernel: [96157.045186] e1000e: eth2 NIC Link is Down
2012:12:16-22:53:37  kernel: [96198.800298] e1000e: eth0 NIC Link is Down
2012:12:16-22:53:40 alphavil-1 kernel: [96201.201181] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2012:12:16-22:53:52  kernel: [96213.821062] e1000e: eth0 NIC Link is Down
2012:12:16-22:53:53  kernel: [96214.873173] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
2012:12:16-22:54:13  kernel: [96234.821261] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
2012:12:16-22:54:13  kernel: [96234.821277] e1000e 0000:03:00.0: eth2: 10/100 speed: disabling TSO
2012:12:16-22:55:18  kernel: [96299.489802] ADDRCONF(NETDEV_UP): eth2: link is not ready
2012:12:16-22:55:18  kernel: [96299.489813] 8021q: adding VLAN 0 to HW filter on device eth2
2012:12:16-22:55:20  kernel: [96301.825260] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
2012:12:16-22:55:20  kernel: [96301.825274] e1000e 0000:03:00.0: eth2: 10/100 speed: disabling TSO
2012:12:16-22:55:20  kernel: [96301.826286] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready


Very strange for me: 8021q: adding VLAN 0 to HW filter on device eth2  but I have no VLAN !

ethtool shows:

Settings for eth2:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
       drv probe link
Link detected: yes


The other interfaces have no problem. Has anybody an idea?

Cheers


This thread was automatically locked due to age.
Parents
  • Please always remember to state your precise version number - 9.004-33?

    First, try setting the MTU of the interface to a smaller value, say 1364.  If that works, ask your ISP how high you should set it.

    If that doesn't work, you will want to cycle through the different combinations of speeds and duplex for the NIC on the 'Hardware' tab.  After you make a change, power cycle the modem and your appliance to be certain they renegotiate the connection.

    Did that help?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • Please always remember to state your precise version number - 9.004-33?

    First, try setting the MTU of the interface to a smaller value, say 1364.  If that works, ask your ISP how high you should set it.

    If that doesn't work, you will want to cycle through the different combinations of speeds and duplex for the NIC on the 'Hardware' tab.  After you make a change, power cycle the modem and your appliance to be certain they renegotiate the connection.

    Did that help?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data