[Bug 203735] Transparent interception of ipv6 with squid and pf causes panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203735 Bjoern A. Zeeb changed: What|Removed |Added Depends on||212105 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212105 [Bug 212105] ipfw dumps core after adding rule with table -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 203735] Transparent interception of ipv6 with squid and pf causes panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203735 Bjoern A. Zeeb changed: What|Removed |Added Depends on|212105 | Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212105 [Bug 212105] ipfw dumps core after adding rule with table -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 193452] Dell PowerEdge 210 II -- Kernel panic bce (broadcom)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193452 Márcio Elias changed: What|Removed |Added CC||marcioel...@gmail.com --- Comment #2 from Márcio Elias --- Hi, we get the same problem with same hardware on a 10.3-RELEASE. We get this in a Dell R210 II and a T210, both with the same driver loaded, and both running IPNAT to translate a lot o private IP's to Public IP's (we are a ISP). The strange is that this error not happens on the time of more load, is random, can occur any time. After change sysctl variables related to network tunning the crashes get less frequent, but the max uptime that we can get is about 2 days. Below is the Sysctl variables that we change. net.bpf.optimize_writers=1 kern.random.sys.harvest.ethernet=0 kern.random.sys.harvest.point_to_point=0 kern.random.sys.harvest.interrupt=0 net.inet.raw.maxdgram=16384 net.inet.raw.recvspace=16384 net.route.netisr_maxqlen=2048 net.inet.ip.redirect=0 kern.ipc.shmmax=2147483648 And this on the /boot/loader.conf net.link.ifqmaxlen=2048 net.isr.maxthreads=4 net.isr.defaultqlimit=2048 Also we enable LARGE_NAT on /usr/src/sys/contrib/ipfilter/netinet/ip_nat.h. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 193452] Dell PowerEdge 210 II -- Kernel panic bce (broadcom)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193452 Kubilay Kocak changed: What|Removed |Added Status|In Progress |Open Version|9.2-RELEASE |10.3-RELEASE Severity|Affects Only Me |Affects Some People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 203735] Transparent interception of ipv6 with squid and pf causes panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203735 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable10?, ||mfc-stable11? Status|In Progress |Open Keywords||crash, needs-patch, ||needs-qa --- Comment #6 from Kubilay Kocak --- Open until assigned -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Cannot access a couple websites
Hi We are experiencing a issue which has me rather stumped. We are using Freebsd 10.3-RELEASE-p7 under Hyper-V 2012 R2 as a firewall (pf), and are unable to browse to www.amazon.com and outlook.office365.com under certain circumstances. The FreeBSD firewall has three interfaces: hn0: public /30 with default route pointing to telco NTU device hn1: public /28 allocated from telco hn2: private /24 NAT is configured on hn0 to nat any outbound traffic to the interface address: nat on hn0 inet from hn2:network to any -> (hn0) In this circumstance, all browsing is fine. However, if we nat outbound traffic to an address in the /28 public range, we are unable to browse to www.amazon.com and outlook.office365.com as two examples. All other sites are fine. Further, if we add another seperate test VM into the /28 public subnet, the same issue occurs. In this situation, no nat is taking place, the firewall is simply routing traffic between the test vm (with a public IP) and the telco link. We are not seeing any traffic being blocked by the pf firewall; we log all dropped packets with "block return log (all)" Packet captures show the connection get up to negotiating the SSL/TLS parameters (server hello, certificate, certificate status) but then various TCP retransmissions and keep alive packets are sent from the webserver IP, and thats where it just sits until the browser times out. We are using a kernel with ALTQ enabled, and the issue occurs both when pf queues are configured and unconfigured. We host a few other services behind this firewall; no issues that we are aware of. Services are natted to addresses in the /28 range. Toggling scrub on/off also makes no difference. The telco is not interested; they claim the traceroutes are fine. (we do see return traffic) I also tried dropping the MTU on the test VM to 1460 with no luck. Has anyone got any ideas on what this could be? We'd be grateful for any assistance. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Cannot access a couple websites
Probably not at all related, but I had a similar problem, youtube worked fine, but cnn would get partial page loads, through a box NATing a public IP. The culprit for me was MTU was wrong. I had FreeBSD in a Xen VM, using the FreeBSD xn driver utilizing VLAN's. When I used VLAN's on that driver it changed the MTU (manpage does warn of this) from 1500 to 1496. What I was seeing was ICMP need-to-fragment packets sent from the FreeBSD box, which the Linux router upstream just dropped. The fix for me was to create the VLAN in Xen, so the MTU was correct and access the NIC as a non-vlan NIC within the VM. Traceroute worked, pings worked, PC's OK on some sites, 'droids all failed. On Wed, Aug 24, 2016 at 7:02 AM, Carl Hattingh wrote: > Hi > > We are experiencing a issue which has me rather stumped. We are using > Freebsd 10.3-RELEASE-p7 under Hyper-V 2012 R2 as a firewall (pf), and are > unable to browse to www.amazon.com and outlook.office365.com under certain > circumstances. > > The FreeBSD firewall has three interfaces: > > hn0: public /30 with default route pointing to telco NTU device > hn1: public /28 allocated from telco > hn2: private /24 > > NAT is configured on hn0 to nat any outbound traffic to the interface > address: > > nat on hn0 inet from hn2:network to any -> (hn0) > > In this circumstance, all browsing is fine. > > However, if we nat outbound traffic to an address in the /28 public range, > we are unable to browse to www.amazon.com and outlook.office365.com as two > examples. All other sites are fine. > Further, if we add another seperate test VM into the /28 public subnet, the > same issue occurs. In this situation, no nat is taking place, the firewall > is simply routing traffic between the test vm (with a public IP) and the > telco link. > > We are not seeing any traffic being blocked by the pf firewall; we log all > dropped packets with "block return log (all)" > > Packet captures show the connection get up to negotiating the SSL/TLS > parameters (server hello, certificate, certificate status) but then various > TCP retransmissions and keep alive packets are sent from the webserver IP, > and thats where it just sits until the browser times out. > > We are using a kernel with ALTQ enabled, and the issue occurs both when pf > queues are configured and unconfigured. We host a few other services > behind this firewall; no issues that we are aware of. Services are natted > to addresses in the /28 range. > > Toggling scrub on/off also makes no difference. > > The telco is not interested; they claim the traceroutes are fine. (we do > see return traffic) > > I also tried dropping the MTU on the test VM to 1460 with no luck. > > Has anyone got any ideas on what this could be? We'd be grateful for any > assistance. > ___ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Tue, Aug 23, 2016 at 10:40 PM, Kevin Oberman < kob6...@gmail.com> wrote: > On Tue, Aug 23, 2016 at 11:48 AM, Adrian Chadd < > adrian.ch...@gmail.com> wrote: > >> Hi, >> >> Compile in IWN_DEBUG and IEEE80211_DEBUG and then do: >> >> wlandebug +assoc +auth +state +rate >> sysctl debug.iwn.0.debug=0x1 >> >> that's TX debugging, and it hopefully will show it trying to do >> association and failing. My guess is that something changed when doing >> the 11n bits for -11 and it's failing to send out the 802.1x frame >> exchange. >> >> It may be something as simple as "adrian needs to fix the rate control >> again". >> >> >> >> -adrian >> > Not working right. I do see 802.11 messages but nothing from iwn. Rebuilt with: optionsIEEE80211_DEBUG optionsIWN_DEBUG > sysctl debug.iwn.0.debug=0x1 sysctl: unknown oid 'debug.iwn.0.debug' Exit 1 > sysctl -a | grep iwn deviceiwn net.wlan.0.%parent: iwn0 net.wlan.devices: iwn0 dev.iwn.0.debug: 0 dev.iwn.0.%parent: pci1 dev.iwn.0.%pnpinfo: vendor=0x8086 device=0x0085 subvendor=0x8086 subdevice=0x1311 class=0x028000 dev.iwn.0.%location: slot=0 function=0 dbsf=pci0:3:0:0 dev.iwn.0.%driver: iwn dev.iwn.0.%desc: Intel Centrino Advanced-N 6205 dev.iwn.%parent: > Here is what I did log. (In this case it did re-associate fairly quickly, unlike when I booted up and it took repeated tries to get an association.) Aug 24 09:54:57 rogue dhclient: New IP Address (wlan0): 192.168.1.5 Aug 24 09:54:57 rogue dhclient: New Subnet Mask (wlan0): 255.255.255.0 Aug 24 09:54:57 rogue dhclient: New Broadcast Address (wlan0): 192.168.1.255 Aug 24 09:54:57 rogue dhclient: New Routers (wlan0): 192.168.1.1 Aug 24 09:54:59 rogue dhclient: New Routers (wlan0): 192.168.1.1 Aug 24 09:56:28 rogue kernel: wlan0: [00:18:e7:dc:05:19] AMRR: current rate 15, txcnt=12, retrycnt=0 Aug 24 09:57:38 rogue kernel: wlan0: [00:18:e7:dc:05:19] AMRR: current rate 15, txcnt=11, retrycnt=0 Aug 24 09:58:43 rogue kernel: wlan0: [00:18:e7:dc:05:19] AMRR: current rate 15, txcnt=12, retrycnt=0 Aug 24 09:59:17 rogue wpa_supplicant[364]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:18:e7:dc:05:19 reason=3 locally_generated=1 Aug 24 09:59:17 rogue kernel: wlan0: [00:18:e7:dc:05:19] station deauth via MLME (reason: 3 (sending STA is leaving/has left IBSS or ESS)) Aug 24 09:59:17 rogue kernel: wlan0: ieee80211_new_state_locked: RUN -> INIT (nrunning 0 nscanning 0) Aug 24 09:59:17 rogue kernel: wlan0: ieee80211_newstate_cb: RUN -> INIT arg 3 Aug 24 09:59:17 rogue kernel: wlan0: sta_newstate: RUN -> INIT (3) Aug 24 09:59:17 rogue kernel: wlan0: [00:18:e7:dc:05:19] send station disassociate (reason: 8 (sending STA is leaving/has left BSS)) Aug 24 09:59:17 rogue kernel: wlan0: [a0:88:b4:c6:ad:28] amrr_node_init: non-11n node Aug 24 09:59:17 rogue kernel: wlan0: [a0:88:b4:c6:ad:28] AMRR: nrates=0, initial rate 0 Aug 24 09:59:17 rogue kernel: wlan0: link state changed to DOWN Aug 24 09:59:17 rogue kernel: wlan0: stop running, 1 vaps running Aug 24 09:59:17 rogue kernel: wlan0: ieee80211_new_state_locked: INIT -> INIT (nrunning 0 nscanning 0) Aug 24 09:59:17 rogue kernel: wlan0: down parent iwn0 Aug 24 09:59:17 rogue kernel: wlan0: ieee80211_newstate_cb: INIT -> INIT arg -1 Aug 24 09:59:17 rogue kernel: wlan0: sta_newstate: INIT -> INIT (-1) Aug 24 09:59:17 rogue wpa_supplicant[364]: wlan0: CTRL-EVENT-TERMINATING Aug 24 09:59:17 rogue dhclient[376]: connection closed Aug 24 09:59:17 rogue dhclient[376]: exiting. Aug 24 09:59:17 rogue kernel: wlan0: ieee80211_vap_detach: STA parent iwn0 Aug 24 09:59:17 rogue kernel: wlan0: stop running, 0 vaps running Aug 24 09:59:17 rogue kernel: wlan0: ieee80211_new_state_locked: INIT -> INIT (nrunning 0 nscanning 0) Aug 24 09:59:17 rogue kernel: wlan0: ieee80211_newstate_cb: INIT -> INIT arg -1 Aug 24 09:59:17 rogue kernel: wlan0: sta_newstate: INIT -> INIT (-1) Aug 24 09:59:17 rogue rtsold[817]: interface wlan0 removed Aug 24 09:59:17 rogue kernel: wlan0: Ethernet address: a0:88:b4:c6:ad:28 Aug 24 09:59:17 rogue wpa_supplicant[1638]: Successfully initialized wpa_supplicant Aug 24 09:59:18 rogue wpa_supplicant[1655]: Successfully initialized wpa_supplicant Aug 24 09:59:18 rogue root: /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Aug 24 09:59:18 rogue wpa_supplicant[1656]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Aug 24 09:59:18 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 Aug 24 09:59:18 rogue wpa_supplicant[1656]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 Aug 24 09:59:19 rogue wpa_supplicant[1656]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Operation now in progress Aug 24 09:59:19 rogue wpa_supplicant[1656]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 Aug 24 09:59:19 rogue wpa_supplicant[1656]: wlan0: Trying to associate with 00:18:e7:dc:05:19 (SSID='babcom' freq=2462 MHz) Aug 24 09:59:29 rogue wpa_supplicant[1656]: wlan0: Authentication with 00:18:e7:dc:05:19 timed out. Aug 24 09:59:29 rogue wpa_supplicant[16
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > Not working right. I do see 802.11 messages but nothing from iwn. > Rebuilt with: > optionsIEEE80211_DEBUG > optionsIWN_DEBUG > > [...] > > Any idea what is going on? Your original email mentions 11.0-BETA4. Are you still running stable/11? If so, could you please update to r304715? If running releng/11.0, the matching commit is r304719. Glen signature.asc Description: PGP signature
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > > Not working right. I do see 802.11 messages but nothing from iwn. > > Rebuilt with: > > optionsIEEE80211_DEBUG > > optionsIWN_DEBUG > > > > [...] > > > > Any idea what is going on? > > Your original email mentions 11.0-BETA4. Are you still running > stable/11? If so, could you please update to r304715? If running > releng/11.0, the matching commit is r304719. > > Glen > Since my initial post I have updated to r304734 (running 11-STABLE). I did that before rebuilding my kernel with the DEBUG options as it was already three weeks old. So this does not seem to have fixed the issue. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > > > Not working right. I do see 802.11 messages but nothing from iwn. > > > Rebuilt with: > > > optionsIEEE80211_DEBUG > > > optionsIWN_DEBUG > > > > > > [...] > > > > > > Any idea what is going on? > > > > Your original email mentions 11.0-BETA4. Are you still running > > stable/11? If so, could you please update to r304715? If running > > releng/11.0, the matching commit is r304719. > > > > Since my initial post I have updated to r304734 (running 11-STABLE). I did > that before rebuilding my kernel with the DEBUG options as it was already > three weeks old. So this does not seem to have fixed the issue. Dumb question, but with reason. Does ifconfig(8) actually show wlan0 'UP'? I'm asking this because I'm seeing something strange locally on one machine. Glen signature.asc Description: PGP signature
Re: iwn(4) association issues in 11-Stable (and maybe RC)
I have been unable to catch it, so I don't know. I know the UP/DOWN sequences in the first log showed many per second and all in the same second. In this case it was UP for 13 seconds, so something was different. I will try to test some more later, but I have to go out for a couple of hours right now. On Aug 24, 2016 12:46 PM, "Glen Barber" wrote: > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: > > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > > > > Not working right. I do see 802.11 messages but nothing from iwn. > > > > Rebuilt with: > > > > optionsIEEE80211_DEBUG > > > > optionsIWN_DEBUG > > > > > > > > [...] > > > > > > > > Any idea what is going on? > > > > > > Your original email mentions 11.0-BETA4. Are you still running > > > stable/11? If so, could you please update to r304715? If running > > > releng/11.0, the matching commit is r304719. > > > > > > > Since my initial post I have updated to r304734 (running 11-STABLE). I > did > > that before rebuilding my kernel with the DEBUG options as it was already > > three weeks old. So this does not seem to have fixed the issue. > > Dumb question, but with reason. > > Does ifconfig(8) actually show wlan0 'UP'? > > I'm asking this because I'm seeing something strange locally on one > machine. > > Glen > > ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote: > On Aug 24, 2016 12:46 PM, "Glen Barber" wrote: > > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > > > > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: > > > > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > > > > > Not working right. I do see 802.11 messages but nothing from iwn. > > > > > Rebuilt with: > > > > > optionsIEEE80211_DEBUG > > > > > optionsIWN_DEBUG > > > > > > > > > > [...] > > > > > > > > > > Any idea what is going on? > > > > > > > > Your original email mentions 11.0-BETA4. Are you still running > > > > stable/11? If so, could you please update to r304715? If running > > > > releng/11.0, the matching commit is r304719. > > > > > > > > > > Since my initial post I have updated to r304734 (running 11-STABLE). I > > did > > > that before rebuilding my kernel with the DEBUG options as it was already > > > three weeks old. So this does not seem to have fixed the issue. > > > > Dumb question, but with reason. > > > > Does ifconfig(8) actually show wlan0 'UP'? > > > > I'm asking this because I'm seeing something strange locally on one > > machine. > > > > I have been unable to catch it, so I don't know. I know the UP/DOWN > sequences in the first log showed many per second and all in the same > second. In this case it was UP for 13 seconds, so something was different. > > I will try to test some more later, but I have to go out for a couple of > hours right now. > Ok, thanks. This is different than the issue I'm seeing, part of which turned out to be a config issue on one of two machines, but completely odd on the other. Glen signature.asc Description: PGP signature
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 08:19:21PM +, Glen Barber wrote: > On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote: > > On Aug 24, 2016 12:46 PM, "Glen Barber" wrote: > > > > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > > > > > > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: > > > > > > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > > > > > > Not working right. I do see 802.11 messages but nothing from iwn. > > > > > > Rebuilt with: > > > > > > optionsIEEE80211_DEBUG > > > > > > optionsIWN_DEBUG > > > > > > > > > > > > [...] > > > > > > > > > > > > Any idea what is going on? > > > > > > > > > > Your original email mentions 11.0-BETA4. Are you still running > > > > > stable/11? If so, could you please update to r304715? If running > > > > > releng/11.0, the matching commit is r304719. > > > > > > > > > > > > > Since my initial post I have updated to r304734 (running 11-STABLE). I > > > did > > > > that before rebuilding my kernel with the DEBUG options as it was > > > > already > > > > three weeks old. So this does not seem to have fixed the issue. > > > > > > Dumb question, but with reason. > > > > > > Does ifconfig(8) actually show wlan0 'UP'? > > > > > > I'm asking this because I'm seeing something strange locally on one > > > machine. > > > > > > > I have been unable to catch it, so I don't know. I know the UP/DOWN > > sequences in the first log showed many per second and all in the same > > second. In this case it was UP for 13 seconds, so something was different. > > > > I will try to test some more later, but I have to go out for a couple of > > hours right now. > > > > Ok, thanks. This is different than the issue I'm seeing, part of which > turned out to be a config issue on one of two machines, but completely > odd on the other. > Sigh. On my side, it was a config issue on both machines. Sorry for the noise, but I'm sure you understand my concern and panic this late in 11.0. Glen signature.asc Description: PGP signature
Re: iwn(4) association issues in 11-Stable (and maybe RC)
hi Would /someone/ pretty please fix this "run wpa_supplicant multiple times at interface start" problem? I'm sure it's screwing things up in a bad way, and trying to grovel around and fix the way we do rc scripts is not my favourite thing in the world. Thanks, -adrian On 24 August 2016 at 13:23, Glen Barber wrote: > On Wed, Aug 24, 2016 at 08:19:21PM +, Glen Barber wrote: >> On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote: >> > On Aug 24, 2016 12:46 PM, "Glen Barber" wrote: >> > >> > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: >> > > > >> > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: >> > > > >> > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: >> > > > > > Not working right. I do see 802.11 messages but nothing from iwn. >> > > > > > Rebuilt with: >> > > > > > optionsIEEE80211_DEBUG >> > > > > > optionsIWN_DEBUG >> > > > > > >> > > > > > [...] >> > > > > > >> > > > > > Any idea what is going on? >> > > > > >> > > > > Your original email mentions 11.0-BETA4. Are you still running >> > > > > stable/11? If so, could you please update to r304715? If running >> > > > > releng/11.0, the matching commit is r304719. >> > > > > >> > > > >> > > > Since my initial post I have updated to r304734 (running 11-STABLE). I >> > > did >> > > > that before rebuilding my kernel with the DEBUG options as it was >> > > > already >> > > > three weeks old. So this does not seem to have fixed the issue. >> > > >> > > Dumb question, but with reason. >> > > >> > > Does ifconfig(8) actually show wlan0 'UP'? >> > > >> > > I'm asking this because I'm seeing something strange locally on one >> > > machine. >> > > >> > >> > I have been unable to catch it, so I don't know. I know the UP/DOWN >> > sequences in the first log showed many per second and all in the same >> > second. In this case it was UP for 13 seconds, so something was different. >> > >> > I will try to test some more later, but I have to go out for a couple of >> > hours right now. >> > >> >> Ok, thanks. This is different than the issue I'm seeing, part of which >> turned out to be a config issue on one of two machines, but completely >> odd on the other. >> > > Sigh. On my side, it was a config issue on both machines. Sorry for > the noise, but I'm sure you understand my concern and panic this late in > 11.0. > > Glen > ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 2:45 PM, Glen Barber wrote: > Dumb question, but with reason. > > Does ifconfig(8) actually show wlan0 'UP'? > > I'm asking this because I'm seeing something strange locally on one > machine. > > Glen Follow up dumb question, but I've very recently experienced (with ath(4), however) the following: * wlan0 is declared 'UP' and even associated, as declared by ifconfig(8) * DHCP seems successful- wlan0 has my static reservation However, the machine would otherwise seem to have no network. All ping(8) packets lost, but the network is otherwise fine. Related, by chance? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 01:51:47PM -0700, Adrian Chadd wrote: > On 24 August 2016 at 13:23, Glen Barber wrote: > > On Wed, Aug 24, 2016 at 08:19:21PM +, Glen Barber wrote: > >> On Wed, Aug 24, 2016 at 01:11:21PM -0700, Kevin Oberman wrote: > >> > On Aug 24, 2016 12:46 PM, "Glen Barber" wrote: > >> > > >> > > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > >> > > > > >> > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber > >> > > > wrote: > >> > > > > >> > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > >> > > > > > Not working right. I do see 802.11 messages but nothing from iwn. > >> > > > > > Rebuilt with: > >> > > > > > optionsIEEE80211_DEBUG > >> > > > > > optionsIWN_DEBUG > >> > > > > > > >> > > > > > [...] > >> > > > > > > >> > > > > > Any idea what is going on? > >> > > > > > >> > > > > Your original email mentions 11.0-BETA4. Are you still running > >> > > > > stable/11? If so, could you please update to r304715? If running > >> > > > > releng/11.0, the matching commit is r304719. > >> > > > > > >> > > > > >> > > > Since my initial post I have updated to r304734 (running 11-STABLE). > >> > > > I > >> > > did > >> > > > that before rebuilding my kernel with the DEBUG options as it was > >> > > > already > >> > > > three weeks old. So this does not seem to have fixed the issue. > >> > > > >> > > Dumb question, but with reason. > >> > > > >> > > Does ifconfig(8) actually show wlan0 'UP'? > >> > > > >> > > I'm asking this because I'm seeing something strange locally on one > >> > > machine. > >> > > > >> > > >> > I have been unable to catch it, so I don't know. I know the UP/DOWN > >> > sequences in the first log showed many per second and all in the same > >> > second. In this case it was UP for 13 seconds, so something was > >> > different. > >> > > >> > I will try to test some more later, but I have to go out for a couple of > >> > hours right now. > >> > > >> > >> Ok, thanks. This is different than the issue I'm seeing, part of which > >> turned out to be a config issue on one of two machines, but completely > >> odd on the other. > >> > > > > Sigh. On my side, it was a config issue on both machines. Sorry for > > the noise, but I'm sure you understand my concern and panic this late in > > 11.0. > > > > Glen > > > > Would /someone/ pretty please fix this "run wpa_supplicant multiple > times at interface start" problem? > > I'm sure it's screwing things up in a bad way, and trying to grovel > around and fix the way we do rc scripts is not my favourite thing in > the world. > This does not interfere in my case, it was a configuration issue. However, I was never able to effectively (as in, reliably) reproduce wpa_supplicant starting more than once. When it *did*, everything still worked as expected. Glen signature.asc Description: PGP signature
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 03:21:12PM -0500, Kyle Evans wrote:
> On Wed, Aug 24, 2016 at 2:45 PM, Glen Barber wrote:
> > Dumb question, but with reason.
> >
> > Does ifconfig(8) actually show wlan0 'UP'?
> >
> > I'm asking this because I'm seeing something strange locally on one
> > machine.
> >
> > Glen
>
> Follow up dumb question, but I've very recently experienced (with ath(4),
> however) the following:
>
> * wlan0 is declared 'UP' and even associated, as declared by ifconfig(8)
> * DHCP seems successful- wlan0 has my static reservation
>
> However, the machine would otherwise seem to have no network. All ping(8)
> packets lost, but the network is otherwise fine. Related, by chance?
I don't think so, but I'm not sure we have enough data yet.
What does your routing table ('netstat -rn') look like, and what do you
have in your rc.conf regarding IPv6?
(And, do you have pf(4) enabled?)
Glen
signature.asc
Description: PGP signature
Re: iwn(4) association issues in 11-Stable (and maybe RC)
On Wed, Aug 24, 2016 at 12:45 PM, Glen Barber < g...@freebsd.org> wrote: > On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: > > > > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: > > > > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: > > > > Not working right. I do see 802.11 messages but nothing from iwn. > > > > Rebuilt with: > > > > optionsIEEE80211_DEBUG > > > > optionsIWN_DEBUG > > > > > > > > [...] > > > > > > > > Any idea what is going on? > > > > > > Your original email mentions 11.0-BETA4. Are you still running > > > stable/11? If so, could you please update to r304715? If running > > > releng/11.0, the matching commit is r304719. > > > > > > > Since my initial post I have updated to r304734 (running 11-STABLE). I > did > > that before rebuilding my kernel with the DEBUG options as it was already > > three weeks old. So this does not seem to have fixed the issue. > > Dumb question, but with reason. > > Does ifconfig(8) actually show wlan0 'UP'? > > I'm asking this because I'm seeing something strange locally on one > machine. > > Glen I have stopped and started the network repeatedly using both my home router and my hot-spot and I can't get it to fail. It associates the first time every time. I'm about ready to chalk up my one failure with the new kernel as a fluke. I'll continue testing later today, but this one may be resolved. I'll also rebuild my kernel without the debug options just in case the slight timing change had some impact on this. Thanks to both Glen and Adrian for helping me look into this. Still have no idea why IWN_DEBUG didn't seem to work. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: iwn(4) association issues in 11-Stable (and maybe RC)
IWN_DEBUG worked, it's 'dev.iwn.0.debug', not 'debug.iwn.0.debug'. My bad. Make sure you build the module by doing 'buildkernel', not 'cd sys/modules/iwn && make', as (because reasons I want to grr) we don't enforce that people put in a path to their kernel config .h directory, so it defaults to "some arbitrary options". -a On 24 August 2016 at 15:42, Kevin Oberman wrote: > On Wed, Aug 24, 2016 at 12:45 PM, Glen Barber wrote: >> >> On Wed, Aug 24, 2016 at 12:20:57PM -0700, Kevin Oberman wrote: >> > >> > On Wed, Aug 24, 2016 at 12:03 PM, Glen Barber wrote: >> > >> > > On Wed, Aug 24, 2016 at 11:55:13AM -0700, Kevin Oberman wrote: >> > > > Not working right. I do see 802.11 messages but nothing from iwn. >> > > > Rebuilt with: >> > > > optionsIEEE80211_DEBUG >> > > > optionsIWN_DEBUG >> > > > >> > > > [...] >> > > > >> > > > Any idea what is going on? >> > > >> > > Your original email mentions 11.0-BETA4. Are you still running >> > > stable/11? If so, could you please update to r304715? If running >> > > releng/11.0, the matching commit is r304719. >> > > >> > >> > Since my initial post I have updated to r304734 (running 11-STABLE). I >> > did >> > that before rebuilding my kernel with the DEBUG options as it was >> > already >> > three weeks old. So this does not seem to have fixed the issue. >> >> Dumb question, but with reason. >> >> Does ifconfig(8) actually show wlan0 'UP'? >> >> I'm asking this because I'm seeing something strange locally on one >> machine. >> >> Glen > > > I have stopped and started the network repeatedly using both my home router > and my hot-spot and I can't get it to fail. It associates the first time > every time. I'm about ready to chalk up my one failure with the new kernel > as a fluke. I'll continue testing later today, but this one may be resolved. > > I'll also rebuild my kernel without the debug options just in case the > slight timing change had some impact on this. > > Thanks to both Glen and Adrian for helping me look into this. Still have no > idea why IWN_DEBUG didn't seem to work. > -- > R. Kevin Oberman, Network Engineer > E-mail: kob6...@gmail.com ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
