Re: forwarding didn't work if wlan0 is member of a bridge

[Sergey Manucharian]

Excerpts from Olivier Cochard-Labbé's message from Wed 23-Dec-15 11:31:
> If wlan0 interface is member of a bridge, FreeBSD didn't reach to
> forward-back packets to wireless client
> 
> My setup is this one:
> 
> internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0]
>  <--> wireless client
> 
> and the problem description:
>  - wireless clients didn't receive any packet back: the fbsd-router blocks
> answers because it thinks wireless clients are "unreachable".
>  - But wireless clients can reach all IP of the fbsd-router hitself without
> problem, and fbsd-router can ping them too.
>  - Ethernet clients connected to the same bridge0 didn't have problem

I believe this is related to the fact that wifi adapter cannot have more
that one MAC address. And that becomes true when it's a member of a
bridge. There exist some tricky ways to overcome that though.

S.

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

Re: Need help with New Build -- Skylake

[Vijay Rjah]

On 12/23/15 2:29 AM, Ed Maste wrote:

On 22 December 2015 at 12:39, Vijay Rjah  wrote:

The only issue i have is that the boot process takes a lot of time..
(similar to
https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/
). the system ultimately boots, but boot times are around 4 - 5 Mins..

How do I debug it? any suggestions?

A useful first step is to get a verbose boot ("boot -v" from the
loader prompt) and note where there are any large or unexpected
delays. The "memory test" that was responsible for many reports of
slow FreeBSD boots has been disabled in 11.x for quite some time, so
it won't be that.
___
freebsd-questi...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Thanks for your reply..

It takes about 3-4 Mins just to get to the boot option screen.. ( I mean 
the menu where it lets you select multi/single user mode etc...)


I have attached the output of "boot -v"..

-Thanks
Vijay
Dec 23 23:03:13 vrajah-bsd syslogd: kernel boot file is /boot/kernel/kernel
Dec 23 23:03:13 vrajah-bsd kernel: Table 'FACP' at 0x8ad96270
Dec 23 23:03:13 vrajah-bsd kernel: Table 'APIC' at 0x8ad96380
Dec 23 23:03:13 vrajah-bsd kernel: APIC: Found table at 0x8ad96380
Dec 23 23:03:13 vrajah-bsd kernel: APIC: Using the MADT enumerator.
Dec 23 23:03:13 vrajah-bsd kernel: MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
Dec 23 23:03:13 vrajah-bsd kernel: SMP: Added CPU 0 (AP)
Dec 23 23:03:13 vrajah-bsd kernel: MADT: Found CPU APIC ID 2 ACPI ID 2: enabled
Dec 23 23:03:13 vrajah-bsd kernel: SMP: Added CPU 2 (AP)
Dec 23 23:03:13 vrajah-bsd kernel: MADT: Found CPU APIC ID 1 ACPI ID 3: enabled
Dec 23 23:03:13 vrajah-bsd kernel: SMP: Added CPU 1 (AP)
Dec 23 23:03:13 vrajah-bsd kernel: MADT: Found CPU APIC ID 3 ACPI ID 4: enabled
Dec 23 23:03:13 vrajah-bsd kernel: SMP: Added CPU 3 (AP)
Dec 23 23:03:13 vrajah-bsd kernel: Copyright (c) 1992-2015 The FreeBSD Project.
Dec 23 23:03:13 vrajah-bsd kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 
1989, 1991, 1992, 1993, 1994
Dec 23 23:03:13 vrajah-bsd kernel: The Regents of the University of California. 
All rights reserved.
Dec 23 23:03:13 vrajah-bsd kernel: FreeBSD is a registered trademark of The 
FreeBSD Foundation.
Dec 23 23:03:13 vrajah-bsd kernel: FreeBSD 11.0-CURRENT #0 r291495: Mon Nov 30 
23:14:34 UTC 2015
Dec 23 23:03:13 vrajah-bsd kernel: 
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
Dec 23 23:03:13 vrajah-bsd kernel: FreeBSD clang version 3.7.0 
(tags/RELEASE_370/final 246257) 20150906
Dec 23 23:03:13 vrajah-bsd kernel: WARNING: WITNESS option enabled, expect 
reduced performance.
Dec 23 23:03:13 vrajah-bsd kernel: PPIM 0: PA=0xa, VA=0x8261, 
size=0x1, mode=0
Dec 23 23:03:13 vrajah-bsd kernel: VT(vga): resolution 640x480
Dec 23 23:03:13 vrajah-bsd kernel: Preloaded elf kernel "/boot/kernel/kernel" 
at 0x82419000.
Dec 23 23:03:13 vrajah-bsd kernel: Preloaded /boot/entropy "/boot/entropy" at 
0x82419e48.
Dec 23 23:03:13 vrajah-bsd kernel: Preloaded elf obj module 
"/boot/kernel/zfs.ko" at 0x82419e98.
Dec 23 23:03:13 vrajah-bsd kernel: Preloaded elf obj module 
"/boot/kernel/opensolaris.ko" at 0x8241a680.
Dec 23 23:03:13 vrajah-bsd kernel: Calibrating TSC clock ... TSC clock: 
3696187166 Hz
Dec 23 23:03:13 vrajah-bsd kernel: CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz 
(3696.19-MHz K8-class CPU)
Dec 23 23:03:13 vrajah-bsd kernel: Origin="GenuineIntel"  Id=0x506e3  
Family=0x6  Model=0x5e  Stepping=3
Dec 23 23:03:13 vrajah-bsd kernel: 
Features=0xbfebfbff
Dec 23 23:03:13 vrajah-bsd kernel: 
Features2=0x7ffafbbf
Dec 23 23:03:13 vrajah-bsd kernel: AMD 
Features=0x2c100800
Dec 23 23:03:13 vrajah-bsd kernel: AMD Features2=0x121
Dec 23 23:03:13 vrajah-bsd kernel: Structured Extended 
Features=0x29c67af
Dec 23 23:03:13 vrajah-bsd kernel: XSAVE 
Features=0xf
Dec 23 23:03:13 vrajah-bsd kernel: VT-x: Basic 
Features=0xda0400
Dec 23 23:03:13 vrajah-bsd kernel: Pin-Based 
Controls=0x7f
Dec 23 23:03:13 vrajah-bsd kernel: Primary Processor 
Controls=0xfff9fffe
Dec 23 23:03:13 vrajah-bsd kernel: Secondary Processor 

