I corrected that typo. Sorry about the trouble.
On Tuesday, June 30, 2020 at 12:51:01 AM UTC-7, Zsolt Máté wrote:
>
> There was a typo in the wiki, edited it.
> Instead of domain_name_servers there was domain_name_server.
>
>
>
> On Tuesday, June 30, 2020 at 7:39:11 PM UTC+12, Zsolt Máté wrote:
>>
There was a typo in the wiki, edited it.
Instead of domain_name_servers there was domain_name_server.
On Tuesday, June 30, 2020 at 7:39:11 PM UTC+12, Zsolt Máté wrote:
>
> Did anything change with the latest raspberry pi images? I'm trying to do
> a clean install, downloaded the last image (bas
Did anything change with the latest raspberry pi images? I'm trying to do a
clean install, downloaded the last image (based on Debian Buster),
installed and configured hostapd as per wiki.
Now the DNS is not resolving any address. I can ping external IP addresses
while I'm connected to the pi vi
Reinstalling hostapd solved the issue.
On Thursday, June 6, 2019 at 4:57:26 PM UTC+12, Zsolt Máté wrote:
>
> To be honest, I can't find anything related to hostapd in the logs.
> sudo cat /var/log/syslog | grep hostapd returns nothing.
> If I search my archived logs I can see the handshakes, etc,
To be honest, I can't find anything related to hostapd in the logs.
sudo cat /var/log/syslog | grep hostapd returns nothing.
If I search my archived logs I can see the handshakes, etc, but nothing in
my latest ones.
On Thursday, June 6, 2019 at 4:48:51 PM UTC+12, Scott Grayban wrote:
>
> Have you
Have you looked at the logs when starting hostapd?
On Jun 5, 2019, 9:24 PM, at 9:24 PM, "Zsolt Máté" wrote:
>Anyone having issues with this?
>I had a power outage a few days ago and ever since I can't get hostapd
>to
>work/start.
>Somehow my wlan0 is not starting up and not broadcasting it's SS
Anyone having issues with this?
I had a power outage a few days ago and ever since I can't get hostapd to
work/start.
Somehow my wlan0 is not starting up and not broadcasting it's SSID anymore.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To u
On Thursday, April 4, 2019 at 6:48:06 AM UTC-4, bthoven wrote:
>
> That was what I have been trying to do, the sniff, without success. Could
> you suggest how should I set the sniff thing.
>
> Now my ObserverIP has local ip 192.168.2.122. It directs the data to my
> live weewx 192.168.2.3 port 55
My 'live' weewx server ip is 192.168.2.3 (via wifi), my ObserverIP is
192.168.2.122 (wired connect to router) and its destination server is
192.168.2.3 port 55. Interceptor setting in weewx.conf:[Interceptor]
# This section is for the network traffic interceptor driver.
# The driver
Post your settings.
On Thursday, April 4, 2019 at 3:48:06 AM UTC-7, bthoven wrote:
>
> Hi m,
> That was what I have been trying to do, the sniff, without success. Could
> you suggest how should I set the sniff thing.
>
> Now my ObserverIP has local ip 192.168.2.122. It directs the data to my
> l
Hi m,
That was what I have been trying to do, the sniff, without success. Could
you suggest how should I set the sniff thing.
Now my ObserverIP has local ip 192.168.2.122. It directs the data to my
live weewx 192.168.2.3 port 55 which runs Interceptor in listening mode.
Thanks
On Thu, 4 Apr 2019
On Thursday, April 4, 2019 at 1:12:22 AM UTC-4, Chotechai Piyavongsiri
wrote:
>
> As I'm setting up and testing another weewx server and would like to
> receive live data from the same IP Observer without changing the
> destination IP/port, do you think your approach would allow two weewx
> ser
I have no clue about running 2 weewx to get the same data... nothing to
lose if you try.
As for the hostapd it's as close to weewx for dummies as I can get :P Just
follow it step by step as many have done it without any issues.
Hostapd does require your station to connect to that WIFI to work a
Hi Scott,
I've been running weewx on ubuntu for a few years using Interceptor
(listening mode) to receive data direct from my IP Observer (the firmware
still allows me to specify the destination server IP and Port).
As I'm setting up and testing another weewx server and would like to
receive l
Look in the config file for the DHCP server.
You should find something like this:
# Fixed IP addresses can also be specified for hosts.
Then, you can use the MAC address of the console and whatever IP you wish
it to have.
Just be aware that the fixed IP has to be outside the DHCP range, so you'd
BTW that's only if your WS is the only one that's connecting to the hostapd
!!
I can't say if it will change if another device connects and *non should
because it will cause to much interference with port 80*.
On Saturday, January 5, 2019 at 5:45:26 PM UTC-8, Zsolt Máté wrote:
>
> Good to know.
Oh that IP for the LAN with hotsapd won't change. So your weather
station won't get a new IP on the 10.x network.
On Saturday, January 5, 2019 at 5:34:57 PM UTC-8, Zsolt Máté wrote:
>
> The issue is not the eth0, that I've reserved in my router.
> The problem could be the indoor unit, that c
Good to know. Thanks for the information.
On Sunday, January 6, 2019 at 2:38:32 PM UTC+13, Scott Grayban wrote:
>
> Oh that IP for the LAN with hotsapd won't change. So your weather
> station won't get a new IP on the 10.x network.
>
>
> On Saturday, January 5, 2019 at 5:34:57 PM UTC-8, Zsolt
The issue is not the eth0, that I've reserved in my router.
The problem could be the indoor unit, that connects to wlan0 and receives
the 10.*.*.* IP address.
On Sunday, January 6, 2019 at 12:24:48 PM UTC+13, Scott Grayban wrote:
>
> Glad you got it working !!
>
> Most routers have reserve DHCP s
That's what I'm researching right now.
On Sunday, January 6, 2019 at 12:11:31 PM UTC+13, Scott Grayban wrote:
>
> Use reserved DHCP then.
>
> On Saturday, January 5, 2019 at 3:09:42 PM UTC-8, Zsolt Máté wrote:
>>
>> If you're asking me, yes, I did. After reading your reply, I switched to
>> su an
Glad you got it working !!
Most routers have reserve DHCP settings. So I'm sure yours does also.
On Saturday, January 5, 2019 at 3:18:33 PM UTC-8, Zsolt Máté wrote:
>
> That's what I'm researching right now.
>
> On Sunday, January 6, 2019 at 12:11:31 PM UTC+13, Scott Grayban wrote:
>>
>> Use rese
Use reserved DHCP then.
On Saturday, January 5, 2019 at 3:09:42 PM UTC-8, Zsolt Máté wrote:
>
> If you're asking me, yes, I did. After reading your reply, I switched to
> su and ran the command as root. Tanks for the tutorial.
>
> The only thing I don't like (but I can live with it) is the DHCP.
If you're asking me, yes, I did. After reading your reply, I switched to su
and ran the command as root. Tanks for the tutorial.
The only thing I don't like (but I can live with it) is the DHCP. In case
the indoor unit looses DC power for any reason, it may receive a new IP
address. Then someon
Did you get it working ?
On Friday, January 4, 2019 at 7:21:17 PM UTC-8, Zsolt Máté wrote:
>
> Thanks, I was running it with sudo.
>
> On Saturday, January 5, 2019 at 4:17:32 PM UTC+13, Scott Grayban wrote:
>>
>> Run that as root
>> On Jan 4, 2019, at 7:15 PM, "Zsolt Máté" wrote:
>>>
>>> I can't
Think this might not be a raspbian issue as such. iptables-save is run with
privileges but the redirection to the file is run by your existing shell
which does not (necessarily) have sufficient privileges. Try using the same
command and redirecting to /var/tmp/iptables.ipv4.nat (or some other wi
sudo won't work correctly for some reason for certain commands in raspbian.
On Friday, January 4, 2019 at 7:21:17 PM UTC-8, Zsolt Máté wrote:
>
> Thanks, I was running it with sudo.
>
> On Saturday, January 5, 2019 at 4:17:32 PM UTC+13, Scott Grayban wrote:
>>
>> Run that as root
>> On Jan 4, 2019
Thanks, I was running it with sudo.
On Saturday, January 5, 2019 at 4:17:32 PM UTC+13, Scott Grayban wrote:
>
> Run that as root
> On Jan 4, 2019, at 7:15 PM, "Zsolt Máté" >
> wrote:
>>
>> I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
>> It returns: -bash: /etc/iptables.ipv4.nat: P
Run that as root
On Jan 4, 2019, 7:15 PM, at 7:15 PM, "Zsolt Máté" wrote:
>I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
>It returns: -bash: /etc/iptables.ipv4.nat: Permission denied
>
>--
>You received this message because you are subscribed to a topic in the
>Google Groups "weew
I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
It returns: -bash: /etc/iptables.ipv4.nat: Permission denied
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an ema
Created
https://github.com/weewx/weewx/wiki/hostapd-WiFi-setup-for-Interceptor-driver
On Thursday, January 3, 2019 at 10:10:53 AM UTC-8, G Hammer wrote:
>
> The wiki
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this grou
The wiki
On Thu, Jan 3, 2019 at 12:43 PM Scott Grayban wrote:
> I got the hostapd how-to written. Where should I post it at ?
>
> On Wednesday, January 2, 2019 at 6:29:38 AM UTC-8, G Hammer wrote:
>>
>> That would be great. You had a shorter route than I did. Not a Pi, but
>> same idea.
>>
> --
I got the hostapd how-to written. Where should I post it at ?
On Wednesday, January 2, 2019 at 6:29:38 AM UTC-8, G Hammer wrote:
>
> That would be great. You had a shorter route than I did. Not a Pi, but
> same idea.
>
--
You received this message because you are subscribed to the Google Groups
wow I didn't go through that much at all !!
On Wednesday, January 2, 2019 at 6:29:38 AM UTC-8, G Hammer wrote:
>
> That would be great. You had a shorter route than I did. Not a Pi, but
> same idea.
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" gro
That would be great. You had a shorter route than I did. Not a Pi, but same
idea.
sudo xed /etc/default/grub
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
sudo update-grub
sudo reboot
sudo apt-get install hostapd
iw reg get
sudo iw reg set US
sudo xed /etc/hostapd/hostapd.conf
I'll do a write up on how to install and use hostapd for weeWX since I
turned into a semi-pro on it today and while it's still fresh in my head.
On Wednesday, January 2, 2019 at 6:15:31 AM UTC-8, G Hammer wrote:
>
> Glad it was hardware, else the error made little sense.
> Yep, the Pi and SD car
Glad it was hardware, else the error made little sense.
Yep, the Pi and SD cards are always something to look at. And have a backup
for!
Good you're up and running.
On Wednesday, January 2, 2019 at 9:11:23 AM UTC-5, Scott Grayban wrote:
>
> Ok I got hostapd working on the same PI as weeWX and th
Very happy and tired !!!
Jan 2 06:06:10 raspberrypi weewx[1845]: restx: MQTT: Published record
2019-01-02 06:05:04 PST (1546437904)
Jan 2 06:07:10 raspberrypi weewx[1845]: interceptor: MainThread:
unrecognized parameter hourlyrainin=0.00
Jan 2 06:07:10 raspberrypi weewx[1845]: interceptor: Ma
37 matches
Mail list logo
