Re: mpd5/Netgraph issues after upgrading to 7.4

[Przemyslaw Frasunek]

>> I've seen that Mike reported similar issues in October
>> (http://lists.freebsd.org/pipermail/freebsd-stable/2013-October/075552.html).
>> Did you managed to resolve it?
> I worked around the crash by removing ipv6 from the kernel.  The box has
> been functioning without a crash since then.

Hi,

FYI -- after upgrade to 9-STABLE no further crashes occurred, even with IPv6
enabled.

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: mpd5/Netgraph issues after upgrading to 7.4

[Mike Tancsa]

On 3/9/2014 7:33 AM, Przemyslaw Frasunek wrote:

I've seen that Mike reported similar issues in October
(http://lists.freebsd.org/pipermail/freebsd-stable/2013-October/075552.html).
Did you managed to resolve it?

 I worked around the crash by removing ipv6 from the kernel.  The box has
been functioning without a crash since then.


Hi,

FYI -- after upgrade to 9-STABLE no further crashes occurred, even with IPv6
enabled.


What sort of uptime have you seen with ipv6 enabled ?

---Mike



--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: kern/187341: [netinet] [patch] CARP addresses in backup state should't be used as source

[linimon]

Old Synopsis: CARP addresses in backup state should't be used as source
New Synopsis: [netinet] [patch] CARP addresses in backup state should't be used 
as source

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Mar 9 15:37:50 UTC 2014
Responsible-Changed-Why: 
reclassify.

http://www.freebsd.org/cgi/query-pr.cgi?pr=187341
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: kern/187194: Server hangs if -arp is present on an IP address

[linimon]

Synopsis: Server hangs if -arp is present on an IP address

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Mar 9 15:39:18 UTC 2014
Responsible-Changed-Why: 
reclassify.

http://www.freebsd.org/cgi/query-pr.cgi?pr=187194
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: LAN network performance issues

[Kevin Oberman]

On Fri, Mar 7, 2014 at 2:57 PM, jcv  wrote:

>
>
> On Fri, 7 Mar 2014, John Baldwin wrote:
>
>  On Friday, March 07, 2014 12:17:05 am jcv wrote:
>>
>>> Hi - I am seeing some strange IPERF results.. Everything goes through my
>>> WIFI/GIGABIT router.
>>>
>>> For these tests everything is plugged directly into the router via
>>> Ethernet cable.
>>>
>>> My issue is the transfer rate from Windows to FreeBSD.
>>>
>>> There are 3 different computers in this lab running 3 different OS.
>>>
>>> Here are the results:
>>>
>>>
>>>
>>> FreeBSD as server:
>>>
>>> [vic@yeaguy ~] iperf -s
>>> 
>>> Server listening on TCP port 5001
>>> TCP window size: 64.0 KByte (default)
>>> 
>>>
>>>
>>> [  4] local 192.168.1.3 port 5001 connected with 192.168.1.8 port 52505
>>> [ ID] Interval   Transfer Bandwidth
>>> [  4]  0.0-10.1 sec   157 MBytes  131 Mbits/sec <- WINDOWS 8.1 as
>>> client on same LAN/ROUTER
>>>
>>>
>>>
>>>
>>> [  5] local 192.168.1.3 port 5001 connected with 192.168.1.12 port 60926
>>> [  5]  0.0-10.0 sec  1.10 GBytes   941 Mbits/sec <-- MACBOOK PRO as
>>> client on same LAN/ROUTER
>>>
>>>
>>> Windows as the server:
>>>
>>> 
>>> Server listening on TCP port 5001
>>> TCP window size: 64.0 KByte (default)
>>> 
>>> [  4] local 192.168.1.8 port 5001 connected with 192.168.1.3 port 60529
>>> [ ID] Interval   Transfer Bandwidth
>>> [  4]  0.0-10.0 sec  1014 MBytes   850 Mbits/sec <- Freebsd 10 as
>>> client on same LAN/ROUTER
>>>
>>>
>>>
>>> [  4] local 192.168.1.8 port 5001 connected with 192.168.1.12 port 60933
>>> [  4]  0.0-10.0 sec  1.08 GBytes   931 Mbits/sec <-- MACBOOK PRO as
>>> client on same LAN/ROUTER
>>>
>>>
>>>
>>> Macbook Pro as the server:
>>>
>>> [  3] local 192.168.1.8 port 52509 connected with 192.168.1.12 port 5001
>>> [ ID] Interval   Transfer Bandwidth
>>> [  3]  0.0-10.0 sec   823 MBytes   690 Mbits/sec <-- WINDOWS 8.1 as
>>> client on same LAN/ROUTER
>>>
>>> [  3] local 192.168.1.3 port 23190 connected with 192.168.1.12 port 5001
>>> [ ID] Interval   Transfer Bandwidth
>>> [  3]  0.0-10.0 sec  1016 MBytes   852 Mbits/sec <-- Freebsd 10 as
>>> client on same LAN/ROUTER
>>>
>>>
>>> With FreeBSD being the server, Windows transfer to FreeBSD is slow,
>>> compared to Macbook to FreeBSD transfer..
>>> With Windows as the server, FreeBSD and Macbook to Windows transfer is
>>> great.
>>> With Macbook as server, Windows and FreeBSD transfer is good.
>>>
>>> The only bad transfer is Windows to FreeBSD. Windows transfer to Mac is
>>> good. Cant really blame Windows for the poor transfer to FreeBSD then.
>>> Macbook to FreeBSD is outstanding, cant really blame FreeBSD for poor
>>> receive performance.
>>>
>>
>> Can you tell us more about the FreeBSD box such as the NIC being used?
>>
>> --
>> John Baldwin
>> ___
>> freebsd-net@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>>
>>
>
> Sure John --
>
> Here is the fbsd nic info:
>
> [vic@yeaguy ~] cat /var/run/dmesg.boot | grep re0
> re0:  port
> 0xe800-0xe8ff mem 0xfdfff000-0xfdff,0xfdff8000-0xfdffbfff irq 18 at
> device 0.0 on pci3
> re0: Using 1 MSI-X message
> re0: Chip rev. 0x4800
> re0: MAC rev. 0x
> miibus0:  on re0
> re0: Ethernet address: d8:50:e6:ba:c8:99
>
>
>
> [vic@yeaguy ~] ifconfig
> re0: flags=8843 metric 0 mtu 1500
>
> options=8209b HWCSUM,WOL_MAGIC,LINKSTATE>
> ether d8:50:e6:ba:c8:99
> inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255
> inet6 fe80::da50:e6ff:feba:c899%re0 prefixlen 64 scopeid 0x1
> nd6 options=29
> media: Ethernet autoselect (1000baseT )
> status: active
> lo0: flags=8049 metric 0 mtu 16384
> options=63
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> inet 127.0.0.1 netmask 0xff00
> nd6 options=21
> [vic@yeaguy ~]
>
> I tried to remove rxcsum and txcsum, but that didnt really improve the
> behavior I almost convinced its a iperf issue? maybe.. after iperf
> testing i did a FTP transfer and it exceeded what iperf is claiming the
> throughput is..  so im not sure what to make of it.
>

You might try installing iperf3 and testing with that. iperf3 is a major
rewrite of iperf and is totally incompatible  with the older version, so
you will need to install iperf3 on all systems

I doubt iperf is the issue,  but this is a way to check.
-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs

Re: LAN network performance issues

[justin victoria]

On 3/9/2014 10:40 AM, Kevin Oberman wrote:
On Fri, Mar 7, 2014 at 2:57 PM, jcv > wrote:




On Fri, 7 Mar 2014, John Baldwin wrote:

On Friday, March 07, 2014 12:17:05 am jcv wrote:

Hi - I am seeing some strange IPERF results.. Everything
goes through my
WIFI/GIGABIT router.

For these tests everything is plugged directly into the
router via
Ethernet cable.

My issue is the transfer rate from Windows to FreeBSD.

There are 3 different computers in this lab running 3
different OS.

Here are the results:



FreeBSD as server:

[vic@yeaguy ~] iperf -s

Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)



[  4] local 192.168.1.3 port 5001 connected with
192.168.1.8 port 52505
[ ID] Interval   Transfer Bandwidth
[  4]  0.0-10.1 sec   157 MBytes  131 Mbits/sec <-
WINDOWS 8.1 as
client on same LAN/ROUTER




[  5] local 192.168.1.3 port 5001 connected with
192.168.1.12 port 60926
[  5]  0.0-10.0 sec  1.10 GBytes   941 Mbits/sec <--
MACBOOK PRO as
client on same LAN/ROUTER


Windows as the server:


Server listening on TCP port 5001
TCP window size: 64.0 KByte (default)

[  4] local 192.168.1.8 port 5001 connected with
192.168.1.3 port 60529
[ ID] Interval   Transfer Bandwidth
[  4]  0.0-10.0 sec  1014 MBytes   850 Mbits/sec
<- Freebsd 10 as
client on same LAN/ROUTER



[  4] local 192.168.1.8 port 5001 connected with
192.168.1.12 port 60933
[  4]  0.0-10.0 sec  1.08 GBytes   931 Mbits/sec <--
MACBOOK PRO as
client on same LAN/ROUTER



Macbook Pro as the server:

[  3] local 192.168.1.8 port 52509 connected with
192.168.1.12 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-10.0 sec   823 MBytes   690 Mbits/sec <--
WINDOWS 8.1 as
client on same LAN/ROUTER

[  3] local 192.168.1.3 port 23190 connected with
192.168.1.12 port 5001
[ ID] Interval   Transfer Bandwidth
[  3]  0.0-10.0 sec  1016 MBytes   852 Mbits/sec <--
Freebsd 10 as
client on same LAN/ROUTER


With FreeBSD being the server, Windows transfer to FreeBSD
is slow,
compared to Macbook to FreeBSD transfer..
With Windows as the server, FreeBSD and Macbook to Windows
transfer is
great.
With Macbook as server, Windows and FreeBSD transfer is good.

The only bad transfer is Windows to FreeBSD. Windows
transfer to Mac is
good. Cant really blame Windows for the poor transfer to
FreeBSD then.
Macbook to FreeBSD is outstanding, cant really blame
FreeBSD for poor
receive performance.


Can you tell us more about the FreeBSD box such as the NIC
being used?

-- 
John Baldwin

___
freebsd-net@freebsd.org 
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
"



Sure John --

Here is the fbsd nic info:

[vic@yeaguy ~] cat /var/run/dmesg.boot | grep re0
re0: 
port 0xe800-0xe8ff mem 0xfdfff000-0xfdff,0xfdff8000-0xfdffbfff
irq 18 at device 0.0 on pci3
re0: Using 1 MSI-X message
re0: Chip rev. 0x4800
re0: MAC rev. 0x
miibus0:  on re0
re0: Ethernet address: d8:50:e6:ba:c8:99



[vic@yeaguy ~] ifconfig
re0: flags=8843 metric 0
mtu 1500


options=8209b
ether d8:50:e6:ba:c8:99
inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255
inet6 fe80::da50:e6ff:feba:c899%re0 prefixlen 64 scopeid 0x1
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active
lo0: flags=8049 metric 0 mtu 16384
options=63
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000

Using pf.conf with public access points.

[Joe Nosay]

My pf.conf is attached. I would like to know:
1. Is everything set up properly?
2. How do I compensate for the use of public access points when the IP
addresses will always be different?


pf.conf
Description: Binary data
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: LAN network performance issues

[Kevin Oberman]

On Sun, Mar 9, 2014 at 11:44 AM, justin victoria  wrote:

>
> On 3/9/2014 10:40 AM, Kevin Oberman wrote:
>
> You might try installing iperf3 and testing with that. iperf3 is a major
> rewrite of iperf and is totally incompatible  with the older version, so
> you will need to install iperf3 on all systems
>
> I doubt iperf is the issue,  but this is a way to check.
>  --
> R. Kevin Oberman, Network Engineer, Retired
> E-mail: rkober...@gmail.com
>
>
> iperf3 on windows isnt playing nice..
>

Can you provide more details on the problem on Windows? I know the primary
developer of iperf3 (who also maintains iperf2) and would like to be sure
he is aware of any and all problems on any platform. He's busy, but iperf3
is part of his day job, so I expect it will be looked at fairly quickly.
-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: LAN network performance issues

[justin victoria]

On 3/9/2014 12:40 PM, Kevin Oberman wrote:
On Sun, Mar 9, 2014 at 11:44 AM, justin victoria > wrote:



On 3/9/2014 10:40 AM, Kevin Oberman wrote:

You might try installing iperf3 and testing with that. iperf3 is
a major rewrite of iperf and is totally incompatible  with the
older version, so you will need to install iperf3 on all systems

I doubt iperf is the issue,  but this is a way to check.
-- 
R. Kevin Oberman, Network Engineer, Retired

E-mail: rkober...@gmail.com 


iperf3 on windows isnt playing nice..


Can you provide more details on the problem on Windows? I know the 
primary developer of iperf3 (who also maintains iperf2) and would like 
to be sure he is aware of any and all problems on any platform. He's 
busy, but iperf3 is part of his day job, so I expect it will be looked 
at fairly quickly.

--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com 


I keep getting this error:

justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$ ./iperf3.exe -c 192.168.1.3
  2 [main] iperf3 3116 find_fast_cwd: WARNING: Couldn't compute 
FAST_CWD pointer.  Please report this problem to

the public mailing list cyg...@cygwin.com


Then when im the server:

error: Unable to start listener for connections: Address already in use
error: Unable to start listener for connections: Address already in use
error: Unable to start listener for connections: Address already in use
error: Unable to start listener for connections: Address already in use

and netstat on win:


ustin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$ netstat

Active Connections

  Proto  Local Address  Foreign AddressState
  TCP127.0.0.1:5080 sabertooth:49221   ESTABLISHED
  TCP127.0.0.1:49221sabertooth:5080ESTABLISHED
  TCP127.0.0.1:49637sabertooth:49638   ESTABLISHED
  TCP127.0.0.1:49638sabertooth:49637   ESTABLISHED
  TCP192.168.1.8:49335  lax04s09-in-f22:https  ESTABLISHED
  TCP192.168.1.8:49639  yg:imapESTABLISHED
  TCP192.168.1.8:49641  yg:imapESTABLISHED
  TCP192.168.1.8:49648  yg:imapESTABLISHED
  TCP192.168.1.8:51457  yg:ssh ESTABLISHED
  TCP192.168.1.8:51637  yg:ssh ESTABLISHED
  TCP192.168.1.8:52390  bn1wns1011611:httpsESTABLISHED
  TCP192.168.1.8:52643  lax04s09-in-f1:https   ESTABLISHED
  TCP192.168.1.8:52647  yg:imapESTABLISHED
  TCP192.168.1.8:52649  yg:imapESTABLISHED
  TCP192.168.1.8:52741  103.10.4.40:ftpESTABLISHED
  TCP192.168.1.8:60435  176.32.96.103:http ESTABLISHED
  TCP192.168.1.8:61874  yg:microsoft-dsESTABLISHED
  TCP192.168.1.8:63656  yg:ssh ESTABLISHED

justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$




___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: LAN network performance issues

[Nick Chevsky]

On Sun, Mar 9, 2014 at 1:35 PM, justin victoria  wrote:

>
> I keep getting this error:
>
> justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
> $ ./iperf3.exe -c 192.168.1.3
>   2 [main] iperf3 3116 find_fast_cwd: WARNING: Couldn't compute
> FAST_CWD pointer.  Please report this problem to
> the public mailing list cyg...@cygwin.com


You need to upgrade your cygwin1.dll to fix this problem on Windows 8+.

--
Nick Chevsky
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: LAN network performance issues

[justin victoria]

On 3/9/2014 12:40 PM, Kevin Oberman wrote:

On Sun, Mar 9, 2014 at 11:44 AM, justin victoria  wrote:


On 3/9/2014 10:40 AM, Kevin Oberman wrote:

You might try installing iperf3 and testing with that. iperf3 is a major
rewrite of iperf and is totally incompatible  with the older version, so
you will need to install iperf3 on all systems

I doubt iperf is the issue,  but this is a way to check.
  --
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com


iperf3 on windows isnt playing nice..


Can you provide more details on the problem on Windows? I know the primary
developer of iperf3 (who also maintains iperf2) and would like to be sure
he is aware of any and all problems on any platform. He's busy, but iperf3
is part of his day job, so I expect it will be looked at fairly quickly.




I keep getting this error:

justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$ ./iperf3.exe -c 192.168.1.3
  2 [main] iperf3 3116 find_fast_cwd: WARNING: Couldn't compute 
FAST_CWD pointer.  Please report this problem to

the public mailing list cyg...@cygwin.com


Then when im the server:

error: Unable to start listener for connections: Address already in use
error: Unable to start listener for connections: Address already in use
error: Unable to start listener for connections: Address already in use
error: Unable to start listener for connections: Address already in use

and netstat on win:


ustin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$ netstat

Active Connections

  Proto  Local Address  Foreign AddressState
  TCP127.0.0.1:5080 sabertooth:49221   ESTABLISHED
  TCP127.0.0.1:49221sabertooth:5080ESTABLISHED
  TCP127.0.0.1:49637sabertooth:49638   ESTABLISHED
  TCP127.0.0.1:49638sabertooth:49637   ESTABLISHED
  TCP192.168.1.8:49335  lax04s09-in-f22:https  ESTABLISHED
  TCP192.168.1.8:49639  yg:imapESTABLISHED
  TCP192.168.1.8:49641  yg:imapESTABLISHED
  TCP192.168.1.8:49648  yg:imapESTABLISHED
  TCP192.168.1.8:51457  yg:ssh ESTABLISHED
  TCP192.168.1.8:51637  yg:ssh ESTABLISHED
  TCP192.168.1.8:52390  bn1wns1011611:httpsESTABLISHED
  TCP192.168.1.8:52643  lax04s09-in-f1:https   ESTABLISHED
  TCP192.168.1.8:52647  yg:imapESTABLISHED
  TCP192.168.1.8:52649  yg:imapESTABLISHED
  TCP192.168.1.8:52741  103.10.4.40:ftpESTABLISHED
  TCP192.168.1.8:60435  176.32.96.103:http ESTABLISHED
  TCP192.168.1.8:61874  yg:microsoft-dsESTABLISHED
  TCP192.168.1.8:63656  yg:ssh ESTABLISHED

justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$




___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: LAN network performance issues

[justin victoria]

On 3/9/2014 1:38 PM, Nick Chevsky wrote:

On Sun, Mar 9, 2014 at 1:35 PM, justin victoria  wrote:


I keep getting this error:

justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$ ./iperf3.exe -c 192.168.1.3
   2 [main] iperf3 3116 find_fast_cwd: WARNING: Couldn't compute
FAST_CWD pointer.  Please report this problem to
the public mailing list cyg...@cygwin.com


You need to upgrade your cygwin1.dll to fix this problem on Windows 8+.

--
Nick Chevsky
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"



I just completely removed the old cygwin directory, downloaded a new 
copy of it and installed.. still seeing:


justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$ ./iperf3.exe -s
  1 [main] iperf3 3380 find_fast_cwd: WARNING: Couldn't compute 
FAST_CWD pointer.  Please report this problem to

the public mailing list cyg...@cygwin.com



_Warning: There are multiple cygwin1.dlls on your path _ (not sure about 
this issue tho)

base-cygwin  3.3-1   OK
cygwin   1.7.28-2OK
cygwin-debuginfo 1.7.28-2OK


justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$ echo $PATH
/usr/local/bin:/usr/bin:/cygdrive/c/Program Files (x86)/AMD 
APP/bin/x86_64:/cygdrive/c/Program Files (x86)/AMD 
APP/bin/x86:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program 
Files (x86)/ATI Technologies/ATI.ACE/Core-Static


justin@sabertooth /cygdrive/c/iperf3-3.0b4-cygwin-v2
$



___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Using pf.conf with public access points.

[Jason Hellenthal]

Sorry bit there is not enough information here. How can anyone know what you 
are trying to accomplish by any of this.

-- 
 Jason Hellenthal
 Voice: 95.30.17.6/616
 JJH48-ARIN

> On Mar 9, 2014, at 15:36, Joe Nosay  wrote:
> 
> My pf.conf is attached. I would like to know:
> 1. Is everything set up properly?
> 2. How do I compensate for the use of public access points when the IP
> addresses will always be different?
> 
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


smime.p7s
Description: S/MIME cryptographic signature

Re: Using pf.conf with public access points.

[Joe Nosay]

On Sun, Mar 9, 2014 at 6:05 PM, Jason Hellenthal wrote:

>
> Sorry bit there is not enough information here. How can anyone know what
> you are trying to accomplish by any of this.
>
> --
>  Jason Hellenthal
>  Voice: 95.30.17.6/616
>  JJH48-ARIN
>
> On Mar 9, 2014, at 15:36, Joe Nosay  wrote:
>
> My pf.conf is attached. I would like to know:
> 1. Is everything set up properly?
> 2. How do I compensate for the use of public access points when the IP
> addresses will always be different?
>
> 
>
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
>

1. I can only access public wireless because I homeless. There is no
"static" nor "home" ip address for me to use.
2. I am trying to setup a jail as a developer environment.
3. I need to be able to get the jail started. I do not know the proper
commands nor am I able to find the reference to them.
4. I will need internet access in the jail. I need to test a UDP Lite patch
and that means having to broadcast on the available subnet listed.
5. If there is a set of commands- I have to go back to setting up the
proper sysctl jail references- to start everything, then where may I find
them?

Yes, I will look again.
Now you know what I am working with and the conditions.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Using pf.conf with public access points.

[John-Mark Gurney]

Joe Nosay wrote this message on Sun, Mar 09, 2014 at 15:36 -0400:
> 2. How do I compensate for the use of public access points when the IP
> addresses will always be different?

it doesn't appear that pf has this ability, but it looks like ipfw
has this, from ipfw(8):
 me  matches any IP address configured on an interface in the
 system.

So, maybe switching to ipfw might be an option..

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 "All that I will do, has been done, All that I have, has not."
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Using pf.conf with public access points.

[André Lucas]

On 9 March 2014 23:18, John-Mark Gurney  wrote:

> Joe Nosay wrote this message on Sun, Mar 09, 2014 at 15:36 -0400:
> > 2. How do I compensate for the use of public access points when the IP
> > addresses will always be different?
>
> it doesn't appear that pf has this ability, but it looks like ipfw
> has this, from ipfw(8):
>  me  matches any IP address configured on an interface in
> the
>  system.
>
> So, maybe switching to ipfw might be an option..
>

pf can follow the IP address of an interface. From the pf.conf(5) manual
page, "When the interface name is surrounded by parentheses, the rule is
automatically updated whenever the interface changes its address.  The
ruleset does not need to be reloaded.  This is especially useful with nat."

-André
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Using pf.conf with public access points.

[Jason Hellenthal]

You'll want to not use up addresses in your pf.conf

Block on default and then open up by definition of ports instead. Forget the 
whole IPAddr thing and treat this as a roaming client firewall.


-- 
 Jason Hellenthal
 Voice: 95.30.17.6/616
 JJH48-ARIN

> On Mar 9, 2014, at 19:18, John-Mark Gurney  wrote:
> 
> Joe Nosay wrote this message on Sun, Mar 09, 2014 at 15:36 -0400:
>> 2. How do I compensate for the use of public access points when the IP
>> addresses will always be different?
> 
> it doesn't appear that pf has this ability, but it looks like ipfw
> has this, from ipfw(8):
> me  matches any IP address configured on an interface in the
> system.
> 
> So, maybe switching to ipfw might be an option..
> 
> -- 
>  John-Mark GurneyVoice: +1 415 225 5579
> 
> "All that I will do, has been done, All that I have, has not."
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


smime.p7s
Description: S/MIME cryptographic signature

A problem on SCTP

[Niu Zhixiong]

Dear freebsd-net all,
 I am a beginner of FreeBSD. I meet a problem in SCTP testing.

I have two virtual machine, both installed FreeBSD 10 / i386 / with generic
KERNEL
(the host is CentOS 6.5 x86-64 with KVM)

The first virtual machine named freetest0 and second is freetest1

freetest0 = freebsd 10 / i386 / the IF is vtnet2 192.168.6.100
freetest1 = freebsd 10 / i386 / the IF is vtnet2 192.168.6.110

I want to test the speed between to freetest(s) IF.
But, the problem is they cannot get connected by SCTP. the TCP and UDP are
well.

Whatever I use iperf3 (with SCTP support) and netperfmeter, they cannot get
connected by SCTP.

#the server is freetest1
root@freetest1:~ # netstat -an -f inet
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address  Foreign Address
 (state)
tcp46  0  0 *.9000 *.*LISTEN
tcp4   0  0 192.168.0.110.22   192.168.0.1.39754
 ESTABLISHED
tcp4   0  0 192.168.0.110.22   192.168.0.1.39752
 ESTABLISHED
tcp4   0  0 127.0.0.1.25   *.*LISTEN
tcp4   0  0 *.22   *.*LISTEN
udp46  0  0 *.9000 *.*
udp4   0  0 *.514  *.*
Active SCTP associations (including servers)
Proto  Type  Local Address  Foreign Address(state)
sctp46 1to1  fe80::5054:ff:fe.9000 LISTEN
 192.168.8.110.9000
 fe80::5054:ff:fe.9000
 192.168.6.110.9000
 fe80::5054:ff:fe.9000
 192.168.0.110.9000
 127.0.0.1.9000
 fe80::1.9000
 ::1.9000
sctp46 1toN  fe80::5054:ff:fe.9001 LISTEN
 192.168.8.110.9001
 fe80::5054:ff:fe.9001
 192.168.6.110.9001
 fe80::5054:ff:fe.9001
 192.168.0.110.9001
 127.0.0.1.9001
 fe80::1.9001
 ::1.9001





root@freetest0:~ # netperfmeter 192.168.6.110:9000
Network Performance Meter - Version 1.0
---

Active Mode:
   - Measurement ID  = 4bc75bae
   - Remote Address  = 192.168.6.110:9000
   - Control Address = 192.168.6.110:9001 - connecting ...

#



root@freetest0:~ # tcpdump -i vtnet2
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on vtnet2, link-type EN10MB (Ethernet), capture size 65535
bytes
14:11:03.839031 IP 192.168.6.100.55228 > 192.168.6.110.5201: Flags [S],
seq 1318388212, win 65535, options [mss 1460,nop,wscale 6,sackOK,TS val
2652085 ecr 0], length 0
14:11:03.868787 IP 192.168.6.110.5201 > 192.168.6.100.55228: Flags
[R.], seq 0, ack 1318388213, win 0, length 0
14:11:35.235362 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:38.256378 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:40.256418 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:44.256099 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:52.254442 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]

root@freetest1:~ # tcpdump -i vtnet2
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
listening on vtnet2, link-type EN10MB (Ethernet), capture size 65535
bytes
14:11:35.979349 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:39.000411 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:41.000495 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:45.000116 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]
14:11:52.998491 IP 192.168.6.100.52018 > 192.168.6.110.9001: sctp (1)
[INIT] [init tag: 3995201801] [rwnd: 1864135] [OS: 10] [MIS: 2048] [init
TSN: 332259025]

root@freetest0:~ # uname -a
FreeBSD freetest0 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Fri Jan 17
01:46:25 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC
 i386

Could somebody help me? Thank you in advance