Re: Fwd: Billion 7800N

On 22 August 2011 22:02, Camaleón <noelamac@gmail.com> wrote:

On Mon, 22 Aug 2011 10:27:57 +1000, Heddle Weaver wrote:

> On 21 August 2011 21:20, Camaleón <noelamac@gmail.com> wrote:

>> But do you really need it? I mean, does your ISP require you to use a
>> PPP connection with your router? I also use a DSL connection and don't
>> need PPP for nothing.
>>
>>
> No I don't.
> I need pppd of course, but not ppp.

Can you explain why you need pppd? :-?

Well, I was under the impression that with ppp over ethernet, the daemon would be required.

I'm probably wrong.

That's alright.

It makes other people feel good.

>> Can you point me to somewhere on the Internet where I can see what are
>> your ISP connection settings?
>>
>>
> I'll bring them into town and post them on the next trip, probably
> tomorrow.

This is getting very interesting, like a mystery novel :-)

I've got severe health problems, so I have access to the computers of a specialist Disabled Job Network organisation.

They somewhat draw the line before downloading an iso and burning it to disc, though.

This is also why I haven't got back to the list over the last couple of days.

Stretched out on a bed with a definition of headaches that engenders a death-wish, which I would indulge in if I could move.

Luckily the situation takes over completely and I'm incapable of moving.

>> Okay, that's what I thought. Then the same has to apply for your linux
>> box. Can you check if DHCP is enable on the windows laptop?
>>
>>
> It's not mine. so I've given it back, but to establish a connection
> immediately, it must have been as I would have needed an IP address to
> connect.

Yes, having DHCP on is the most common nowadays. Anyway, having a static
IP would have required to manually set the gateway.

Well, there could be something in that.

As I recall, this ISP relegates static and not dynamic addresses.

>> >> The network card requires a firmware, you should download from
>> >> non-free repos. Additional information here:
>> >>
>> >> http://wiki.debian.org/Firmware
>> >>
>> >>
>> > Further along in the sequence, eth0 and the firmware seem to connect
>> > up, so I don't think there's a problem there.
>>
>> Anyway, you should install it.
>>
>>
> O.K.
> I'll do that with aptitude when I get a connection.

Yep, just to discard any source of the problem.

>> In fact, the same you did in your windows box you have to do in your
>> linux box. If DHCP is enabled on windows, enable it on linux. If no
>> dialer was used in windows, do not use a dialer in linux, and so on...
>>
>>
> Well, I'm actually getting an IP address on the Linux laptop, so DHCP
> must be active.

If your ethernet device has an IP assigned that means the router is able
to communicate with your laptop and so you should also be able to access
to the router or at least get a response from wget different than a
"timeout" :-?

I believe the contact between the laptop and modem is inconsistent and think this is the source of the majority of disconnections.

I think there is more than one aspect to this problem.

> I'll post that when I get back in also, although I'm sure I've done it
> already somewhere.
> I recall my IP, the peer's IP, DNS primary and secondary, amongst other
> things, but I'll get proof positive.
> Regards and thanks,

Waiting anxiously for the feedback :-)

O.K., here it is, but it might be a bit of an over-dose:

dhcp last modified May 23rd, and dhcp3, last modified April 29th,

both installed and appear active

~~~~~~~~~~~~~~~~~~~~~~~~~

Primary server: 203.12.160.35

Secondary server: 203.12.160.36

These are both present and correct in 'resolve.conf'

~~~~~~~~~~~~~~~~~~~~~~~~~~

This is interesting because it states 'existing default route through ppp3':

weaver@Bandit:~$ su

Password:

Bandit:/home/weaver# plog

Aug 23 18:24:15 Bandit pppd[22604]: PAP authentication succeeded

Aug 23 18:24:15 Bandit pppd[22604]: peer from calling number 00:03:A0:11:E0:78 authorized

Aug 23 18:24:15 Bandit pppd[22604]: not replacing existing default route through ppp3

Aug 23 18:24:15 Bandit pppd[22604]: local IP address 110.174.203.247

Aug 23 18:24:15 Bandit pppd[22604]: remote IP address 10.20.21.81

Aug 23 18:24:15 Bandit pppd[22604]: primary DNS address 203.12.160.35

Aug 23 18:24:15 Bandit pppd[22604]: secondary DNS address 203.12.160.36

