Re: remote IP address not being sent

js2k2000@xxxxxxxxx writes:

>Correction/Clarification.

>I was dialing a ISP half way around the world using a landline, and was
>having trouble connecting. I used several of the available telephone
>numbers. What I have discovered since the original posting is that some
>of the servers do supply a remote IP address and some do not.

>I have tested with WinXP and the router that I am working on. Having or
>not having the remote IP does not impact the WinXP data transfers. The

Win sends a default which the router accepts. It does not matter which
number.

>tests have shown that the router needs to have the remote IP in order
>for it to operate. So I have concluded that the PPP client in the
>router is a bit deficient.

>Internally the routers PPP client remote IP is defaulted to 0.0.0.0.
>When the link goes up, if it does not receive the remote IP it stays
>0.0.0.0. It then uses this address when it updates the route table
>default gateway entry.

Put
10.1.1.1:
into /etc/ppp/options.
>Although I'm not working on the PPP software I may have to fix the
>problem. So...

No problem.

>If no remote IP is received, what address should be used instead?
o
>What RFC covers this issue?

None. It does not matter. The only purpose of that remote address is for
the routing tables in your computer. Nothing else in the world knows or
cares what you call the other end of a ppp link.


>And now for your comments.

>> That's weird. Why would you send a request for an MTU of 1500?
>> That's the default. There's no reason to ask for the default.
>>
>Well that's what it does

I thought you were in control. It is a bug in the software. Not serious.

.

Relevant Pages
Loading