Re: [l2tpns-devel] dhcp mechanism??

[Brendan O'D. <bo...@c4...>]

Most of these are warnings which you may ignore.  The problem appears
to be that the inclusion of syslog.h no longer works if it occurs
before stdio.h.  The Debian package is patched for this:

  http://sources.debian.net/patches/patch/l2tpns/2.2.1-1/02-fix-syslog-null.patch/

You can either apply that patch, or use the Debian source:

  apt-get source l2tpns

On 23 October 2015 at 00:00, ve2cii <ve...@ve...> wrote:
>     Hi,
>
>    I tried to compile it on a debian-7 machine and it won't compile.  I have
> attached the errors.
> It could be I am missing a dependency?
>
>
> On 10/15/2015 09:21 PM, Brendan O'Dea wrote:
>>
>> On 15 October 2015 at 03:46, ve2cii <ve...@ve...> wrote:
>>>
>>>       Ahh thank you.  Here is what we have run into:
>>>
>>> In the startup file we played with the MTU and set it to max:
>>>
>>>   From the startup-config file:
>>>
>>> set l2tp_mtu 1622    (no matter what we set the mtu to it is always the
>>> same for the tunnel 1492)
>>>
>>> And the tun0 is showing 1492
>>>
>>> tun0      Link encap:UNSPEC  HWaddr
>>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>>>             inet addr:67.69.22.58  P-t-P:67.69.22.58 Mask:255.255.255.255
>>>             UP POINTOPOINT RUNNING  MTU:1492  Metric:1
>>>             RX packets:9102759304 errors:0 dropped:0 overruns:0 frame:0
>>>             TX packets:13962497099 errors:0 dropped:2230 overruns:0
>>> carrier:0
>>>             collisions:0 txqueuelen:1000
>>>             RX bytes:2053780927070 (2.0 TB)  TX bytes:17062940820040
>>> (17.0 TB)
>>
>> Ah.  There is code in there to limit the MRU to 1492.  At the time I
>> did that, we were running on machines with 1500 MTU interfaces and all
>> the customers were running PPPoE, so I've really no experience testing
>> anything higher.
>>
>> The relevant code is in l2tpns.c, lines 4683 and 2684:
>>
>>      if (MRU > PPPoE_MRU)
>>              MRU = PPPoE_MRU;
>>
>> where PPPoE_MRU is defined in l2tpns.h as 1492.
>>
>> You could try commenting out those two lines and testing perhaps.
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> L2tpns-devel mailing list
>> L2t...@li...
>> https://lists.sourceforge.net/lists/listinfo/l2tpns-devel
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> L2tpns-devel mailing list
> L2t...@li...
> https://lists.sourceforge.net/lists/listinfo/l2tpns-devel
>