Bandit:/home/weaver#

~~~~~~~~~~~~~~~~~~~~~~~~~~

...and here we have ppp addresses where there shouldn't be any:

Bandit:/home/weaver# /sbin/ifconfig

eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46

inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:2297 errors:0 dropped:110 overruns:0 frame:0

TX packets:3351 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:583932 (570.2 KiB) TX bytes:340990 (332.9 KiB)

Interrupt:16

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:493 errors:0 dropped:0 overruns:0 frame:0

TX packets:493 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:29474 (28.7 KiB) TX bytes:29474 (28.7 KiB)

ppp0 Link encap:Point-to-Point Protocol

inet addr:110.174.203.247 P-t-P:10.20.21.72 Mask:255.255.255.255

UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1

RX packets:3 errors:0 dropped:0 overruns:0 frame:0

TX packets:3 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:3

RX bytes:54 (54.0 B) TX bytes:54 (54.0 B)

ppp1 Link encap:Point-to-Point Protocol

inet addr:110.174.203.247 P-t-P:10.20.21.72 Mask:255.255.255.255

UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1

RX packets:3 errors:0 dropped:0 overruns:0 frame:0

TX packets:22 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:3

RX bytes:54 (54.0 B) TX bytes:8574 (8.3 KiB)

ppp2 Link encap:Point-to-Point Protocol

inet addr:110.174.203.247 P-t-P:10.20.21.36 Mask:255.255.255.255

UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1

RX packets:12 errors:0 dropped:0 overruns:0 frame:0

TX packets:3 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:3

RX bytes:1197 (1.1 KiB) TX bytes:54 (54.0 B)

ppp3 Link encap:Point-to-Point Protocol

inet addr:110.174.203.247 P-t-P:10.20.21.81 Mask:255.255.255.255

UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1

RX packets:126 errors:0 dropped:0 overruns:0 frame:0

TX packets:85 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:3

RX bytes:161873 (158.0 KiB) TX bytes:5037 (4.9 KiB)

Where would I go to delete those?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

...and they seem to be breeding:

Bandit:/home/weaver# /sbin/route -n

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp7

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp5

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp6

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp4

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp1

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp2

0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp3

10.20.21.36 0.0.0.0 255.255.255.255 UH 0 0 0 ppp2

10.20.21.36 0.0.0.0 255.255.255.255 UH 0 0 0 ppp4

10.20.21.72 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0

10.20.21.72 0.0.0.0 255.255.255.255 UH 0 0 0 ppp1

10.20.21.81 0.0.0.0 255.255.255.255 UH 0 0 0 ppp3

10.20.21.81 0.0.0.0 255.255.255.255 UH 0 0 0 ppp6

10.20.21.173 0.0.0.0 255.255.255.255 UH 0 0 0 ppp5

10.20.21.173 0.0.0.0 255.255.255.255 UH 0 0 0 ppp7

Bandit:/home/weaver#

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

But behind all of this is the knowledge that this old laptop gives up the connection - not the modem or peer - on a fairly frequent, inconsistent basis, reminiscent of how a dry joint works in other electronic fields I've worked in (High-end amps) and the memory of how hard that is to find, let alone deal with. This assumption comes from messages like "Serial port not detected".Or, is that ppp looking for a dial-up modem?

I'm afraid I've reached the end of what little knowledge I have, but I know that the only network configuration tools I have installed are pppoe and pppoeconf and I've never configured a phone number.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The local IP address of 110.174.203.247 is correct.

Remote IP should be 10.20.21.36, but anything within that general band could be considered kosher.

...and for what it's worth:

Bandit:/home/weaver# ifconfig ppp0

ppp0 Link encap:Point-to-Point Protocol

inet addr:110.174.203.247 P-t-P:10.20.21.173 Mask:255.255.255.255

UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1

RX packets:4 errors:0 dropped:0 overruns:0 frame:0

TX packets:6 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:3

RX bytes:181 (181.0 B) TX bytes:220 (220.0 B)

That's about it, unless there's anything else you need. I'm afraid I don't have anything solid to contribute at this stage, but would be grateful for a translation.

It looks like I can get a reconditioned Dell PC for $250.00 this Monday, which should leave me free to play with the laptop a little more.

So, if you don't want to become any more involved with this situation, I can understand.

Regards and thanks,

Weaver