Azzz
Sent from my iPhoneapp.pp0-0--
the 3step i got the following warning:
''SIOCADDRT: Invalid argument''
Now the network does not work.
The same three steps under debian3.0 work fine, but I
rather cannot
update from debian2.2 to debian3.0 because debian2.2
runs on very
old computer so debian3.0 is "too he
> 2step
> ' I changed the file /etc/network/interfaces'
> 3step 'ifup --all'
>
> after the 3step i got the following warning:
> ''SIOCADDRT: Invalid argument''
>
> Now the network does not work.
> Could you please someone h
the 3step i got the following warning:
''SIOCADDRT: Invalid argument''
Now the network does not work.
The same three steps under debian3.0 work fine, but I
rather cannot
update from debian2.2 to debian3.0 because debian2.2
runs on very
old computer so debian3.0 is "too he
Hi,
When you configured your kernel (with 'make menuconfig' or 'make
xconfig'), did you select the rtl8139 driver? This is under the
Network Devices options, 10/100 MBPS. I personally suggest compiling
it as a module so that an "M" shows up next to it in the square
brackets.
For compiling the ker
e -
From: "Elizabeth Barham" <[EMAIL PROTECTED]>
To:
Sent: Thursday, May 02, 2002 7:53 PM
Subject: Re: SIOCADDRT : No such device
> [EMAIL PROTECTED] writes:
>
> > Also, when I do make config, I select all default. How do I know,
> > what card, I have.
&
--
On Thu, 2 May 2002 19:36:00
dkotian3 wrote:
>Hi,
>>>What an ifconfig give you ?
>> ifconfig eth0
> eth0: error fetching interface information: Device not found
Hi,
Can you also mail the output of cat /proc/interrupts.
I have a weird feeling that your eth0 will not be listed there,
Thanks
[EMAIL PROTECTED] writes:
> Also, when I do make config, I select all default. How do I know,
> what card, I have.
Depends on your machine's bus. For pci, use "lspci". It has
a verbose option which can be increased with more v's, as in
lspci -vv
With an ISA bus (and PNP devices), use
pnpdump
Hi,
>>What an ifconfig give you ?
ifconfig eth0
eth0: error fetching interface information: Device not found
>>Did you compile it in the kernel ?
I did it, and boot with the new kernel.
I have both 2.2.19 installed from CD and also 2.4.18 (source from
kernel.org).
When I do uname -a, I c
t; > work.
> >
> > Generally, ifconfig should show you whether or not a NIC is noticed by
> > the kernel. You said that you insmod'ed them - did you receive any
> > report that this may have not worked while doing it?
> >
> > sockios.h:
> > /* Routin
>Thanks ,
>Could someone help in how to add network drivers for debian.
>The network card seems to be RTL8129.
>
>Thanks and Regards
>Deepak
Hi,
What an ifconfig give you ?
Did you compile it in the kernel ?
Did you configure your /etc/network/interfaces file ?
Give us more informations...
fconfig should show you whether or not a NIC is noticed by
> the kernel. You said that you insmod'ed them - did you receive any
> report that this may have not worked while doing it?
>
> sockios.h:
> /* Routing table calls. */
> #define SIOCADDRT 0x890B /* add rou
re I can setup 'route' ?
>
> You need to have the NICs bound to an ethernet device for route to
> work.
>
> Generally, ifconfig should show you whether or not a NIC is noticed by
> the kernel. You said that you insmod'ed them - did you receive any
> report that this may have
whether or not a NIC is noticed by
>the kernel. You said that you insmod'ed them - did you receive any
>report that this may have not worked while doing it?
>
>sockios.h:
>/* Routing table calls. */
>#define SIOCADDRT 0x890B /* add routing table entry */
worked while doing it?
sockios.h:
/* Routing table calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C /* delete routing table entry */
#define SIOCRTMSG 0x890D /* call to routing system */
The SIOC
any
report that this may have not worked while doing it?
sockios.h:
/* Routing table calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C /* delete routing table entry */
#define SIOCRTMSG 0x890D /* call to
27; ?
The problem which I am having while setting up route is :
route add -net 192.168.2.0 netmask 255.255.255.0 eth0
SIOCADDRT : No such device
route add default gw 192.168.2.1 eth0
Network unreachable
192.168.2.1 is my gateway to the world and all the computers on the LAN have to
be assigned
Are you sure that you card is up before you try to connect? Before
you type the dhcpd command, what do you see when you type ifconfig?
Is the module loaded (lsmod)?
tmask 0.0.0.0 metric 1
When I try this in debian 2.2.3 with kernel 2.4.9 and my card 3com509
configured in the kernel, then I get the message
"SIOCADDRT: Network is unreachable"
This I get with Debian, Progeny and Demolinux 3.0, but not with Mandrake8.0.
With Mandrake I have no
Britton wrote:
>
> Oddly, this one does't show up in dmesg. It happens a couple of times
> during bootup and thats it. Ideas what is going on would be mose welcome.
You have a `route add -net ...` in one of your init scripts (most likely
in /etc/init.d/network). This was needed by the 2.0 kern
Subject: another strange bootup message: SIOCADDRT: Invalid argument
Date: Tue, Jun 19, 2001 at 01:26:51PM -0800
In reply to:Britton
Quoting Britton([EMAIL PROTECTED]):
>
> Oddly, this one does't show up in dmesg. It happens a couple of times
> during bootu
On Wed, Jun 20, 2001 at 06:36:24PM +0200, Andrea Vettorello wrote:
> Britton wrote:
>
> > Oddly, this one does't show up in dmesg. It happens a couple of times
> > during bootup and thats it. Ideas what is going on would be mose welcome.
>
Hi There,
Don't know if I can
Britton wrote:
> Oddly, this one does't show up in dmesg. It happens a couple of times
> during bootup and thats it. Ideas what is going on would be mose welcome.
IIRC i was having something like that on boot when i've upgraded from slink to
potato, try looking in your /etc/network but don't re
Oddly, this one does't show up in dmesg. It happens a couple of times
during bootup and thats it. Ideas what is going on would be mose welcome.
Britton Kerin
__
GNU GPL: "The Source will be with you... always."
> I use my Debian 2.2r2 as a router, but it always shows the message
> "SIOCADDRT: File exists" at boot every time.
> I use the kernel 2.2.17 that come with the debian 2.2.
That's because your using the old /etc/init.d/network file, what you can
do is edit that f
Hi,
I use my Debian 2.2r2 as a router, but it always shows the message
"SIOCADDRT: File exists" at boot every time. I use the kernel 2.2.17 that come
with the debian 2.2.
Best regard
u-land
== Mailed via Openfind ==-
http://mail2000.com.tw/ ´£¨Ñ§K¶O¹q¤l¶l¥ó«H½c
On 12 Jun 2000, Jason Quigley wrote:
> BTW, somebody mentioned problems with disk performance under 2.2.15 and that
> I should stay with 2.2.14.
>
> I am interested in getting LVM working on my system and the only 2.2.x
> system that will be patched will be 2.2.15+.
>
> Does anybody know if this
BTW, somebody mentioned problems with disk performance under 2.2.15 and that
I should stay with 2.2.14.
I am interested in getting LVM working on my system and the only 2.2.x
system that will be patched will be 2.2.15+.
Does anybody know if this person was using the wrong orifice to communicate?
Mark wrote:
> Hmm, ok, but the networks file is stock, set up by the debian install. I
> have upgraded the kernel from 2.0.38 to 2.2.15 - would this be the "route"
> of the problem?
:) Yup.
If I am not entirely mistaken, the 2.2.x kernel doesn't need the route
entry as it sets routes automatical
>... my /etc/init.d/network says 127.0.0.0 but don't take that for gospel.
>
>Cheers,
> Corey Popelier
> http://members.dingoblue.net.au/~pancreas
> Work Email: [EMAIL PROTECTED]
>
>On Mon, 12 Jun 2000, Mark wrote:
>
>> On boot up, when my system executes the ne
y Popelier
http://members.dingoblue.net.au/~pancreas
Work Email: [EMAIL PROTECTED]
On Mon, 12 Jun 2000, Mark wrote:
> On boot up, when my system executes the network init script, it gives the
> error:
>
> SIOCADDRT: Invalid Parameters
>
> the network script contains:
>
On boot up, when my system executes the network init script, it gives the
error:
SIOCADDRT: Invalid Parameters
the network script contains:
ifconfig lo 127.0.0.1
route add -net 127.0.0.1 lo
It's crashing on the "route add" bit. Shouldn't it be "route ad
John wrote:
>I have only just seen your message. The error is in the email program
>made available to me by my ISP when I signed on some 20 months ago.
>I had noted the problem with incoming mail, but did not think it would
>affect outgoing mail onto other machines. If I've caused any dif
John wrote:
>
> on 05 Jan 100, Howard Mann wrote...
>
> >
> >
> >> 2. For some time now when booting, I get the message
> >> 'SIOCADDRT - invalid argument'. It appears to cause
> >> no problem - nevertheless, I'd like
on 05 Jan 100, Howard Mann wrote...
>
>
>> 2. For some time now when booting, I get the message
>> 'SIOCADDRT - invalid argument'. It appears to cause
>> no problem - nevertheless, I'd like to understand exactly
>> what is referred to
t: archive/latest/77758
>> X-loop: debian-user@lists.debian.org
>> Precedence: list
>> Resent-sender: [EMAIL PROTECTED]
>> To: debian-user@lists.debian.org
>> From: John <[EMAIL PROTECTED]>
>> Subject: Vera and SIOCADDRT - separate subjects
>> Date: W
is mail 32
> > > Resent-message-id: <[EMAIL PROTECTED]>
> > > Resent-from: debian-user@lists.debian.org
> > > X-mailing-list: archive/latest/77758
> > > X-loop: debian-user@lists.debian.org
> > > Precedence: list
> > > Resent-sender: [EMAIL
John <[EMAIL PROTECTED]> writes:
> 1. I found and installed a program, Vera 1.4a-1, which is
> stated to list acronyms. There was no problem with
> dselect and 'dpkg -l' shows it as installed, however, I
> am neither able to locate any file of that name nor to
> access the list. An
; > Precedence: list
> > Resent-sender: [EMAIL PROTECTED]
> > To: debian-user@lists.debian.org
> > From: John <[EMAIL PROTECTED]>
> > Subject: Vera and SIOCADDRT - separate subjects
> > Date: Wed, 5 Jan 100 20:23:07 GMT
>^^^
>
ailing-list: archive/latest/77758
> X-loop: debian-user@lists.debian.org
> Precedence: list
> Resent-sender: [EMAIL PROTECTED]
> To: debian-user@lists.debian.org
> From: John <[EMAIL PROTECTED]>
> Subject: Vera and SIOCADDRT - separate subjects
> Date: Wed, 5 Jan 100 20:23:07 GMT
> 2. For some time now when booting, I get the message
> 'SIOCADDRT - invalid argument'. It appears to cause
> no problem - nevertheless, I'd like to understand exactly
> what is referred to and make any correction needed.
> So far I've found n
some time now when booting, I get the message
'SIOCADDRT - invalid argument'. It appears to cause
no problem - nevertheless, I'd like to understand exactly
what is referred to and make any correction needed.
So far I've found no reference to meaning - there have
ito >when I use the command route, for example route add -net 127.0.0.0 I get
danito >the message SIOCADDRT: Invalid argument. I use an ethernet SMC ultra and
danito >it works fine, even when I get that message. The configuration of the
danito >Kernel is OK. I would like to know what is g
route add -host 127.0.0.1 lo
is added automatically by kernel. You don't need to do it again. If you want to
overwrite it with some other options - use it with full syntax.
goto /usr/src/linux/Documentation
On Wed, Dec 29, 1999 at 03:34:29PM -0500, Sebastian Canagaratna wrote:
> Try from the co
st of the file gives the proper information.
Sebastian Canagaratna
Department of Chemistry
Ohio NOrthern University
Ada, OH 45810.
> I use Debian 2.1 and I have changed my Kernel 2.0.36 to 2.2.4 and
> when I use the command route, for example route add -net 127.0.0.0 I get
> the mes
I use Debian 2.1 and I have changed my Kernel 2.0.36 to 2.2.4 and
when I use the command route, for example route add -net 127.0.0.0 I get
the message SIOCADDRT: Invalid argument. I use an ethernet SMC ultra and
it works fine, even when I get that message. The configuration of the
Kernel is OK
I had the same problem upgrading from kernel 2.0.x to 2.2.13:
SIOCADDRT: Invalid argument
I solved the SIOCADDRT error message updating the
/etc/init.d/network script. Just to be safe I installed also the
netbase_3.12-2 package for Slink
(http://www.debian.org/~rcw/2.2/warnings.html).
BTW, just
Charles Lewis ([EMAIL PROTECTED]) wrote:
> The way we solved the SIOCADDRT problem (in potato) was to just comment out
> the route add lines. Apparently they are not needed. Although why they were
> needed in slink and not potato I don't know.
It's a kernel issue. Linux 2.2.x
Yep. Looks like the 2.2.x series is smart enought not to
need them. Course, I still include them for completion's
sake.
Bryan
On 20-Oct-99 Colin Marquardt wrote:
> * Charles Lewis <[EMAIL PROTECTED]> writes:
>
>> The way we solved the SIOCADDRT problem (in potato)
* Charles Lewis <[EMAIL PROTECTED]> writes:
> The way we solved the SIOCADDRT problem (in potato) was to just comment out
> the route add lines. Apparently they are not needed. Although why they were
> needed in slink and not pota
The way we solved the SIOCADDRT problem (in potato) was to just comment out
the route add lines. Apparently they are not needed. Although why they were
needed in slink and not potato I don't know.
===
Charles Lewis, Director of Administrative Comp
rote:
>> 2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
>> route add -net 127.0.0.0
>>to:
>> route add -net 127.0.0.0 netmask 255.255.255.0 lo
>>
> I had the same problem (2.0.36->2.2.12) in my /etc/init.d/network:
>#! /
ying to load modules I didn't need/want. I ended up
> commenting everything out. Is there any reason not to delete the file?
>
> Richard Weil
>
> Hans Gubitz wrote:
>
>> On Mon, Oct 18, 1999 at 09:31:54PM -0400, Bryan Scaringe wrote:
>> > 2) As for SIOCA
1999 at 09:31:54PM -0400, Bryan Scaringe wrote:
> > 2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
> > route add -net 127.0.0.0
> >to:
> > route add -net 127.0.0.0 netmask 255.255.255.0 lo
> >
> I had the same proble
On Mon, Oct 18, 1999 at 09:31:54PM -0400, Bryan Scaringe wrote:
> 2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
> route add -net 127.0.0.0
>to:
> route add -net 127.0.0.0 netmask 255.255.255.0 lo
>
I had the same problem (2.0.36->2.2.12)
it works for me.
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
file has a line to add a route for local network traffic through
the loopback interface. As of Kernel 2.2.0, you need to have
a netmask on that line. Debian Slink is designed for 2.0.x
kernels which
it works for me.
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
file has a line to add a route for local network traffic through
the loopback interface. As of Kernel 2.2.0, you need to have
a netmask on that line. Debian Slink is designed for 2.0.x
kernels which
>>>>> "Kai" == Kai Rascher <[EMAIL PROTECTED]> writes:
Kai> Hi experts, I installed kernel 2.2.11 (Debian 2.1) and
Kai> everything seem all right. But there are two messages
Kai> ´SIOCADDRT invalid argument´ during boot process I don´t
Ka
Hi again,
When I try to restart /etc/init.d/network or set the route from the
cli, I get an SIOCADDRT: Invalid argument error. I searched through
the archives, and the only thing I found was a reference to 2.2.*
kernels and upgrade netbase to the one in potato.
The kernel on this machine is
, Armin Wegner wrote:
> Hi,
>
> Booting Slink with Linux 2.2.5 kernel I get the message
> SIOCADDRT: Invalid argument
> after mounting the file systems. What does this mean? Looks like an error,
> doesn't it?
>
> Armin
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
>
Hi,
Booting Slink with Linux 2.2.5 kernel I get the message
SIOCADDRT: Invalid argument
after mounting the file systems. What does this mean? Looks like an error,
doesn't it?
Armin
chives" on the map to the left. From
there, you find the April 1999 debian-user, and search for SIOCADDRT (using
alt-f in netscape or / in lynx). You'll find it in the third page of
debian-user for this month. You can find two specific fixes on that page,
mine (http://www.debian.org/Lists
On Sat, 17 Apr 1999, Chad A. Adlawan wrote:
> hi Vaidhy,
> i also got the same error as u guys did, that is, i got it after i
> upgraded from 2.0.36 to 2.2.4. do u think that same fix'll still work for
> me ? i dont feel too comfortable removing some lines from my init.d/network
> because thou
t; > >
> > > > On Fri, Apr 16, 1999 at 09:15:37PM -0400, Chris Brown wrote:
> > > > > Greetings,
> > > > > I'm cleaning up the boot messages of a system we're moving to
> > > > > another location, and I ran into a funny mes
t; > On Fri, Apr 16, 1999 at 09:15:37PM -0400, Chris Brown wrote:
> > > > Greetings,
> > > > I'm cleaning up the boot messages of a system we're moving to
> > > > another location, and I ran into a funny message. When the system
> > > >
I'm cleaning up the boot messages of a system we're moving to
> > > another location, and I ran into a funny message. When the system
> > > boots everything looks OK until It mounts the local filesystems. I
> > > get this weird error,
> > > &qu
I'm cleaning up the boot messages of a system we're moving to
> > another location, and I ran into a funny message. When the system
> > boots everything looks OK until It mounts the local filesystems. I
> > get this weird error,
> > "SIOCADDRT: In
ssages of a system we're moving to
> another location, and I ran into a funny message. When the system
> boots everything looks OK until It mounts the local filesystems. I
> get this weird error,
> "SIOCADDRT: Invalid argument"
> twice, and then it mov
Greetings,
I'm cleaning up the boot messages of a system we're moving to
another location, and I ran into a funny message. When the system
boots everything looks OK until It mounts the local filesystems. I
get this weird error,
"SIOCADDRT: Invalid argument"
twice,
Subject: Help for error: "SIOCADDRT: Invalid argument."
Date: Sat, Apr 10, 1999 at 07:58:40PM +0200
In reply to:Norbert Nemec
Quoting Norbert Nemec([EMAIL PROTECTED]):
> Hi out there,
>
> I've been trying to compile kernel 2.2.1 for several machines in o
James Mastros wrote:
> On Sat, Apr 10, 1999 at 07:58:40PM +0200, Norbert Nemec wrote:
> > I've been trying to compile kernel 2.2.1 for several machines in our small
> > network. Now, some computers bring the message above during bootup at
> > the command:
> > route add -net 127.0.0.0
> > (in
On Sat, Apr 10, 1999 at 07:58:40PM +0200, Norbert Nemec wrote:
> I've been trying to compile kernel 2.2.1 for several machines in our small
> network. Now, some computers bring the message above during bootup at
> the command:
> route add -net 127.0.0.0
> (in /etc/init.d/network)
The simple
Hi out there,
I've been trying to compile kernel 2.2.1 for several machines in our small
network. Now, some computers bring the message above during bootup at
the command:
route add -net 127.0.0.0
(in /etc/init.d/network)
After that, the IP-network is not working fully. (Parts, like nfs
On Thu, 18 Mar 1999, Asokan P wrote:
> My machine has suddenly started displaying this message
> SIOCADDRT - invalid argument.
You would have noticed this message after putting the kernel 2.2.X.In
these kernels the route add command is not needed.So remove this line from
/etc/netwo
"Asokan P" <[EMAIL PROTECTED]> writes:
> My machine has suddenly started displaying this message
> SIOCADDRT - invalid argument.
> The network card is dtected and while booting up it shows up correctly
> I traced it to the two route commands in /etc/inet.d/network
>
On Thu, 18 Mar 1999, Asokan P wrote:
> My machine has suddenly started displaying this message
> SIOCADDRT - invalid argument.
> The network card is dtected and while booting up it shows up correctly
> I traced it to the two route commands in /etc/inet.d/network
> They are corre
My machine has suddenly started displaying this message
SIOCADDRT - invalid argument.
The network card is dtected and while booting up it shows up correctly
I traced it to the two route commands in /etc/inet.d/network
They are correct - as per the man, ifconfig looks alright
ping 192.168.3.208
0.0.1
> route add -net 127.0.0.0
> I get
> SIOCADDRT: Invalid argument
>
> When I type
> IPADDR=192.168.0.4
> NETMASK=255.255.255.0
> NETWORK=192.168.0.0
> BROADCAST=192.168.0.255
> GATEWAY=192.168.0.4
> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROA
On 08-Mar-99 Oz Dror wrote:
> When I type
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
> I get
> SIOCADDRT: Invalid argument
>
2.2.x (and later 2.1.x) kernels do not need route statements. Unless you have
to set a gateway that is non-obvious.
When I type
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
I get
SIOCADDRT: Invalid argument
When I type
IPADDR=192.168.0.4
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
GATEWAY=192.168.0.4
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net
*- On 9 Feb, Ed Cogburn wrote about "[SOLVED] Re: Kernel 2.2.1: SIOCADDRT:
Invalid argument ?"
> "Ralf G. R. Bergs" wrote:
>>
>> On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
>>
>> > route add -net 127.0.0.0
>> >
>&
"Ralf G. R. Bergs" wrote:
>
> On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
>
> > route add -net 127.0.0.0
> >
> > Its the route command thats generating the "SIOCADDRT: Invalid
> >argument". I'm up to date with potat
On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
> route add -net 127.0.0.0
>
> Its the route command thats generating the "SIOCADDRT: Invalid
>argument". I'm up to date with potato, (I got the kernel deb from
>there) so what could this be?
The
*- On 9 Feb, Ed Cogburn wrote about "Kernel 2.2.1: SIOCADDRT: Invalid
argument ?"
>
>
> After upgrading to the 2.2.1 kernel, I now get an error during
> bootup. I narrowed it to /etc/init.d/network:
>
> ifconfig lo 127.0.0.1
> route add -n
After upgrading to the 2.2.1 kernel, I now get an error during
bootup. I narrowed it to /etc/init.d/network:
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
Its the route command thats generating the "SIOCADDRT: Invalid
argument". I'm up to date
Are you running a 2.1.x kernel? If so comment out the route commands in
/etc/init.d/network and read linux/Documentation/Changes in the kernel
source.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lindsay Allen <[EMAIL PROTECTED]> Perth, Western Australia
voice +61 8
I also get this error message on boot. The route command seems to be
broken, as the route manpage syntax will not add the loopback route
and generates this message. Don't know enough about it to tell exactly
what is broken (package-wise).
--
Eddie Seymour, WB4MLE
E-Mail [EMAIL PROTECTED]
PGP KE
hi
i keep on getting the message "SIOCADDRT: Invalid argument" on bootup since
i started using 2.1.x. i traced the message to this line in
/etc/init.d/network:
route add -net 127.0.0.0
now, will commenting out this line have any untoward effects? if so, can i
upgrade to a later
masqueraded.
ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
When I run "route add default ppp0", I get an error message, "SIOCADDRT:
Operation not supported by device" ... how can I fix this?
I'm using kernel 2.0.34, ip masquerading is built in and running on eth0
--&g
> >> May 21 13:15:07 muso pppd[1020]: rcvd [IPCP ConfReq id=0x6 >> 00> ]
> >> May 21 13:15:07 muso pppd[1020]: sent [IPCP ConfRej id=0x6 >> 195.64.64.1>]
> >> May 21 13:15:07 muso pppd[1020]: rcvd [IPCP ConfReq id=0x7 >> 195.64.64.1 195.64.69.173> ]
> >> May 21 13:15:07 muso pppd[1020]: sent [I
e "noipdefault" option
for ppp.
--j
>> May 21 13:15:07 muso pppd[1020]: sent [IPCP ConfAck id=0x8 > 00>]
>> May 21 13:15:07 muso pppd[1020]: ioctl(SIOCADDRT) device route: Network is
>> down(100)
>> May 21 13:15:07 muso pppd[1020]: sent [IPCP
Hello Joost,
You will most likely get more expert advice than I can offer, but this
might help.
muso
The two ends agree that muso is to be 195.64.69.173. The remote wants to
be 195.64.64.1 but muso declines. No IP number is negotiated and the
connection fails.
stelo
negotiates
Mar 19 12:0
pppd[1020]: sent [IPCP ConfRej id=0x7 ]
May 21 13:15:07 muso pppd[1020]: rcvd [IPCP ConfReq id=0x8 ]
May 21 13:15:07 muso pppd[1020]: sent [IPCP ConfAck id=0x8 ]
May 21 13:15:07 muso pppd[1020]: ioctl(SIOCADDRT) device route: Network is
down(100)
May 21 13:15:07 muso pppd[1020]: sent [IPCP TermReq i
93 matches
Mail list logo
