Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 6 subscribers
  • Views 1935 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

VDSL comes up and close ?

Jerome ROXIN

Hi Sophos Community !

 

I've decided to use my SG125Rev3 with Allnet VDSL modem instead of my ISP box.

I 've read a lot of forums and captured as many details of the connection as I could.

The connection is PPPoE with login, VLan835 & MTU 1500. I set the MAC@ of the ISP box to the port used by Allnet. Normaly, no issue.

When I plug the data cable in and look at the logs, here what I get :

2020:08:10-17:03:36 heimdall pppd-pppoe[29480]: Plugin rp-pppoe.so loaded.
2020:08:10-17:03:36 heimdall pppd-pppoe[29480]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
2020:08:10-17:03:36 heimdall pppd-pppoe[29480]: pppd 2.4.7 started by root, uid 0
2020:08:10-17:03:36 heimdall pppd-pppoe[29480]: Send PPPOE Discovery V1T1 PADI session 0x0 length 18
2020:08:10-17:03:36 heimdall pppd-pppoe[29480]: dst ff:ff:ff:ff:ff:ff src 2c:79:d7:36:
2020:08:10-17:03:36 heimdall pppd-pppoe[29480]: [service-name] [host-uniq 28 73 00 00] [PPP-max-payload 05 dc]
2020:08:10-17:03:41 heimdall pppd-pppoe[29480]: Send PPPOE Discovery V1T1 PADI session 0x0 length 18
2020:08:10-17:03:41 heimdall pppd-pppoe[29480]: dst ff:ff:ff:ff:ff:ff src 2c:79:d7:36:
2020:08:10-17:03:41 heimdall pppd-pppoe[29480]: [service-name] [host-uniq 28 73 00 00] [PPP-max-payload 05 dc]
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: Send PPPOE Discovery V1T1 PADI session 0x0 length 18
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: dst ff:ff:ff:ff:ff:ff src 2c:79:d7:36:
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: [service-name] [host-uniq 28 73 00 00] [PPP-max-payload 05 dc]
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 51
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: dst 2c:79:d7:36: src 00:00:5e:00:01:1b
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: [service-name] [AC-name BSR02-AIX] [host-uniq 28 73 00 00] [AC-cookie 44 24 30 be bc 08 b7 35 6e fb 10 7c 85 5b 58 91] [PPP-max-payload 05 dc]
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: Send PPPOE Discovery V1T1 PADR session 0x0 length 38
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: dst 00:00:5e:00:01:1b src 2c:79:d7:36:  --> The MAC@ from my ISP Box

