Subject: Re: gre tunneling causing predictable reboot
To: Heiko Rupp <email@example.com>
From: None <firstname.lastname@example.org>
Date: 04/27/2001 23:31:48
>> scripts. For some reason, I had put the greconfig line before the
>> ifconfig line. Restoring the order of theese two lines cleared up the
>> problem. This seems very strange to me, and I have no idea how to debug a
>> problem like this.
>If I recall correctly, you need to have the ifconfig (and especially a
>to the remote network) first in order to have the tunnel route calculated
>Perhaps I should look at the gif code, how the route is calculated there and
>gre accordingly when I get a modem running under NetBSD again. Also there is
>new RFC on GRE, that updates RFC1701/2 a bit.
if it is permitted to break existing configuration, i would suggest
redesigning gre(4) to take SIOCSIFPHYADDR, and split outer header
address pair configuration from inner pair. just like gif(4) does.
there still are possibilities for routing loop within the kernel,
however, it is much easier to configure/debug the tunnelling interface
this way. (and we can get rid of greconfig(8)!)
the current configuration twist is there because gre(4) reuses
interface address configuration to decide outer header address pair.
outer header address pair should not be mixed up with interface address