Re: forwarding didn't work if wlan0 is member of a bridge

[Kristof Provost]

On 2015-12-23 08:08:29 (-0700), Sergey Manucharian  wrote:
> I believe this is related to the fact that wifi adapter cannot have more
> that one MAC address. And that becomes true when it's a member of a
> bridge. There exist some tricky ways to overcome that though.
> 
That's true, but that only applies in station mode (i.e. as a wifi
client). If I'm reading the report right Olivier is using wifi0 as an
access point here.

Regards,
Kristof
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Bootstrapping from stable/9 to head?

[Warner Losh]

Make build world first!
On Dec 23, 2015 5:06 PM, "NGie Cooper"  wrote:

> Hi Ian and Warner,
> I realize this isn’t a path that’s currently supported, but when I
> was running a test for jhb on stable/9 (ref9-amd64.freebsd.org to be
> exact), I ran into this error:
>
> bmake[1]: "/scratch/tmp/ngie/svn/Makefile" line 466: "Target architecture
> for arm/conf/A20 unknown.  config(8) likely too old."
> *** [universe_arm_kernels] Error code 1
>
> bmake: stopped in /scratch/tmp/ngie/svn
>
> I was wondering if there was a way where someone could more
> reliably bootstrap from stable/9 to stable/10, or if the directions just
> need to be changed to “upgrade to the latest release of 10, then upgrade to
> 11-CURRENT”?
> Also, config is a build tool in Makefile.inc1… I was wondering if
> the check in Makefile is a bit too stringent / incorrect.
> Thanks,
> -NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Bootstrapping from stable/9 to head?

[NGie Cooper]

Hi Ian and Warner,
I realize this isn’t a path that’s currently supported, but when I was 
running a test for jhb on stable/9 (ref9-amd64.freebsd.org to be exact), I ran 
into this error:

bmake[1]: "/scratch/tmp/ngie/svn/Makefile" line 466: "Target architecture for 
arm/conf/A20 unknown.  config(8) likely too old."
*** [universe_arm_kernels] Error code 1

bmake: stopped in /scratch/tmp/ngie/svn

I was wondering if there was a way where someone could more reliably 
bootstrap from stable/9 to stable/10, or if the directions just need to be 
changed to “upgrade to the latest release of 10, then upgrade to 11-CURRENT”?
Also, config is a build tool in Makefile.inc1… I was wondering if the 
check in Makefile is a bit too stringent / incorrect.
Thanks,
-NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: forwarding didn't work if wlan0 is member of a bridge

[Adrian Chadd]

Hi,

inet 10.239.142.126 netmask 0xffe0 broadcast 10.239.142.127

This looks like a problem with your addressing. That netmask != that broadcast.

Please recheck your networking setup!


-a


