#41

this sounds like a USB hub shutdown as a result of not enough current— i suspect you may have a bunch of USB devices plugged in? this could happen if the norns is powered up without a wall connector.

also heads up, if you’re not actively using the wifi, i’d take the nub out. saves power, keeps the system more stable.

1 Like
#42

I’m having a wifi issue with the new Norns Shield. I’m able to find my network and enter the password. After hitting ‘OK’ I’m taken back to the menu and the STATUS says “activating” with my network name listed. Soon after it shows some activity under SIGNAL, but then my network name disappears and it gets hung on “activating” and never connects.

#43

A reboot / reset usually solves wifi issues.
Also try deleting and re-adding the network before reboot.

#44

Should have tried that before posting. That worked. Thanks.

1 Like
#45

not sure if this is a wifi issue or more specifically a maiden issue…

turned on my norns today in a while and it connected to my wifi just fine, except that I couldn’t access maiden. trying to connect through macos didn’t work either.

I tried to update (because I was one version behind) and that worked just fine, but still couldn’t connect to maiden after the update. removed the wifi network and re-added it, but that didn’t help either.

any ideas?

1 Like
#46

What did you try, what happened?

If you used norns.local and it wouldn’t resolve, i guess is some issue with hosts file / zeroconf, and you could try putting in the ip address explicitly

#47

sorry, to be more precise:

entering the ip address (in a browser or via the network window in macos finder) or norns.local both give me a “server not found” or a timed out connection failure, throughout all the steps listed above (before/after update/reset, before/after removing and re-adding the network info on norns).

wifi signal remains strong on norns through all of this.

1 Like
#48

If the device update completely successfully then that means your norns can access the internet, dns is working, and norns isn’t running in hotspot mode… so if you can’t access maiden via the IP address listed on the norns screen that leads me to suspect the computer being used to access maiden might be the problem. Does your network have multiple base stations? Multiple subsets?

#49

just wanted to report that i have the exact same issue as @karst - connected to wifi > couldn’t connect to norns.local or the IP address in my laptop browser or cyberduck (timeouts on both) > redid all my norns wifi network presets > updated to the new norns os via wifi just fine > still couldn’t access maiden from my laptop or phone. haven’t yet tried it on a different wifi network, will do as soon as i can.

#50

Out of curiousity, @madeofoak, @karst, when typing in norns.local or the IP address of the machine into a browser can you tell if the browser is using HTTP or HTTPS?

Many browsers have started to assume HTTPS (encrypted HTTP) by default when it is not explicitly specified in the URL. The built in server on norns is only setup to listen for HTTP requests (not HTTPS).

Does it work if http://norns.local/ is typed in explicitly?

#51

Does your network have multiple base stations? Multiple subsets?

@ngwese, good call. looks like the issue only exists while on the wifi extender’s network, not on the main network. don’t know why this worked a few weeks ago and not now, but I can only assume something changed on my network’s end.

#52

writing in ‘http’does not fix the problem, and i’m not on an extension or meshed wifi network.

#53

It is hard to say without really getting into the details of the hardware involved, layout of the base stations, etc. While “zeroconf” / “multicast-dns” is really handy for allowing computers to find each other by name (instead of by IP address) there are many things which can make it fail to function on anything beyond the most basic of networks. The chief problem is that mdns uses multicast addressing to broadcast out information regarding its presence to any computer on the same segment of the network. The complication comes when the multicast packets get to a router - the router could be connected to any number of additional network segments. If the router were to rebroadcast the information on all its other network segments one ends up with a bunch of chatter which can hurt the performance of a network (particularly on WiFi). The default behavior for routers it to not rebroadcast multicast packets. In larger networks the use of multicast is restricted if not out right prevented.

In the case of a mesh network I wouldn’t expect each part of the mesh to be a different segment/subnet but it probably depends on the gear involved.

Another problem which can occur is when devices (like norns) use DHCP to request an IP address for the network and get assigned different addresses over time. When norns gets an address it broadcasts that out via mdns, if norns is rebooted or moved to a different network it may acquire a new address and then broadcast that new address out. Computers within mdns range now can have two conflicting mappings for norns.local to an IP address. Generally timeouts/leases on the mdns entries will fix this conflict in time but it is not immediate.

A third potential problem is a variation of the above. If you have multiple norns devices on the same network each will try to claim norns.local which will lead to confusion.

Using the IP address should be reliable if/when norns.local doesn’t appear to be working. One step I’ve taken myself is to tell my DCHP server to give norns a static assignment which results in it getting the same IP address each time it boots (which is handy but not a requirement)

Hmmm. Not sure. What IP address does norns report on its main menu screen (press K2)?

1 Like
#54

I have a similar problem.
first months no issues at all with wifi, now I have to restart several times until my antenna works and I can operate with Cuberduck on the Norns. Any tip?
Thanks!