On 14/6/18 7:44 am, Jeff Kletsky wrote:
On 6/13/18 1:28 PM, Andrey V. Elsukov wrote:
On 13.06.2018 23:04, Jeff Kletsky wrote:
The kernel version of libalias uses m_megapullup() function to make
single contiguous buffer. m_megapullup() uses m_get2() function to
allocate mbuf of appropriate siz
On 14/6/18 3:01 am, Andrey V. Elsukov wrote:
On 13.06.2018 20:16, Jeff Kletsky wrote:
When a T-Mobile "femto-cell" is trying to establish its IPv4, IPSEC
tunnel to the T-Mobile provisioning servers, the reassembled, 4640-byte
return packet is silently dropped by the in-kernel NAT, even though it
On 14/6/18 1:41 am, Michael Sierchio wrote:
I see you have a case of Netgraph. Perhaps Julian will chime in.
well I'm reading but not got any specific ideas at the moment..
Netgraph itself has no requirements on packet size or even contents.
a node may however have some.
On Wed, Jun 13, 2018
On 6/13/18 1:28 PM, Andrey V. Elsukov wrote:
On 13.06.2018 23:04, Jeff Kletsky wrote:
The kernel version of libalias uses m_megapullup() function to make
single contiguous buffer. m_megapullup() uses m_get2() function to
allocate mbuf of appropriate size. If size of packet greater than 4k it
w
On 13.06.2018 23:04, Jeff Kletsky wrote:
>> The kernel version of libalias uses m_megapullup() function to make
>> single contiguous buffer. m_megapullup() uses m_get2() function to
>> allocate mbuf of appropriate size. If size of packet greater than 4k it
>> will fail. So, if you use MTU greater t
On 6/13/18 12:01 PM, Andrey V. Elsukov wrote:
On 13.06.2018 20:16, Jeff Kletsky wrote:
When a T-Mobile "femto-cell" is trying to establish its IPv4, IPSEC
tunnel to the T-Mobile provisioning servers, the reassembled, 4640-byte
return packet is silently dropped by the in-kernel NAT, even though
On 13.06.2018 20:16, Jeff Kletsky wrote:
> When a T-Mobile "femto-cell" is trying to establish its IPv4, IPSEC
> tunnel to the T-Mobile provisioning servers, the reassembled, 4640-byte
> return packet is silently dropped by the in-kernel NAT, even though it
> "matches" the outbound packet from less
I see you have a case of Netgraph. Perhaps Julian will chime in.
On Wed, Jun 13, 2018 at 10:32 AM, Jeff Kletsky wrote:
> On 6/13/18 10:22 AM, Michael Sierchio wrote:
>
> On Wed, Jun 13, 2018 at 10:16 AM, Jeff Kletsky wrote:
>>
>> When a T-Mobile "femto-cell" is trying to establish its IPv4, IPS
On 6/13/18 10:22 AM, Michael Sierchio wrote:
On Wed, Jun 13, 2018 at 10:16 AM, Jeff Kletsky wrote:
When a T-Mobile "femto-cell" is trying to establish its IPv4, IPSEC tunnel
to the T-Mobile provisioning servers, the reassembled, 4640-byte return
packet is silently dropped by the in-kernel NAT
On Wed, Jun 13, 2018 at 10:16 AM, Jeff Kletsky wrote:
When a T-Mobile "femto-cell" is trying to establish its IPv4, IPSEC tunnel
> to the T-Mobile provisioning servers, the reassembled, 4640-byte return
> packet is silently dropped by the in-kernel NAT, even though it "matches"
> the outbound pac
10 matches
Mail list logo