On 23 December 2015 at 02:31, Olivier Cochard-Labbé  wrote:
> Hi,
>
> If wlan0 interface is member of a bridge, FreeBSD didn't reach to
> forward-back packets to wireless client
>
> My setup is this one:
>
> internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0]
>  <--> wireless client
>
> and the problem description:
>  - wireless clients didn't receive any packet back: the fbsd-router blocks
> answers because it thinks wireless clients are "unreachable".
>  - But wireless clients can reach all IP of the fbsd-router hitself without
> problem, and fbsd-router can ping them too.
>  - Ethernet clients connected to the same bridge0 didn't have problem
>
> A tcpdump on the outgoing interface shows the fbsd-router correctly
> receiving/NATing/forwarding the wireless-client packet (10.239.142.104
> natted to 192.168.100.70) toward the Internet-gateway (192.168.100.254),
> but once received the response from the internet-gateway it is not able to
> reach the wireless-client (unreachable):
> [fbsd-router]~> sudo tcpdump -pni net0 icmp
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on net0, link-type EN10MB (Ethernet), capture size 262144 bytes
> 07:35:24.869560 IP 192.168.100.70 > 192.168.100.254: ICMP echo request, id
> 1, seq 375, length 40
> 07:35:24.869772 IP 192.168.100.254 > 192.168.100.70: ICMP echo reply, id 1,
> seq 375, length 40
> 07:35:24.870314 IP 192.168.100.70 > 192.168.100.254: ICMP host
> 10.239.142.104 unreachable, length 36
>
> But directly from the fbsd-router, there is no problem for reaching the
> wireless-client:
> [fbsd-router]~> ping wireless-client
> PING 10.239.142.104 (10.239.142.104): 56 data bytes
> 64 bytes from 10.239.142.104: icmp_seq=0 ttl=128 time=2.633 ms
> 64 bytes from 10.239.142.104: icmp_seq=1 ttl=128 time=1.614 ms
>
> I'm using a bridge because I need to use only one subnet for all my clients
> (ethernet and wifi):
> [fbsd-router]~> ifconfig bridge0
> bridge0: flags=8843 metric 0 mtu
> 1500
> ether 02:82:9f:45:81:00
> inet 10.239.142.126 netmask 0xffe0 broadcast 10.239.142.127
> nd6 options=49
> groups: bridge
> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
> maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
> member: wlan0 flags=143
> ifmaxaddr 0 port 6 priority 128 path cost 3
> member: net1 flags=143
> ifmaxaddr 0 port 2 priority 128 path cost 55
>
> And this "unreacheable" problem is related to the bridge, if I remove the
> wlan0 from the bridge, there is no more problem.
>
> What problem can cause FreeBSD to answer back "unreachable" when wlan0 is
> member of a bridge ?
>
> Head versions tested: r290522, r291362, r292613.
>
> Thanks,
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Need help with New Build -- Skylake

[Vijay Rajah]

On 12/24/15 12:22 PM, Ian Smith wrote:

  ~2 minutes delay there.  sendmail (mta and msp both) at least
are unhappy about your hostname, and sleep on it.  I don't know whether
that's significant or related to the longer delay you report.  I just
skimmed through your dmesg, but didn't spot anything glaringly obvious.

FWIW, cheers, Ian

Ian,

Thanks for taking the time to help me.

The delay is (mostly) before the boot loader menu is presented. Once the 
system starts to boot.. It is pretty fast...


When the system boots, after the BIOS hands over the control to the OS.. 
there are 6-7 lines, which give boot loader version etc.. (the last of 
this gives the details of the build host etc..)


Then there is a spinning wheel, an the system just sits there for some 
time.. (even the wheel spins slowly). after 3-4 mins I see it loads the 
/boot/default/loader.conf . After this the menu is loaded..


so, the issue is long before this dmesg even begins... Unfortunately, I 
do not know how to force a verbose boot before the boot menu...


-Thanks
Vijay

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

forwarding didn't work if wlan0 is member of a bridge

[Olivier Cochard-Labbé]

Hi,

If wlan0 interface is member of a bridge, FreeBSD didn't reach to
forward-back packets to wireless client

My setup is this one:

internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0]
 <--> wireless client

and the problem description:
 - wireless clients didn't receive any packet back: the fbsd-router blocks
answers because it thinks wireless clients are "unreachable".
 - But wireless clients can reach all IP of the fbsd-router hitself without
problem, and fbsd-router can ping them too.
 - Ethernet clients connected to the same bridge0 didn't have problem

A tcpdump on the outgoing interface shows the fbsd-router correctly
receiving/NATing/forwarding the wireless-client packet (10.239.142.104
natted to 192.168.100.70) toward the Internet-gateway (192.168.100.254),
but once received the response from the internet-gateway it is not able to
reach the wireless-client (unreachable):
[fbsd-router]~> sudo tcpdump -pni net0 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on net0, link-type EN10MB (Ethernet), capture size 262144 bytes
07:35:24.869560 IP 192.168.100.70 > 192.168.100.254: ICMP echo request, id
1, seq 375, length 40
07:35:24.869772 IP 192.168.100.254 > 192.168.100.70: ICMP echo reply, id 1,
seq 375, length 40
07:35:24.870314 IP 192.168.100.70 > 192.168.100.254: ICMP host
10.239.142.104 unreachable, length 36

