On Fri, Jul 31, 2015, at 02:00 PM, [email protected] wrote: > On Fri, Jul 31, 2015, at 04:19 AM, Morrie Wyatt wrote: > > Hi Ben. > > > > The other thing you will find on most modem diagnostic > > pages is a log viewing facility. > > > > It should give you a handle on what the modem has been > > attempting, and at what point things are failing. > > > > One possible trap I have seen people fall for before is > > the username. Usually it will be "[email protected]" > > rather than just "username". Without the tail component, > > the DSLAM at the exchange won't forward the authentication > > details to the correct provider. > > At a quick glance, the username and password will seem > > to be correct. > > > > Things to check anyway. > > > > Regards, > > Morrie. > > >
I've had look at the "diagnostics" in the modem and the error is: "ppp error". Otherwise there are figures for all sorts of things. I assume that this is the pppd in the modem and not the pppd on the computer. The modem is using pppoe in routed mode, which I assume is also in the modem and not the pppoe on my computer. Waiting for the technician to check the server at the other end. ben > Thanks Morrie and Daniel for alerting me to the log facility in the > modem itself ... I'm going to try and have a look at that shortly when I > get off this dial-up session I'm on now to see what I can find. > > Ben > > > -----Original Message----- > > From: luv-main [mailto:[email protected]] On Behalf Of Daniel > > Jitnah > > Sent: Friday, 31 July 2015 8:57 PM > > To: [email protected]; Luv Main > > Subject: Re: adsl problems > > > > Hi Ben > > > > I dont know this particular modem. But all modems that I have come > > across have diagnostics functions accessible from the web interface. > > You will be able to test whether it connects to the outside world and to > > what extent. > > > > There should be a test for adls line status. Thats before any ip based > > connection is established. It should tell you things like connection > > status, adsl synchronisation status, max attainable connection rate, > > noise ratio etc. So if you see data and numbers there it should be > > connected. If you don't see figures then you have no connection. > > If you do then its likely an IP issue. Also the Telstra technician on > > the other side may be able to tell if there is a connection to your > > modem from their side. > > > > Daniel. > > > > > > > > > > On 31/07/15 20:37, [email protected] wrote: > > > On Fri, Jul 31, 2015, at 02:30 AM, Daniel Jitnah wrote: > > >> Hi Ben, > > >> > > >> Is your modem set to Bridge or PPPoE mode? > > >> > > >> PPPoE is easier, and I assume it is here! > > >> > > >> If PPPoE, you should not have to do anything, assuming that your modem > > >> is stock Telstra configuration and has dhcp-server on. > > >> > > >> Set your PC to dhcp and let it connect and get an ip from the modem. > > >> That all you need to do. > > >> > > >> Of course you want be able to connect to it if its ip 10.0.0.138 and you > > >> seem to have your IP 192.168.0.3 (different subnet). > > >> > > >> Alternatively set your IP to 10.0.0.3 and you should be able to connect > > >> to it. But dhcp is easier and it should get routing and dns information > > >> etc automatically. > > >> > > >> Cheers > > >> Daniel. > > > > > > Thanks Daniel. Just after I sent the email I went back to the ethernet > > > config and changed the BOOTPROTO to dhcp and rebooted. I got an address > > > on the same network as the modem and got in through the browser! Failing > > > to do that config before was an oversight. > > > > > > The modem is in router mode by default and I thought I'd go with that > > > for starters before I acquainted myself a bit more with running it from > > > my computer in bridge mode. > > > > > > Unfortunately, after getting into the modem through the browser, it > > > still wouldn't connect to the internet. So, now that I sensed the > > > problem was connection rather than me, I rang Telstra and suggested that > > > the connection to the exchange may be a problem. My password and > > > username were fine. I had to "infer" that the computer was Windows, but > > > all the technician took me through was the browser's view of the modem - > > > operating system was irrelevant. He was in the Phillipines and tried to > > > re-set the server half a dozen times, and I reset the modem each time, > > > but it still would not connect, so the latest is that he will have a > > > technician look at the exchange here in Olinda. That's where it sits at > > > the moment. > > > > > > ben > > > > > >> > > >> > > >> On 31/07/15 19:13, [email protected] wrote: > > >>> I am unable to get my Telstra adsl working. I'm trying to upgrade from > > >>> dial-up and I thought I did a lot of research, but I have failed to get > > >>> anywhere with the adsl and I need help. > > >>> > > >>> The adsl unit is a Technicolor modem/router TG799vac. > > >>> > > >>> I hooked it up and the lights flashed but the Status and Internet lights > > >>> remained red. > > >>> > > >>> I tried to get into the unit with firefox and midori but both failed to > > >>> reach the modem's address http://10.0.0.138 which is the address on the > > >>> unit. I am running network.service and it's up. The config for my > > >>> ethernet connection which goes into the ethernet socket on the modem is: > > >>> [ben@til network-scripts]$ cat ifcfg-enp63s0 > > >>> TYPE=Ethernet > > >>> BOOTPROTO=none > > >>> DEFROUTE=yes > > >>> IPV4_FAILURE_FATAL=no > > >>> IPV6INIT=no > > >>> NAME=enp63s0 > > >>> UUID=6479f67e-53e7-4953-a796-cf3d3f770b2f > > >>> ONBOOT=yes > > >>> HWADDR=00:1E:0B:2C:8E:22 > > >>> PEERDNS=yes > > >>> PEERROUTES=yes > > >>> IPADDR=192.168.0.3 > > >>> NETMASK=255.255.255.0 > > >>> USERCTL=yes > > >>> NM_CONTROLLED=no > > >>> PREFIX=24 > > >>> > > >>> This config was part of my home network and I didn't change it before I > > >>> plugged everything in and powered up. > > >>> > > >>> I tried to make a route to the modem with: > > >>> #route add default gw 10.0.0.138 > > >>> but I get "network is unreachable" but 'systemctl -a |grep network' > > >>> shows network service loaded and active. > > >>> > > >>> So, I'm stuck. In my research before hand I came across many posts > > >>> saying: "just plug it in, use the browser to configure it > > >>> and off you go." I did get comfort from that, but my experience is of > > >>> failure. What can I do to get this modem working? > > >>> > > >>> My distro is fedora 22 and I don't run a desktop, just a window manager > > >>> and am used to doing most things on the command line. > > >>> -- > > >>> Thanks. > > >>> ben > > >>> > > >>> > > >>> > > >>> [email protected] > > >>> _______________________________________________ > > >>> luv-main mailing list > > >>> [email protected] > > >>> http://lists.luv.asn.au/listinfo/luv-main > > >>> > > _______________________________________________ > > luv-main mailing list > > [email protected] > > http://lists.luv.asn.au/listinfo/luv-main > > > > _______________________________________________ > > luv-main mailing list > > [email protected] > > http://lists.luv.asn.au/listinfo/luv-main > _______________________________________________ > luv-main mailing list > [email protected] > http://lists.luv.asn.au/listinfo/luv-main _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
