On Sat, Dec 08, 2001 at 11:44:47PM +0100, Joerg Wunsch wrote:
As Ruslan Ermilov wrote:
You need to configure /some/ interface address for the remote end
anyway, and it must not clash with any other routing table entry,
since ifconfig ... up always adds an entry for the remote IP
On Fri, Dec 07, 2001 at 09:01:12PM +0100, Joerg Wunsch wrote:
As Ruslan Ermilov wrote:
phk has chosen 0.0.0.1 since it obviously cannot be a meaningful
statically configured address.
OK, but is it really necessary? It's much simpler to add routes
over P2P interfaces using the
As Ruslan Ermilov wrote:
You need to configure /some/ interface address for the remote end
anyway, and it must not clash with any other routing table entry,
since ifconfig ... up always adds an entry for the remote IP address
for p2p interfaces.
Only if you have INET address configured
On 7 Dez, Ruslan Ermilov wrote:
The magical destination address is 0.0.0.1. It is used as a
`placeholder' address for the remote side, so you can add a route to
it.
Should probably be extended to 0.0.0.*, so you can add more than one
interface that way.
I thought this already
As Ruslan Ermilov wrote:
phk has chosen 0.0.0.1 since it obviously cannot be a meaningful
statically configured address.
OK, but is it really necessary? It's much simpler to add routes
over P2P interfaces using the interface name ...
You need to configure /some/ interface address for
Hi,
with rev 1.61 of in.c I4B directly hangs up after dialing out. At the
moment I run a current kernel as of yesterday with a netinet directory
as of today except for in.c (which is at rev 1.60 here) and everything
works fine.
Bye,
Alexander.
--
The computer revolution is over. The
Hi,
with rev 1.61 of in.c I4B directly hangs up after dialing out. At the
moment I run a current kernel as of yesterday with a netinet directory
as of today except for in.c (which is at rev 1.60 here) and everything
works fine.
Hi,
Can you give me more details about the failure - error
On Thu, Dec 06, 2001 at 01:52:49PM +, Brian Somers wrote:
Hi,
with rev 1.61 of in.c I4B directly hangs up after dialing out. At the
moment I run a current kernel as of yesterday with a netinet directory
as of today except for in.c (which is at rev 1.60 here) and everything
works
On 6 Dez, Ruslan Ermilov wrote:
with rev 1.61 of in.c I4B directly hangs up after dialing out. At the
moment I run a current kernel as of yesterday with a netinet directory
as of today except for in.c (which is at rev 1.60 here) and everything
works fine.
Can you give me more details
Ruslan Ermilov [EMAIL PROTECTED] wrote:
ISTR that I4B uses some special magical destination address for some
purpose (0.0.0.0 or something).
The magical destination address is 0.0.0.1. It is used as a
`placeholder' address for the remote side, so you can add a route to
it.
Should probably
On Thu, Dec 06, 2001 at 09:23:32PM +0100, Joerg Wunsch wrote:
Ruslan Ermilov [EMAIL PROTECTED] wrote:
ISTR that I4B uses some special magical destination address for some
purpose (0.0.0.0 or something).
The magical destination address is 0.0.0.1. It is used as a
`placeholder' address
11 matches
Mail list logo