2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: [service-name] [host-uniq 28 73 00 00] [PPP-max-payload 05 dc] [AC-cookie 44 24 30 be bc 08 b7 35 6e fb 10 7c 85 5b 58 91]
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: Recv PPPOE Discovery V1T1 PADS session 0x1 length 18
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: dst 2c:79:d7:36: src 00:00:5e:00:01:1b
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: [service-name] [host-uniq 28 73 00 00] [PPP-max-payload 05 dc]
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: PADS: Service-Name: ''
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: PPP session is 1
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: Connected to 00:00:5e:00:01:1b via interface eth0.835
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: using channel 3
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: Using interface ppp0
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: Connect: ppp0 <--> eth0.835
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: sent [LCP ConfReq id=0x1 <magic 0x9a28a3ec>]
2020:08:10-17:03:51 heimdall pppd-pppoe[29480]: rcvd [LCP ConfAck id=0x1 <magic 0x9a28a3ec>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [LCP ConfReq id=0x8d <mru 1492> <auth chap MD5> <magic 0x38008f6c>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: sent [LCP ConfAck id=0x8d <mru 1492> <auth chap MD5> <magic 0x38008f6c>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: sent [LCP EchoReq id=0x0 magic=0x9a28a3ec]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [CHAP Challenge id=0x1 <b063d[...too long...]2f6d9>, name = "BSR02-AIX"]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: sent [CHAP Response id=0x1 <a8f2b[...too long...]09dc9c>, name = "mylogin"]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [LCP EchoRep id=0x0 magic=0x38008f6c]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [CHAP Success id=0x1 "CHAP authentication success"]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: CHAP authentication succeeded: CHAP authentication success
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: CHAP authentication succeeded  YESSSS ! Who doubt ???
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: peer from calling number 00:00:5E:00:01:1B authorized
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [IPCP ConfReq id=0x9a <addr 176.157.64.1>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: sent [IPCP ConfAck id=0x9a <addr 176.157.64.1>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [IPCP ConfNak id=0x1 <addr mypublicIP> <ms-dns1 194.158.122.10> <ms-dns2 194.158.122.15>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: sent [IPCP ConfReq id=0x2 <addr mypublicIP> <ms-dns1 194.158.122.10> <ms-dns2 194.158.122.15>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [IPCP ConfAck id=0x2 <addr mypublicIP> <ms-dns1 194.158.122.10> <ms-dns2 194.158.122.15>]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: local IP address mypublicIP
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: remote IP address 176.157.64.1
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: primary DNS address 194.158.122.10
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: secondary DNS address 194.158.122.15
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: Script /etc/ppp/ip-up started (pid 29562)  --- Sounds good, right ?
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: rcvd [LCP TermReq id=0x8e]
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: LCP terminated by peer
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: Connect time 0.0 minutes.
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: Sent 0 bytes, received 0 bytes.
2020:08:10-17:03:54 heimdall pppd-pppoe[29480]: sent [LCP TermAck id=0x8e]
2020:08:10-17:03:55 heimdall pppd-pppoe[29480]: Script /etc/ppp/ip-up finished (pid 29562), status = 0x0  --- finished what ???
2020:08:10-17:03:55 heimdall pppd-pppoe[29480]: Script /etc/ppp/ip-down started (pid 29566)
2020:08:10-17:03:55 heimdall pppd-pppoe[29480]: Script /etc/ppp/ip-down finished (pid 29566), status = 0x0
2020:08:10-17:03:57 heimdall pppd-pppoe[29480]: Connection terminated.   --- Hey, why ????
2020:08:10-17:03:57 heimdall pppd-pppoe[29480]: Modem hangup --- ;(((
2020:08:10-17:03:57 heimdall pppd-pppoe[29480]: Exit.
2020:08:10-17:03:57 heimdall pppoe-sh: DSL connection time shorter than 60 seconds (21 sec): Error? - wait 900 seconds

Could someone help me on that, please ?

I'm ready to share more info (but not confidential of course ;) ) to find the exit.

Thanks a lot.



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

    Hello Jerome,

    Thank you for contacting the Sophos Community.

    What is the output of the following logs when the issue happens?

    • kernel.log
    • system.log
    • fallback.log

    What is the speed of the interface?

    #ethtool ethX

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • 0 in reply to emmosophos

    Hi Emmanuel,

     

    Here are the results :

    FALLBACK (w/o data cable in)

    2020:08:11-10:07:51 heimdall [daemon:info] nwd[4356]: Reloading Config
    2020:08:11-10:07:51 heimdall [daemon:info] nwd[4356]: Interface eth0 is up and link is back up
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0 ether 2c:79:d7:36 <broadcast,multicast,up> group 0
    2020:08:11-10:07:52 heimdall [daemon:info] nwd[4356]: Waiting for MDW cycle to end
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0: detected 1 queue(s), 'network' cpuset
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0:0: affinity irq=0x3 rps/xps=0x3
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0: up
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0.835 ether 2c:79:d7:36: <broadcast,multicast> slave-of eth0 group 0 vlan-id 835
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0.835 ether 2c:79:d7:36: <broadcast,multicast,up> slave-of eth0 group 0 vlan-id 835
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0.835: detected 1 queue(s), 'network' cpuset
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0.835:0: affinity irq=0x3 rps/xps=0x3
    2020:08:11-10:07:52 heimdall [daemon:info] irqd[5247]: eth0.835: up
    2020:08:11-10:07:55 heimdall [daemon:info] irqd[5247]: eth0 ether 2c:79:d7:36: <broadcast,multicast,up,running,lowerup> group 0
    2020:08:11-10:07:55 heimdall [daemon:info] irqd[5247]: eth0.835 ether 2c:79:d7:36: <broadcast,multicast,up,running,lowerup> slave-of eth0 group 0 vlan-id 835
    2020:08:11-10:08:02 heimdall [daemon:info] nwd[4356]: Reloading Config
    2020:08:11-10:08:02 heimdall [daemon:info] nwd[4356]: Interface eth0 is up but link is down
    2020:08:11-10:08:02 heimdall [daemon:info] nwd[4356]: Interface eth0 is up but link is down
    2020:08:11-10:08:02 heimdall [daemon:info] nwd[4356]: Interface eth0.835 is up but link is down
    2020:08:11-10:08:02 heimdall [daemon:info] nwd[4356]: Interface eth0 is up and link is back up
    2020:08:11-10:08:02 heimdall [daemon:info] nwd[4356]: Interface eth0.835 is up and link is back up

    SYSTEM

    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_DefaultSophosUTMSupportHost
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsIPrep1t
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsIPrep5t
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsResolver2a
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsIPrep4t
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsIPrep2t
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsResolver4a
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsIPrep3t
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsResolver3a
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsResolver1a
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsResolver5a
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsSboxAPACPool
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsSboxDefaultPool
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_DefaultLetsEncryptApiServer
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsSboxDEPool
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsSboxUSPool
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsSboxEUPool
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NetDnsSophoLivec
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: Adding REF_NtpPool
    2020:08:11-09:33:55 heimdall dns-resolver[4506]: DNS server failed to contact!

     

    KERNEL (I don't like the last line...)

    2020:08:11-09:28:14 heimdall kernel: [78598.968675] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    2020:08:11-09:28:14 heimdall kernel: [78598.968684] 8021q: adding VLAN 0 to HW filter on device eth0
    2020:08:11-09:28:14 heimdall kernel: [78599.018682] IPv6: ADDRCONF(NETDEV_UP): eth0.835: link is not ready
    2020:08:11-09:28:17 heimdall kernel: [78602.072938] igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
    2020:08:11-09:28:17 heimdall kernel: [78602.073208] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    2020:08:11-09:28:17 heimdall kernel: [78602.073869] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.835: link becomes ready
    2020:08:11-09:28:25 heimdall kernel: [78609.962365] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev-ppp0 instead.

    ETHTOOL

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

     

    As said in the user guide about SFP module (Allnet VDSL module in my case), the eth3 port is shared with SFP (also marked as Eth3)...

    Thanks for your help.

  • 0 in reply to Jerome ROXIN

    Salut Jerome and welcome to the UTM Community!

    I'm confused, is the WAN connection on eth3 or eth0?  What're the Up/Down speeds of the WAN connection?

    Does doing 7 in #7 in Rulz (last updated 2019-04-17) resolve this issue?

    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

    Hi Bob,

    Thanks for your post.

    The WAN port is on eth0 which is shared with eth3, so let focus on eth0.

    The SFP modem is an Allnet4781 which respect Sophos HCL.

    At this time, the WAN connection is not possible as the modem hangs up immediately. That's my problem.

    I didn't try Rulz but I'll have a deep look at this and try it tomorrow.

    Keep you informed Community

    Thanks

  • 0 in reply to Jerome ROXIN

    Hi Sophos Community,

     

    I followed Rulz post (changing the data cable gave me 9 Mb more !!).

    But the problem still occurs. I tested several configurations (modifying MTU, with or w/o Virtual MAC,...) with reboot @ every change. No improvement.

    Here's the last lines of PPPoE logs :

    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: primary DNS address 194.158.122.10
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: secondary DNS address 194.158.122.15
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: Script /etc/ppp/ip-up started (pid 13197)
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: rcvd [LCP TermReq id=0xee]
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: LCP terminated by peer -> Did my ISP close my connection ?
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: Connect time 0.0 minutes.
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: Sent 0 bytes, received 0 bytes.
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: sent [LCP TermAck id=0xee]
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: Script /etc/ppp/ip-up finished (pid 13197), status = 0x0
    2020:08:19-11:43:29 heimdall pppd-pppoe[13125]: Script /etc/ppp/ip-down started (pid 13201)
    2020:08:19-11:43:30 heimdall pppd-pppoe[13125]: Script /etc/ppp/ip-down finished (pid 13201), status = 0x0
    2020:08:19-11:43:32 heimdall pppd-pppoe[13125]: Connection terminated.
    2020:08:19-11:43:32 heimdall pppd-pppoe[13125]: Modem hangup
    2020:08:19-11:43:32 heimdall pppd-pppoe[13125]: Exit.
     
    Is this SFP modem really compatible with my ISP ?
     
     
  • 0 in reply to Jerome ROXIN

    Hello Jerome,

    Thank you for the follow-up!

    At least that part you highlighted means that, yes the ISP terminated the connection. 

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Reply Children
Unfiltered HTML