[solving] piratebox.lan not work

Posted by ziomik 
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.
Now, this forum is in read-only mode. You find details Details hereContinue on /r/PirateBox
[solving] piratebox.lan not work
November 06, 2014 02:14PM
I followed the guide to install several times piratebox but I have a problem.
Once connected to the access point piratebox.lan does not work.
In the well-known ssh / etc / config / network does not exist and if I go on the browser to the IP 192.168.77.1, it works but the box to send the file is not available because the page calls piratebox.lan
Thank's



Edited 1 time(s). Last edit at 11/06/2014 10:57PM by ziomik.
Re: piratebox.lan not work
November 06, 2014 04:48PM
Do you have a static dns entry on the device which u use for testing?

Can you give me the output of the following commands from your piratebox:

ifconfig
ps -ef

thanks; Matthias
Re: piratebox.lan not work
November 06, 2014 05:01PM
Thanks for the quick reply .. here is how:

[root@alarmpi /]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.114  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::ba27:ebff:fe6d:8925  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:6d:89:25  txqueuelen 1000  (Ethernet)
        RX packets 1243  bytes 140094 (136.8 Kicool smiley
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 553  bytes 153490 (149.8 Kicool smiley
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 174  bytes 13340 (13.0 Kicool smiley
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 174  bytes 13340 (13.0 Kicool smiley
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.77.1  netmask 255.255.255.0  broadcast 192.168.77.255
        inet6 fe80::4633:4cff:fe4c:9fe  prefixlen 64  scopeid 0x20<link>
        ether 44:33:4c:4c:09:fe  txqueuelen 1000  (Ethernet)
        RX packets 1103  bytes 119040 (116.2 Kicool smiley
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 680  bytes 159732 (155.9 Kicool smiley
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@alarmpi /]# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  1 16:49 ?        00:00:06 /sbin/init
root         2     0  0 16:49 ?        00:00:00 [kthreadd]
root         3     2  0 16:49 ?        00:00:00 [ksoftirqd/0]
root         5     2  0 16:49 ?        00:00:00 [kworker/0:0H]
root         6     2  0 16:49 ?        00:00:00 [kworker/u2:0]
root         7     2  0 16:49 ?        00:00:00 [rcu_preempt]
root         8     2  0 16:49 ?        00:00:00 [rcu_bh]
root         9     2  0 16:49 ?        00:00:00 [rcu_sched]
root        10     2  0 16:49 ?        00:00:00 [khelper]
root        11     2  0 16:49 ?        00:00:00 [kdevtmpfs]
root        12     2  0 16:49 ?        00:00:00 [netns]
root        13     2  0 16:49 ?        00:00:00 [writeback]
root        14     2  0 16:49 ?        00:00:00 [kintegrityd]
root        15     2  0 16:49 ?        00:00:00 [bioset]
root        16     2  0 16:49 ?        00:00:00 [crypto]
root        17     2  0 16:49 ?        00:00:00 [kblockd]
root        18     2  0 16:49 ?        00:00:00 [khubd]
root        19     2  0 16:49 ?        00:00:00 [md]
root        20     2  0 16:49 ?        00:00:00 [kworker/0:1]
root        21     2  0 16:49 ?        00:00:00 [rpciod]
root        24     2  0 16:50 ?        00:00:00 [khungtaskd]
root        25     2  0 16:50 ?        00:00:00 [kswapd0]
root        26     2  0 16:50 ?        00:00:00 [fsnotify_mark]
root        27     2  0 16:50 ?        00:00:00 [nfsiod]
root        28     2  0 16:50 ?        00:00:00 [bioset]
root        37     2  0 16:50 ?        00:00:00 [kthrotld]
root        38     2  0 16:50 ?        00:00:00 [VCHIQ-0]
root        39     2  0 16:50 ?        00:00:00 [VCHIQr-0]
root        40     2  0 16:50 ?        00:00:00 [VCHIQs-0]
root        41     2  0 16:50 ?        00:00:00 [iscsi_eh]
root        42     2  0 16:50 ?        00:00:00 [dwc_otg]
root        43     2  0 16:50 ?        00:00:00 [DWC Notificatio]
root        44     2  0 16:50 ?        00:00:00 [raid5wq]
root        45     2  0 16:50 ?        00:00:00 [kmpathd]
root        46     2  0 16:50 ?        00:00:00 [kmpath_handlerd]
root        48     2  0 16:50 ?        00:00:00 [mmcqd/0]
root        49     2  0 16:50 ?        00:00:00 [deferwq]
root        50     2  0 16:50 ?        00:00:00 [kworker/u2:2]
root        51     2  0 16:50 ?        00:00:00 [jbd2/mmcblk0p2-]
root        52     2  0 16:50 ?        00:00:00 [ext4-rsv-conver]
root        62     2  0 16:50 ?        00:00:00 [scsi_eh_0]
root        63     2  0 16:50 ?        00:00:00 [usb-storage]
root        69     2  0 16:50 ?        00:00:00 [kworker/0:2]
root        79     1  0 16:50 ?        00:00:02 /usr/lib/systemd/systemd-journald
root        84     2  0 16:50 ?        00:00:00 [kworker/0:1H]
root        93     1  0 16:50 ?        00:00:00 /usr/lib/systemd/systemd-udevd
root       104     2  0 16:50 ?        00:00:00 [bcm2708_spi.0]
root       114     2  0 16:50 ?        00:00:00 [cfg80211]
systemd+   115     1  0 16:50 ?        00:00:00 /usr/lib/systemd/systemd-timesyncd
root       120     1  0 16:50 ?        00:00:00 /usr/bin/crond -n
avahi      121     1  0 16:50 ?        00:00:00 avahi-daemon: running [alarmpi.local]
root       123     1  0 16:50 ?        00:00:00 /usr/lib/systemd/systemd-logind
avahi      125   121  0 16:50 ?        00:00:00 avahi-daemon: chroot helper
dbus       126     1  0 16:50 ?        00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root       128     1  0 16:50 ?        00:00:03 /usr/bin/haveged -w 1024 -v 1
systemd+   137     1  0 16:50 ?        00:00:00 /usr/lib/systemd/systemd-networkd
root       141     1  0 16:50 ?        00:00:00 /usr/bin/sshd -D
systemd+   142     1  0 16:50 ?        00:00:00 /usr/lib/systemd/systemd-resolved
root       143     1  0 16:50 tty1     00:00:00 /sbin/agetty --noclear tty1 linux
root       144     1  0 16:50 ttyAMA0  00:00:00 /sbin/agetty --keep-baud 115200 38400 9600 ttyAMA0 vt102
root       146     1  0 16:50 ?        00:00:00 /usr/bin/minidlnad -P /run/minidlna/minidlna.pid
root       171     1  0 16:50 ?        00:00:00 /usr/sbin/hostapd /opt/piratebox/conf/hostapd.conf
nobody     176     1  0 16:50 ?        00:00:00 /usr/sbin/dnsmasq -x /var/run/piratebox_dnsmasq.pid -C /opt/piratebox/conf/dnsmasq_generated.conf
nobody     183     1  0 16:50 ?        00:00:01 python /opt/piratebox/bin/droopy -H piratebox.lan -d /opt/piratebox/share/Shared -m  -c  8080
nobody     191     1  0 16:50 ?        00:00:00 /usr/sbin/lighttpd -f /opt/piratebox/conf/lighttpd/lighttpd.conf
root       193   141  0 16:50 ?        00:00:00 sshd: root@pts/0   
root       195     1  0 16:50 ?        00:00:00 /usr/lib/systemd/systemd --user
root       196   195  0 16:50 ?        00:00:00 (sd-pam)  
root       198   193  0 16:50 pts/0    00:00:00 -bash
root       216   141  0 16:54 ?        00:00:00 sshd: root@pts/1   
root       218   216  0 16:54 pts/1    00:00:00 -bash
root       250     2  0 16:57 ?        00:00:00 [kworker/u2:1]
root       252   218  0 16:59 pts/1    00:00:00 ps -ef
Re: piratebox.lan not work
November 06, 2014 05:04PM
ok, everything is like expected.

Interesting would be
/opt/piratebox/conf/dnsmasq_generated.conf
, too.

How do you try to access the box? Which device? Can you give me some informations pls?
Re: piratebox.lan not work
November 06, 2014 05:16PM
Device is Raspberry Pi Modell B 512MB
AP: Alfa AWUS036NH
Storage: Trekstor HARD DISK ssd 80Gb / but I also tested with Usbstick Lexar 8Gb

I access the device from a mac connecting to Wifi Piratebox ssh

File dnsmasq_generated.conf :

#dont use resolv.conf
no-resolv
#dont recheck resolv.conf for changes
no-poll

#overwrite dns..
#dhcp-authoritative

# If you don't want dnsmasq to read /etc/hosts, uncomment the
# following line.
no-hosts
# or if you want it to read another file, as well as /etc/hosts, use
# this.
#addn-hosts=/etc/banner_add_hosts
## ^^^^^^  <- generated
interface=wlan0
dhcp-range=192.168.77.10,192.168.77.250,12h
address=/#/192.168.77.1
dhcp-leasefile=/opt/piratebox/tmp/lease.file
addn-hosts=/opt/piratebox/conf/hosts_generated
addn-hosts=/opt/piratebox/conf/hosts_mesh
Re: piratebox.lan not work
November 06, 2014 08:41PM
can you please verify, that you don't have a fixed DNS setting on your wifi profile?
Can you test it with a different device please?

The configuration looks 100% ok.

Matthias
Re: piratebox.lan not work
November 06, 2014 10:56PM
Fuck! The problem was just that I was losing time and thinking it was the installation! Thank you so much, I solved it!
Re: piratebox.lan not work
November 07, 2014 05:11AM
I'm glad, that's it smiling smiley

Have fun with your PirateBox
Matthias