I don't know why you are asking us, you clearly know the most. Fix it yourself.
I offered the benefit of forty years of dealing with people that **** around with their kit. In my tens of thousands of calls fixing similar problems, and your clear lack of knowledge of the basics (such as correctly configuring your dhcp pool) my money is on it being YOUR configuration error.
Last edited:
Where is the alleged error in my configuration? At your place I would make small way
.
Code:
ubnt@ubirout:~$ show configuration
firewall {
all-ping enable
broadcast-ping disable
group {
network-group datenlan {
description t-netz
network 192.168.2.0/24
network 192.168.3.0/24
}
}
ipv6-name IPv6_WAN_IN {
default-action drop
description "IPv6 Pakete aus dem Internet ins LAN"
enable-default-log
rule 1 {
action accept
description "Erlaube bestehende Sitzungen"
state {
established enable
related enable
}
}
rule 2 {
action drop
state {
invalid enable
}
}
rule 5 {
action accept
description "erlaubt ICMPv6"
log disable
protocol icmpv6
}
}
ipv6-name IPv6_WAN_LOCAL {
default-action drop
description "IPv6 Pakete aus dem Internet zum Router"
enable-default-log
rule 1 {
action accept
description "Erlaubt bestehende Sitzungen"
log disable
state {
established enable
related enable
}
}
rule 2 {
action drop
log disable
state {
invalid enable
}
}
rule 5 {
action accept
description "Erlaubt ICMPv6"
log disable
protocol icmpv6
}
rule 110 {
action accept
description "Erlaubt DHCPv6 Pakete"
destination {
port 546
}
protocol udp
source {
port 547
}
}
}
ipv6-receive-redirects disable
ipv6-src-route disable
ip-src-route disable
log-martians enable
name WAN_IN {
default-action drop
description "WAN zu LAN"
enable-default-log
rule 1 {
action accept
description "Erlaube bestehende/in Verbindung stehende Prot."
destination {
}
state {
established enable
related enable
}
}
rule 3 {
action drop
description "Stoppe undefinierten Status"
state {
invalid enable
}
}
}
name WAN_IPTV {
default-action drop
description "IPTV Multicast"
enable-default-log
rule 1 {
action accept
description "Erlaube IPTV Multicast/UDP"
destination {
address 224.0.0.0/4
}
log disable
protocol udp
source {
}
}
rule 2 {
action accept
description "Erlaube IGMP"
log disable
protocol igmp
}
}
name WAN_LOCAL {
default-action drop
description "WAN zum Router"
enable-default-log
rule 1 {
action accept
description "Ping erlauben"
log disable
protocol icmp
}
rule 2 {
action accept
description "Erlaube Multicast"
destination {
address 224.0.0.0/4
}
log disable
protocol all
}
rule 7 {
action accept
description "Erlaube bestehende/in Verbindung stehende Prot."
state {
established enable
related enable
}
}
rule 8 {
action drop
description "stoppe undefinierten Status"
log enable
state {
invalid enable
}
}
}
name lan_in {
default-action accept
description "zwischen LAN"
rule 1 {
action accept
application {
custom-category Computer
}
description "alles erlauben"
destination {
group {
network-group datenlan
}
}
log disable
protocol all
source {
group {
network-group datenlan
}
}
state {
established enable
invalid disable
new enable
related enable
}
}
}
options {
mss-clamp {
interface-type pppoe
mss 1464
}
}
receive-redirects disable
send-redirects enable
source-validation disable
syn-cookies enable
}
interfaces {
ethernet eth0 {
description Internet
duplex auto
speed auto
vif 7 {
description Daten/VoIP
mtu 1500
pppoe 0 {
default-route auto
dhcpv6-pd {
pd 0 {
interface eth0 {
}
interface eth1 {
host-address ::aced:deca
no-dns
prefix-id 42
service slaac
}
prefix-length 56
}
prefix-only
rapid-commit enable
}
firewall {
in {
ipv6-name IPv6_WAN_IN
name WAN_IN
}
local {
ipv6-name IPv6_WAN_LOCAL
name WAN_LOCAL
}
}
ipv6 {
address {
autoconf
}
dup-addr-detect-transmits 1
enable {
}
}
mtu 1492
name-server auto
password ****************
user-id [email]0xxxxxxxxxxxxxxxxxxxx1@txxxxxxxne.de[/email]
}
}
vif 8 {
address dhcp
description IPTV
firewall {
local {
name WAN_IPTV
}
}
mtu 1500
}
}
ethernet eth1 {
address 192.168.2.1/24
description switch
duplex auto
firewall {
in {
name lan_in
}
local {
}
}
ipv6 {
dup-addr-detect-transmits 1
}
speed auto
}
ethernet eth2 {
address 192.168.3.1/24
description Gigaset
duplex auto
firewall {
in {
name lan_in
}
local {
}
out {
}
}
speed auto
}
loopback lo {
}
}
port-forward {
auto-firewall enable
hairpin-nat enable
lan-interface eth2
rule 1 {
description VoIP-SIP
forward-to {
address 192.168.3.115
port 5060-5076
}
original-port sip
protocol udp
}
rule 2 {
description VoIP-UDP
forward-to {
address 192.168.3.115
port 5004-5020
}
original-port 3478
protocol udp
}
wan-interface eth0
}
protocols {
igmp-proxy {
interface eth0.8 {
alt-subnet 0.0.0.0/0
role upstream
threshold 1
}
interface eth1 {
alt-subnet 0.0.0.0/0
role downstream
threshold 1
whitelist 232.0.0.0/8
whitelist 239.35.0.0/16
}
}
rip {
interface eth1
interface eth2
}
static {
}
}
service {
dhcp-server {
disabled false
hostfile-update disable
shared-network-name lan1 {
authoritative disable
subnet 192.168.2.0/24 {
default-router 192.168.2.1
dns-server 94.75.228.28
dns-server 62.141.58.13
lease 259200
start 192.168.2.2 {
stop 192.168.2.97
}
static-mapping xxxxxxxxxxxxxxxxxx {
ip-address 192.168.2.110
mac-address 08:60:6e:69:7b:75
}
static-mapping xxxxxxxxxxxxxx {
ip-address 192.168.2.100
mac-address 00:11:32:20:95:ab
}
static-mapping xxxxxxxxxxxx {
ip-address 192.168.2.170
mac-address 64:51:06:e3:12:aa
}
static-mapping xxxxxxxxxxxx {
ip-address 192.168.2.112
mac-address 00:23:14:72:a7:90
}
static-mapping xxxxxxxxxxx {
ip-address 192.168.2.103
mac-address b8:27:eb:c8:ee:06
}
static-mapping xxxxxxxxxx {
ip-address 192.168.2.150
mac-address 14:49:e0:68:f2:c0
}
static-mapping xxxxxxxxxxxx {
ip-address 192.168.2.135
mac-address b4:52:7e:84:45:86
}
static-mapping xxxxxxxxxx {
ip-address 192.168.2.210
mac-address 14:91:82:61:b1:e2
}
static-mapping xxxxxxxxxxxxx {
ip-address 192.168.2.105
mac-address 00:90:a9:f7:aa:da
}
static-mapping xxxxxxxxx {
ip-address 192.168.2.12
mac-address 00:0F:60:09:56:47
}
static-mapping xxxxxxxxxxx {
ip-address 192.168.2.116
mac-address 00:1f:1f:bc:07:b9
}
static-mapping xxxxxxxxxx {
ip-address 192.168.2.127
mac-address 7c:dd:90:1e:59:a0
}
static-mapping xxxxxxxxx {
ip-address 192.168.2.200
mac-address dc:ef:09:e1:5a:0e
}
static-mapping xxxxxxxxxx {
ip-address 192.168.2.102
mac-address f0:34:04:1e:c7:1d
}
}
}
shared-network-name lan2 {
authoritative disable
subnet 192.168.3.0/24 {
default-router 192.168.3.1
dns-server 192.168.3.1
dns-server 192.168.2.1
lease 86400
start 192.168.3.10 {
stop 192.168.3.89
}
static-mapping Gigaset {
ip-address 192.168.3.115
mac-address 7c:2f:80:46:28:54
}
}
}
use-dnsmasq disable
}
dns {
forwarding {
cache-size 150
listen-on eth1
listen-on eth2
}
}
gui {
http-port 80
https-port 443
older-ciphers enable
}
nat {
rule 5010 {
description "Maskiert ausgehende Adressen"
log disable
outbound-interface pppoe0
protocol all
type masquerade
}
}
ssh {
port 22
protocol-version v2
}
upnp {
}
}
system {
host-name ubirout
login {
user norb {
authentication {
encrypted-password ****************
plaintext-password ****************
}
full-name Norbert
level admin
}
user ubnt {
authentication {
encrypted-password ****************
plaintext-password ****************
}
full-name Norb
level admin
}
}
name-server 185.93.180.131
name-server 88.198.53.55
ntp {
server 0.ubnt.pool.ntp.org {
}
server 1.ubnt.pool.ntp.org {
}
server 2.ubnt.pool.ntp.org {
}
server 3.ubnt.pool.ntp.org {
}
}
syslog {
global {
facility all {
level notice
}
facility protocols {
level debug
}
}
}
time-zone Europe/Berlin
traffic-analysis {
custom-category Bypass-Proxies-and-Tunnels {
name igmp
name sip
}
custom-category Computer {
name Bxxxxxxx
name "Web File Transfer"
name Mxxx.com
}
custom-category File-Transfer {
name "xxxxxxxx"
}
custom-category Streaming-Media {
name rtp
name VLC
name xxxxxx
name "xxxxxxxx"
name "xxxxxxx"
}
custom-category ntp {
name ntp
}
dpi disable
export enable
}
}
traffic-control {
advanced-queue {
queue-type {
hfq VoIP {
description Telefon
host-identifier sip
max-rate 2mbit
subnet 192.168.3.0/24
}
}
}
}
vpn {
ipsec {
auto-firewall-nat-exclude disable
}
}
ubnt@ubirout:~$I lost interest in your problem when you called my post nonsense. I can see three glaring errors in your configuration. Sucks.
Good luck. With your obvious network superiority, you won't really need it, will you?
In my earlier post I stated that WLan worked with my HiFiBerry Digi+ Pro. I was mistaken, it doesn't. I was using a Digi+ until 2 weeks ago when I swopped to the Digi+Pro. Previously Wlan worked (I checked by swopping back). I should point out that I normally use wired lan for preference. Only changes I made were to system and MPD settings for the I2S devices. Although with the Digi+Pro WiFi shows as 100% signal strength with it's usual ip address it is not accessible.
I therefore have to concur with Tim and Melmac that there is a problem, but it is related to the Digi+ Pro, not Moode. My Digi +Pro is latest generation, so oscillator interference is a plausible explanation.
Nevertheless with the wired lan the system works well and sounds great. Thanks again to Tim for all his work.
I therefore have to concur with Tim and Melmac that there is a problem, but it is related to the Digi+ Pro, not Moode. My Digi +Pro is latest generation, so oscillator interference is a plausible explanation.
Nevertheless with the wired lan the system works well and sounds great. Thanks again to Tim for all his work.
Thanks for your answer.
Even if I must admit it left me a bit frustrated, I decided to investigate further and found (at least one of) the problem:
-It has nothing to do with my network or CIFS but has to do with the usb target I was trying to access to on the moode CIFS shares:
-If I copy to the SD card CIFS share (\\moode\SDCARD\*), speed is OK, but if I try to do anything on a USB target (\\moode\USB\My_Disk\*), then the speed is so worse than even a 1Mo file copy at 10-20Ko maxi, then gives a copy error before the end.
Same problem occurs whatever the USB target (usb key; 2,5 inch drive..)
I knew that the way the raspberry handle usb and network can cause bottleneck, but I didn't think it could be that worse in CIFS.
Did any of you experienced such situation, so I would consider it as "by design limitation", or should I investigate further ?
Thanks in advance.
Did you add touchscreen support by yourself or use an image? It may just be the screensaver coming on in which you can either extend the time (see post 6325), disable it, or just touch the screen to have it turn back on.
Last year there was a bug in the rpi software which caused the screen to not wake from sleep but that has been fixed for a while.
Sent from my iPad using Tapatalk
Think there looking into the problem of the Digi+Pro with it effecting the Pi's WiFi
https://github.com/raspberrypi/linux/issues/1588
Hi,
Try changing sync to async for your particular USB disks file system in the config file below, then reboot.
/etc/udisks-glue.conf
-Tim
If you are using a USB wifi adapter, it may significantly impact throughput. I don't tend to copy across the network to USB devices attached to the Pi, and I now exclusively use the Pi3, with its built-in wifi adapter.
One easy test would be to connect using Ethernet and test your throughput.
Do you have the make and model of the wifi adapter you're using? Not all drivers are created equal...
I think they have concluded that the solution resides in a physical redesign.
IIRC you can send your faulty unit back for refund or replacement.
static IP
It's worked out
Fresh image in the raspberry.
External Wlan at the Rasberry (hifiberry disturbs)
Turn on the Rasberry
In the router are displayed 4 leases, each 2 for each interface (eth0, internal wlan0). This happens only with Moode os, I've tested with several other clients, including Raspberry with other os.
The moode os with "moode.local call.
configure SSID, PSK
Disable the internal WLAN in the Webfrontend Configure system.
Moode os reboot.
With putty etc/network/interfaces and ifconfig.
Determine the valid Ip for Wlan0 (external)
In the router, the IP for the Wlan0 map.
Check if this IP, Moode os is accessible (not always the case)
Clear all leases in the router
Reboot moode os
Moode os with the valid IP call.
Otherwise the path to the NAS can not be saved
Configure - Network - here Wifi (wlan0) is on DHCP field, the gateway field, DNS field, IP field is not visible and thus not adjustable.
All functions in the LAN are given, the playing of Internet radio fails.
Wifi (wlan0) field switch to static, enter IP, gateway, DNS.
Then Internet radio is also available.
Moode os has its static IP
All attempts to set the IP directly at the first call of the Moode os fail even though in the config files correct values after securing the configuration are registered.
My usual way with all other clients, Ethernet cable to a client, go to the configuration menu, activate Wlan interface, static IP, subnet mask, if necessary enter DNS, save configuration.
Done.
With the moode os is walked obviously a special way, or it is seriously not planned to set a static IP.
But the fact is, the Moode os is more stable in contrast to rune audio or volumio
It's worked out
Fresh image in the raspberry.
External Wlan at the Rasberry (hifiberry disturbs)
Turn on the Rasberry
In the router are displayed 4 leases, each 2 for each interface (eth0, internal wlan0). This happens only with Moode os, I've tested with several other clients, including Raspberry with other os.
The moode os with "moode.local call.
configure SSID, PSK
Disable the internal WLAN in the Webfrontend Configure system.
Moode os reboot.
With putty etc/network/interfaces and ifconfig.
Determine the valid Ip for Wlan0 (external)
In the router, the IP for the Wlan0 map.
Check if this IP, Moode os is accessible (not always the case)
Clear all leases in the router
Reboot moode os
Moode os with the valid IP call.
Otherwise the path to the NAS can not be saved
Configure - Network - here Wifi (wlan0) is on DHCP field, the gateway field, DNS field, IP field is not visible and thus not adjustable.
All functions in the LAN are given, the playing of Internet radio fails.
Wifi (wlan0) field switch to static, enter IP, gateway, DNS.
Then Internet radio is also available.
Moode os has its static IP
All attempts to set the IP directly at the first call of the Moode os fail even though in the config files correct values after securing the configuration are registered.
My usual way with all other clients, Ethernet cable to a client, go to the configuration menu, activate Wlan interface, static IP, subnet mask, if necessary enter DNS, save configuration.
Done.
With the moode os is walked obviously a special way, or it is seriously not planned to set a static IP.
But the fact is, the Moode os is more stable in contrast to rune audio or volumio
Find it odd that the HiFiBerry DAC+ is made to run on a Pi and there testing procedure didn't picked up that there could be a problem
It's like Pioneer making a car stereo which doesn't work when used in a car
Feature possibility - USB CD player
Hello
I very much like my NAS(flac)>Pi3(Moode)>i2s DAC>amp setup.
It would be handy however to be able to quickly play the odd CD, i.e. without having to rip, copy it across to NAS then update the moode library.
Which leads me to wonder... could it be possible plug a USB optical drive into the Pi3 and have moode use it as a source?
Here's to wishful thinking
Oli
Hello
I very much like my NAS(flac)>Pi3(Moode)>i2s DAC>amp setup.
It would be handy however to be able to quickly play the odd CD, i.e. without having to rip, copy it across to NAS then update the moode library.
Which leads me to wonder... could it be possible plug a USB optical drive into the Pi3 and have moode use it as a source?
Here's to wishful thinking
Oli
Here is a recent discussion, you may be able to find more if you search the thread.
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-614.html#post4961217
In its base configuration Moode is primarily Audio and has the ability to enable a UPNP interface for controlling the playback of music. The DNLA spec is based on UPNP so you will get some of what you want.
If you want to play music controlled by a phone application such as Bubble, Lumin or Linn Kazoo then yes you can do that with Moode.
As for the right Hardware Combo , there is a lot of personal choice, I use a Pi3 and HiFi Berry Digi+ to an external Dac and a PI2 with an IQAudio Dac couldn't confirm they are the best choices. Search this thread as somewhere Tim mentions what he uses and you can be sure they are tested thoroughly.
At the moment consider avoiding the HiFiberry Pro stuff if you are a newcomer as there are issues with these boards and RPI3 boards wireless.
If possible use a wired connection, for high bit rate music especially.