Skip to contentSkip to conversation

ipq_set_verdict problem in bridge+iptables

DISCUSSION Yong Li 2 participants 3 messages Jul 13, 2003 – Jul 15, 2003 2 messages not in the archive netfilter

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 20030712222620.28732.48265.Mailman@kashyyyk

Yong Li

author
#1 lore raw

Hello All,

I encountered a problem with the ipq_set_verdict function. I want to modify the packet content and size using the ipq_set_verdict function. However, I found I cannot change the IP packet size more than 400+ bytes. Is it a known issue?

Thanks in advance!

Yong

#2 lore raw
Quoted 6 lines · Yong Li

Hello All,

I encountered a problem with the ipq_set_verdict function. I want to modify the packet content and size using the ipq_set_verdict function. However, I found I cannot change the IP packet size more than 400+ bytes. Is it a known issue?

what do you mean by 'I cannot' ? What happens? Is an error returned to the ipq_set_verdict() call? Is the packet silently discarded? Is the packet truncated?

Anyway, it should work. But if you exceed the outgoing interface's MTU, I could imagine that no fragmentation happens...

Quoted 2 lines

Thanks in advance!
Yong

Signature · 5 lines
- Harald Welte <[email protected]>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

A message that is not in the archive (sent off-list or not yet received): 001c01c34a6f$97af4fe0$8501a8c0@dev

author
#4 lore raw

----- Original Message -----
From: "Yong" <[email protected]>
To: "Harald Welte" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, July 15, 2003 9:22 AM
Subject: Re: ipq_set_verdict problem in bridge+iptables

Quoted 40 lines

Hello Harald,

Thank you for your emails!

I want to use the iptable_queue in bridge+iptables environment. I can get the packet in userspace using -j QUEUE command. However, If I change the packet size. for example, I change the ping icmp packet size to 400, the packet Ethernet header is changed. In my test, the MAC address is changed to 0xffffffffff. I can capture this packet using sniffer tool. Since the MAC address is changed, the other computer cannot receive the ICMP packet.

It seems that the bridge iptables patch changed something in the function ipq_set_verdict().

Regarding the MTU issue, you are right. the ipq_set_verdict function does not perform the IP fragment. If I send a packet larger than MTU, it is missing. Is it by design?

Can I modify the ipq_set_verdict function to perform the IP fragment? Is there any patch for this IP fragment issue?

Thank you again for your help!

Yong

----- Original Message -----
From: "Harald Welte" <[email protected]>
To: "Yong Li" <[email protected]>
Cc: <[email protected]>
Sent: Monday, July 14, 2003 4:07 PM
Subject: Re: ipq_set_verdict problem in bridge+iptables

Quoted 6 lines · Yong Li

Hello All,

I encountered a problem with the ipq_set_verdict function. I want to modify the packet content and size using the ipq_set_verdict function. However, I found I cannot change the IP packet size more than 400+ bytes. Is it a known issue?

what do you mean by 'I cannot' ? What happens? Is an error returned to the ipq_set_verdict() call? Is the packet silently discarded? Is the packet truncated?

Anyway, it should work. But if you exceed the outgoing interface's MTU, I could imagine that no fragmentation happens...

Quoted 2 lines

Thanks in advance!
Yong