On Sat, Aug 1, 2015, at 12:38 AM, Allan Duncan wrote:
On 01/08/15 07:33, bnis@fastmail.fm wrote:
On Fri, Jul 31, 2015, at 02:00 PM, bnis@fastmail.fm wrote:
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
With an ADSL modem most people let it do the ppp session, and just connect through it to the outside world using it as a firewall and router using NAT on IPV4.
Have a ferret aound your modem's web interface looking for a Status or similar page. Some designs have lots of useful info, others bugger all.
There are three steps in the adsl process:
First, the low level is the modem that just goes between you and _your_ dslam in the exchange. This has a number of steps of negotiation between the ends, and if your modem has good feedback you will see the progression of the lockup. This establishes a bi-directional bitstream.
Second, a packet protocol layer is established to use with pppoe or pppoa.
Third, now there is an IP connection traversing the link there is a ppp account validation. This uses the User/Password combo, and can be done in the modem (usually default) or another device such as a computer or a suitable router. Your modem status may give you some useful info on its progress.
If you use a computer it is up to you the do all the firewalling etc. Of course if you are running IPV6 then the router won't help you much either.
Hope this helps.
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
Thank you Allan ... that's good info for me. And warm thanks to all the other guys who helped. Each response stimulated me in my plight. My adsl is up and I'm happy. The technician must have attended to the server at the exchange because he didn't bother with me. So for those interested, here is my working /etc/sysconfig/network-scripts/ifcfg-enp3s0 file contents: TYPE=Ethernet BOOTPROTO=dhcp HWADDR=12:AA:14:33:9A:F3 ONBOOT=yes I use network and not NetworkManager and I have had to start it before I can ping the modem and get on the net, so it's not starting on boot despite me setting it to start so with chkconfig. I'll look into that. I did get an M$ computer and it showed the same faults in the modems "logs" as the linux computer did, as one would expect I guess. I disable ipv6. ben