he means Apipa...
http://compnetworking.about.com/cs/protocolsdhcp/g/bldef_apipa.htm
as soon as something starts with 169.x.y.z I guess.. netmask 255.0.0.0
2007/9/22, Marek Lindner :
>
> Am Samstag, 22. September 2007 21:41:21 schrieb a.anse...@oltrelinux.com:
> > >> Still remain the minor proble
Am Samstag, 22. September 2007 21:41:21 schrieb a.anse...@oltrelinux.com:
> >> Still remain the minor problem in arrangement of IPIPA subnet mask:
> >> 169.254.0.0/16 on clients
> >> 169.254.0.0/24 on gateway
> >
> > I don't know where you can see that. The tun interface is a point to > >
> > point
>> Still remain the minor problem in arrangement of IPIPA subnet mask:
>> 169.254.0.0/16 on clients
>> 169.254.0.0/24 on gateway
>
> I don't know where you can see that. The tun interface is a point to > >
> point connection ...
...sure, it was a safe-IP on my router which cause that messages abou
Am Samstag, 22. September 2007 20:00:04 schrieb a.anse...@oltrelinux.com:
> great work Marek,
> now client can ping outside mesh obtaining the correct IP from gateway.
> Thanks!
God. This makes the weekend even better. ;-)
> Still remain the minor problem in arrangement of IPIPA subnet mask
great work Marek,
now client can ping outside mesh obtaining the correct IP from gateway.
Thanks!
Still remain the minor problem in arrangement of IPIPA subnet mask:
169.254.0.0/16 on clients
169.254.0.0/24 on gateway
Have a fine weekend
--
Antonio
space (line 2-log_gateway): suffix
> Hi,
>
>
Hi,
> since you use mipsel device I think these mips log could be of more help
> in fixing mips/mipsel bug in 0.3 branches (alpha and experimental).
> Hopeing this will be usefull... I know today weekend begins :)
thanks a lot for your thorough description - it did help. :-)
Since the weekend
Hi,
since you use mipsel device I think these mips log could be of more help
in fixing mips/mipsel bug in 0.3 branches (alpha and experimental).
Very simple scenario:
[client 5.1.7.251]mesh[gateway 5.1.7.254]
all node running 0.3 apha (the today latest rv6300.3-alpha)
# d3 level debug