#876 closed defect (fixed)
various trouble with ietf wifi networks in my windows7
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | tbd | Milestone: | ietf-091 |
| Component: | wireless | Keywords: | |
| Cc: | My Current Location: | ||
| My MAC Address: | My OS: |
Description
-- Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail!
Change history (10)
comment:1 Changed 6 years ago by
| Component: | incoming → wireless |
|---|---|
| Owner: | changed from llynch@… to nkukich@… |
| Type: | request → defect |
comment:2 Changed 6 years ago by
Replying to hiroa-ha@…:
-- Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail!
please see: https://tickets.meeting.ietf.org/wiki/CentrinoIssue
and let us know if this fixes your issue.
comment:3 Changed 6 years ago by
Sorry, I sent a mail before writing body part. 1) in hibiscus, IPv6 DNS did not answer on ietf-a.1x. (I could not get global IPv4 address) 2) in ietf-nat64, DNS did not return any answer. And, ping to external network (wide project) was unreach. > > > > -- > Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail! > -- Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail!
comment:4 follow-up: 5 Changed 6 years ago by
Oe-san tuned my windows7's wif-parameter that prefers 2.4GHz band. It works well !! thanks! ---- hazeyama (2014/11/11 9:29), Hiroaki Hazeyama wrote: > Sorry, I sent a mail before writing body part. > > 1) in hibiscus, IPv6 DNS did not answer on ietf-a.1x. (I could not get global IPv4 address) > > 2) in ietf-nat64, DNS did not return any answer. And, ping to external network (wide project) was unreach. > > > > >> >> >> -- >> Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail! >> > -- > Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail!
comment:5 Changed 6 years ago by
Replying to hiroa-ha@…:
Oe-san tuned my windows7's wif-parameter that prefers 2.4GHz band. It works well !! thanks! ---- hazeyama (2014/11/11 9:29), Hiroaki Hazeyama wrote: > Sorry, I sent a mail before writing body part. > > 1) in hibiscus, IPv6 DNS did not answer on ietf-a.1x. (I could not get global IPv4 address) > > 2) in ietf-nat64, DNS did not return any answer. And, ping to external network (wide project) was unreach. > > > > >> >> >> -- >> Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail! >> > -- > Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail!
Hazeyama,
If you have time, we'd love to have your help debugging this issue further so we can get a real fix for this issue and not just a workaround. If you can, come to the NOC in the Nautilus room.
Thanks!
Chris.
comment:6 Changed 6 years ago by
Hi, ietf box team. Except when I joined debugging and an engineer turn on the work around, my windws7 laptop pc cannot get IPv4, cannot reach DNS even when I connect to ietf-nat64! If you have a work around, please turn on it! I cannot conduct my business only by iPod touch ! > Oe-san tuned my windows7's wif-parameter that prefers 2.4GHz band. > It works well !! > thanks! > > ---- > hazeyama > > > (2014/11/11 9:29), Hiroaki Hazeyama wrote: > > Sorry, I sent a mail before writing body part. > > > > 1) in hibiscus, IPv6 DNS did not answer on ietf-a.1x. (I could not get global IPv4 address) > > > > 2) in ietf-nat64, DNS did not return any answer. And, ping to external network (wide project) was unreach. > > > > > > > > > >> > >> > >> -- > >> Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail! > >> > > -- > > Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail! > > -- Hiroaki Hazeyama<hiroa-ha@is.naist.jp> sent by ibisMail!
comment:7 Changed 6 years ago by
Hazeyama,
Is the "work-around" you're referring to the ietf-2.4only SSID? Is that working for you? Unfortunately, as it seems there's a specific failure between your laptop's chipset and the new Access Points with certain features turned on, you may not be able to join the NAT64 network. We continue to work with Cisco to address this situation, and if you could come to the NOC (Nautilus) and find Chris Elliott, you may be able to help us debug the issue further.
- Jim
comment:8 Changed 6 years ago by
along with the recommendation to turn off 11.n feature, I can connet ietf-a.1x ! thank you so much! ---- hazeyama (2014/11/12 8:37), IETF Meeting/NOC wrote: > #876: various trouble with ietf wifi networks in my windows7 > -----------------------------+--------------------------------- > Reporter: hiroa-ha@… | Owner: nkukich@… > Type: defect | Status: new > Priority: tbd | Milestone: ietf-91 > Component: wireless | Resolution: > Keywords: | My Current Location: > My MAC Address: | My OS: > -----------------------------+--------------------------------- > > Comment (by jim@…): > > Hazeyama, > Is the "work-around" you're referring to the ietf-2.4only SSID? Is > that working for you? Unfortunately, as it seems there's a specific > failure between your laptop's chipset and the new Access Points with > certain features turned on, you may not be able to join the NAT64 network. > We continue to work with Cisco to address this situation, and if you could > come to the NOC (Nautilus) and find Chris Elliott, you may be able to help > us debug the issue further. > > - Jim > > -- > Ticket URL: <https://tickets.meeting.ietf.org/ticket/876#comment:7> > IETF Meeting/NOC <https://tickets.meeting.ietf.org> > IETF Meeting - NOC pages
comment:9 Changed 6 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Glad it's working for you now. Resolving this ticket.
Thanks!
- Jim
Note: See TracTickets for help on using tickets.
please see: https://tickets.meeting.ietf.org/wiki/CentrinoIssue
and let us know if this fixes your issue.