But directly from the fbsd-router, there is no problem for reaching the
wireless-client:
[fbsd-router]~> ping wireless-client
PING 10.239.142.104 (10.239.142.104): 56 data bytes
64 bytes from 10.239.142.104: icmp_seq=0 ttl=128 time=2.633 ms
64 bytes from 10.239.142.104: icmp_seq=1 ttl=128 time=1.614 ms

I'm using a bridge because I need to use only one subnet for all my clients
(ethernet and wifi):
[fbsd-router]~> ifconfig bridge0
bridge0: flags=8843 metric 0 mtu
1500
ether 02:82:9f:45:81:00
inet 10.239.142.126 netmask 0xffe0 broadcast 10.239.142.127
nd6 options=49
groups: bridge
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: wlan0 flags=143
ifmaxaddr 0 port 6 priority 128 path cost 3
member: net1 flags=143
ifmaxaddr 0 port 2 priority 128 path cost 55

And this "unreacheable" problem is related to the bridge, if I remove the
wlan0 from the bridge, there is no more problem.

What problem can cause FreeBSD to answer back "unreachable" when wlan0 is
member of a bridge ?

Head versions tested: r290522, r291362, r292613.

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

Re: Build from 9.3-RELEASE to 11.0-CURRENT fails for i386 (-Wsign-compare issues with gcc)

[NGie Cooper]

> On Dec 22, 2015, at 10:27, Garrett Cooper  wrote:
> 
> 
>> On Dec 22, 2015, at 08:23, John Baldwin  wrote:
>> 
>>> On Monday, December 21, 2015 11:01:36 AM John Baldwin wrote:
 On Saturday, December 19, 2015 01:05:36 PM NGie Cooper wrote:
 Hi John,
   I tried bootstrapping 9.3-RELEASE to 11.0-CURRENT with i386 and ran into 
 the -Wsign-compare issue below when running make libraries with 
 buildworld, because it’s building libkvm with gcc 4.2.1 :/… I’ve tried 
 bootstrapping with clang/clang37, but haven’t been able to yet. I’ll try 
 installing 10.2-RELEASE via freebsd-update so I can use clang instead of 
 gcc.
 Thanks!
 -NGie
>>> 
>>> We don't actually support going from 9 to 11.  However, these constants
>>> should probably be explicitly unsigned anyway.  I haven't tested this at
>>> all, but something like this:
>>> 
>>> Index: head/lib/libkvm/kvm_i386.h
>>> ===
>>> --- head/lib/libkvm/kvm_i386.h  (revision 292553)
>>> +++ head/lib/libkvm/kvm_i386.h  (working copy)
>>> @@ -57,8 +57,8 @@
>>> #defineI386_PG_PS  0x080
>>> #defineI386_PG_FRAME_PAE   (0x000ff000ull)
>>> #defineI386_PG_PS_FRAME_PAE(0x000fffe0ull)
>>> -#defineI386_PG_FRAME   (0xf000)
>>> -#defineI386_PG_PS_FRAME(0xffc0)
>>> +#defineI386_PG_FRAME   (0xf000u)
>>> +#defineI386_PG_PS_FRAME(0xffc0u)
>>> 
>>> #ifdef __i386__
>>> _Static_assert(PAGE_SHIFT == I386_PAGE_SHIFT, "PAGE_SHIFT mismatch");
>> 
>> This passed a universe build on HEAD.  If you can test that it fixes the 9.3 
>> -> 11.0
>> bootstrap I will commit it.
> 
> I'll fire up a 9.3 VM and give it a shot.
> Thanks :)!!

Hmm… no bueno on ref9-amd64. What likely needs to be done is that the directory 
needs to be built by itself with gcc on i386.
Thanks!
-NGie

cc1: warnings being treated as errors
In file included from /scratch/tmp/ngie/svn/lib/libkvm/kvm_i386.c:63:
/scratch/tmp/ngie/svn/lib/libkvm/kvm_i386.h:73: warning: comparison between 
signed and unsigned
*** [kvm_i386.So] Error code 1

bmake[5]: stopped in /scratch/tmp/ngie/svn/lib/libkvm
1 error

bmake[5]: stopped in /scratch/tmp/ngie/svn/lib/libkvm
*** [lib/libkvm__L] Error code 2

bmake[4]: stopped in /scratch/tmp/ngie/svn

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