db26 IPv6 + PF + packet loss - The FreeBSD Forums
The FreeBSD Forums  

Go Back   The FreeBSD Forums > Server & Networking > Networking

Networking Network related discussions (including general TCP/IP stuff, routing, etc).

Reply
 
Thread Tools Display Modes
  #1  
Old February 24th, 2012, 09:45
folivora folivora is offline
Junior Member
 
Join Date: Sep 2010
Location: Finland
Posts: 94
Thanks: 7
Thanked 2 Times in 2 Posts
Default IPv6 + PF + packet loss

Hi,

I have been trying to use IPv6, but it seems that somehow PF is giving me packet loss.

This is my IPv6 part of my pf.conf

Code:
ext_if="2001:1bxx:1xx:xxxx::x"

block in all

##IPV6

# all ping request allowed out
pass out on $ext_if inet6 proto icmp6 all icmp6-type echoreq keep state

pass out on $ext_if inet6 proto icmp6 all icmp6-type {neighbradv, neighbrsol}

pass in on $ext_if inet6 proto icmp6 all icmp6-type {neighbradv, neighbrsol}
And I see this packet loss:

Code:
ipv6_test:~# ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2001:1bc8:1xx:xxxx::x --> 2a00:1450:4016:801::1012
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=10 hlim=56 time=2971.819 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=11 hlim=56 time=1970.965 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=12 hlim=56 time=971.709 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=13 hlim=56 time=52.543 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=14 hlim=56 time=88.075 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=15 hlim=56 time=52.735 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=16 hlim=56 time=52.692 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=17 hlim=56 time=52.248 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=18 hlim=56 time=118.079 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=19 hlim=56 time=66.114 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=20 hlim=56 time=52.880 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=21 hlim=56 time=52.699 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=22 hlim=56 time=52.338 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=23 hlim=56 time=81.143 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=24 hlim=56 time=52.326 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=25 hlim=56 time=156.092 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=26 hlim=56 time=52.666 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=27 hlim=56 time=53.421 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=38 hlim=56 time=3969.212 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=39 hlim=56 time=2969.969 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=40 hlim=56 time=1969.710 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=41 hlim=56 time=969.471 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=42 hlim=56 time=52.460 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=43 hlim=56 time=72.027 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=44 hlim=56 time=53.288 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=45 hlim=56 time=90.556 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=46 hlim=56 time=52.152 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=47 hlim=56 time=163.019 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=48 hlim=56 time=52.498 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=49 hlim=56 time=53.003 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=50 hlim=56 time=52.539 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=51 hlim=56 time=52.365 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=52 hlim=56 time=52.374 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=53 hlim=56 time=52.188 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=54 hlim=56 time=52.480 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=55 hlim=56 time=52.512 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=56 hlim=56 time=52.345 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=67 hlim=56 time=3968.739 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=68 hlim=56 time=2968.507 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=69 hlim=56 time=1969.249 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=70 hlim=56 time=968.998 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=71 hlim=56 time=52.932 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=72 hlim=56 time=52.441 ms
16 bytes from 2a00:1450:4016:801::1012, icmp_seq=73 hlim=56 time=97.017 ms
^C
--- ipv6.l.google.com ping6 statistics ---
74 packets transmitted, 44 packets received, 40.5% packet loss
round-trip min/avg/max/std-dev = 52.152/633.241/3969.212/1117.673 ms
As you can see that the same "lag" comes up, in certain periods.

I have configured also these options for ipv6 in my rc.conf

Code:
ipv6_enable="YES"
ipv6_network_interface="re0"
ipv6_defaultrouter="2001:1bxx:1xx:xxxx::x"
Am I missing some settings for ipv6 in my pf.conf?

-folivora
__________________
"Thousands of candles can be lighted from a single candle, and the life of the candle will not be shortened. Happiness never decreases by being shared" -- Buddha --

Last edited by DutchDaemon; February 24th, 2012 at 17:35.
Reply With Quote
  #2  
Old February 24th, 2012, 10:44
razrx's Avatar
razrx razrx is offline
Junior Member
 
Join Date: Apr 2009
Location: Holland
Posts: 22
Thanks: 0
Thanked 4 Times in 3 Posts
Default

Quote:
Originally Posted by folivora View Post
Am I missing some settings for ipv6 in my pf.conf?

-folivora
Are you also experiencing the packet loss with pf(4) switched off?
__________________
Proud recurring donor of the FreeBSD Foundation.

Last edited by DutchDaemon; February 24th, 2012 at 17:35.
Reply With Quote
  #3  
Old February 24th, 2012, 10:50
SirDice's Avatar
SirDice SirDice is offline
Moderator
 
Join Date: Nov 2008
Location: Rotterdam, Netherlands
Posts: 13,725
Thanks: 47
Thanked 2,023 Times in 1,862 Posts
Default

Yes, that would be my suggestion too. It looks like the packet loss and the large latencies are caused outside of your network.
__________________
Senior UNIX Engineer at Unix Support Nederland
Experience is something you don't get until just after you need it.
Reply With Quote
  #4  
Old February 24th, 2012, 12:47
OH OH is offline
Member
 
Join Date: Aug 2009
Location: The Netherlands
Posts: 208
Thanks: 4
Thanked 31 Times in 27 Posts
Default

You can always try a traceroute6(8) to find out where the delay happens. Note the -I option.

Last edited by OH; February 24th, 2012 at 12:52. Reason: Fix man
Reply With Quote
  #5  
Old February 24th, 2012, 16:38
RusDyr RusDyr is offline
Junior Member
 
Join Date: Nov 2011
Location: St.Petersburg, Russia
Posts: 78
Thanks: 5
Thanked 8 Times in 8 Posts
Default

Or even better see net/mtr.
Reply With Quote
Reply

Tags
ipv6, pf

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
packet loss in IPFW atwinix Firewalls 0 June 24th, 2011 10:36
[Solved] loss of IPv6 default route su27 Networking 6 February 15th, 2011 17:20
pf on FreeBSD 8 is causing packet loss on connections over IPv6 rmo Firewalls 1 May 30th, 2010 01:13
Packet loss... laneo Networking 3 November 6th, 2009 02:27
IPv6 DAD disables IPv6 Traffic, how to turn IPv6 back on? benzh512 Networking 6 March 10th, 2009 16:57


All times are GMT +1. The time now is 21:56.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.
The mark FreeBSD is a registered trademark of The FreeBSD Foundation and is used by The FreeBSD Project with the permission of The FreeBSD Foundation.
Web protection and acceleration provided by CloudFlare
0