Guest User!

You are not Sophos Staff.

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

What did my ISP do to my connection :(

Hi Guys. I've been with Dodo (Australian ISP) for the last 2 years with no issues however yesterday my modem rebooted and can't connect to internet anymore. First year was on ADSL second year FTTN which I'm on now.
My setup was and is I have a Netgear DM200 vdsl modem on bridged mode and behind it Sophos UTM doing the PPPoE then my Sophos is being my gateway.

Now the issue is I get a random public IP like 211.xxx or 203.xxx from the ISP which is not my static IP. When I get that random IP I'm not connected to internet but my modem says I'm. I've also tried using the Netgear with my PPPoE details and I get the same thing. I have no idea what has happened from the ISP end. If I use their Huwaei modem it works fine and I get my static IP only if I let it do the PPPoE and be the main gateway. If I put it on bridged mode and let either Sophos or Netgear do PPPoE I get that weird public IP.

I called them and got them to reset my connection and of course they don't want provide support since their modem works and other modems not working. Nothing has changed from my end either it just stopped working all of the sudden. I never had issue with it and before Dodo I was with TPG with same exact setup. I also tried putting my static IP replacing the weird public IP but doesn't work.

Could it be my ISP done something to stop me from using my own modem? Anyone knows what they possible they have done or gone wrong?

Cheers
***



This thread was automatically locked due to age.
  • Hi Mohamed,

    have you tried putting in the MAC address of the old router onto the new connection?

    over here a couple of ISPs will only support their router and lock their connection down to a MAC address from the router they provided you with.

    XG & UTM Architect (Systems: XG v18 & UTM 9.7 - Virtual, HW & SW)
    Curious enough to take it apart, skilled enough to put it back together, Clever enough to hide the extra parts when I'm Done!

  • Hi Argo. What you say makes sense to me as only their device authenticates. I'll have to fight against them to get them to even look at the port security settings.

    I'm not sure how I can find the router MAC address I'm assuming it's not the LAN MAC address there should be another one for WAN or something? I've tried using the LAN as a virtual MAC on the Sophos but doesn't work. 

    What I noticed is whatever PPPoE username & password I put it accepts it including the real one as you can see:

    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Plugin rp-pppoe.so loaded.
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: pppd 2.4.7 started by root, uid 0
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Send PPPOE Discovery V1T1 PADI session 0x0 length 12
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst ff:ff:ff:ff:ff:ff src 00:15:5d:b1:8d:17
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [service-name] [host-uniq 5a 24 00 00]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 7c:69:f6:5e:ec:10
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name prthpri-lns01] [AC-cookie e1 bc 3c 28 53 b6 45 67 7d a1 f2 77 1a 44 00 15]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Send PPPOE Discovery V1T1 PADR session 0x0 length 32
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 7c:69:f6:5e:ec:10 src 00:15:5d:b1:8d:17
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [service-name] [host-uniq 5a 24 00 00] [AC-cookie e1 bc 3c 28 53 b6 45 67 7d a1 f2 77 1a 44 00 15]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 7c:69:f6:5e:ec:00
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name prthpri-lns01] [AC-cookie e1 bc 3c 28 53 b6 45 67 7d a1 f2 77 1a 44 00 15]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 7c:69:f6:5e:ec:50
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name prthpri-lns01] [AC-cookie e1 bc 3c 28 53 b6 45 67 7d a1 f2 77 1a 44 00 15]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 7c:69:f6:5e:ec:70
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name prthpri-lns01] [AC-cookie e1 bc 3c 28 53 b6 45 67 7d a1 f2 77 1a 44 00 15]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 6c:20:56:69:74:30
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name mlganxd-lns01] [AC-cookie 74 2e 0c 86 e1 15 1f 13 b2 02 ca c8 b2 bb 2f 99]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 6c:20:56:69:74:50
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name mlganxd-lns01] [AC-cookie 74 2e 0c 86 e1 15 1f 13 b2 02 ca c8 b2 bb 2f 99]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 6c:20:56:69:74:70
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name mlganxd-lns01] [AC-cookie 74 2e 0c 86 e1 15 1f 13 b2 02 ca c8 b2 bb 2f 99]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 86
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 6c:20:56:69:74:10
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-name mlganxd-lns01] [AC-cookie 74 2e 0c 86 e1 15 1f 13 b2 02 ca c8 b2 bb 2f 99]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Recv PPPOE Discovery V1T1 PADS session 0xe1b1 length 69
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: dst 00:15:5d:b1:8d:17 src 7c:69:f6:5e:ec:10
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: [vendor-specific 00 00 0d e9 01 0f 41 56 43 30 30 30 30 35 34 37 36 35 32 32 33 81 04 00 00 58 48 82 04 00 00 d6... (length 33)] [service-name] [host-uniq 5a 24 00 00] [AC-cookie e1 bc 3c 28 53 b6 45 67 7d a1 f2 77 1a 44 00 15]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: PADS: Service-Name: ''
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: PPP session is 57777
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Connected to 7c:69:f6:5e:ec:10 via interface eth0
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: using channel 8
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Using interface ppp0
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Connect: ppp0 <--> eth0
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xc2607144>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [LCP ConfReq id=0x1 <mru 1492> <auth chap MD5> <magic 0xfdad23aa>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: sent [LCP ConfAck id=0x1 <mru 1492> <auth chap MD5> <magic 0xfdad23aa>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0xc2607144>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: sent [LCP EchoReq id=0x0 magic=0xc2607144]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [LCP EchoRep id=0x0 magic=0xfdad23aa]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [CHAP Challenge id=0x1 <ff0bca135320cbd4fa53b91c343dfb8d>, name = "auth"]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: sent [CHAP Response id=0x1 <4b48537f7a29646bf4e4d8e2ca8d972e>, name = "fiber1775842@dodo.co.uk"]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [CHAP Success id=0x1 ""]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: CHAP authentication succeeded
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: CHAP authentication succeeded
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: peer from calling number 7C:69:F6:5E:EC:10 authorized
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [IPCP ConfReq id=0x1 <addr 203.134.115.74>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: sent [IPCP ConfAck id=0x1 <addr 203.134.115.74>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [IPCP ConfNak id=0x1 <addr 211.27.194.42> <ms-dns1 203.134.17.90> <ms-dns2 211.26.25.90>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: sent [IPCP ConfReq id=0x2 <addr 211.27.194.42> <ms-dns1 203.134.17.90> <ms-dns2 211.26.25.90>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: rcvd [IPCP ConfAck id=0x2 <addr 211.27.194.42> <ms-dns1 203.134.17.90> <ms-dns2 211.26.25.90>]
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: local IP address 211.27.194.42
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: remote IP address 203.134.115.74
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: primary DNS address 203.134.17.90
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: secondary DNS address 211.26.25.90
    2019:02:24-23:59:07 sukafun-utm pppd-pppoe[9306]: Script /etc/ppp/ip-up started (pid 9307)
    2019:02:24-23:59:08 sukafun-utm pppd-pppoe[9306]: Script /etc/ppp/ip-up finished (pid 9307), status = 0x0
     
     
    But no internet with that IP above. My static IP is different and I only get it right when using their modem to do PPPoE.
  • fiber1775842@dodo.co.uk

     

    is this your username in Australia?

    should it not be something different?

    XG & UTM Architect (Systems: XG v18 & UTM 9.7 - Virtual, HW & SW)
    Curious enough to take it apart, skilled enough to put it back together, Clever enough to hide the extra parts when I'm Done!

  • That's correct. I've taken screenshot when I was trying random username. Mine ends with .com.au

    As you can see it successfully authenticates and gets random public IP which doesn't make sense to me as well doesn't connect to internet

  • I have had an occasion where my service was supposed to be static but I was getting a dynamic address.   The ISP had configured something incorrectly, and the problem persisted until they found their error.

    Multiple people in this forum have experienced problems with the ISP including an incorrect MTU setting in the DHCP information -- something like 512 or 576 instead of 1512   UTM tries to honor the instruction and then experiences terrible performance.   There seems to be a way to tell UTM to ignore the ISP's MTU setting, for those ISPs that do not know how to fix their own problems.