The modem is being assigned an IP address by the network operator, and there is some data being sent.
But when testing with a loramote, all information is sent via the ethernet conection instead.
Bearer priorities are set to “ppp0, eth0, eth1”.
Checking the log, I find this:
daemon.warn pppd[1214]: Could not determine remote IP address: defaulting to 10.64.64.64
Here is the network configuration.
# defines hostname prefix
HOSTNAME=Wirgrid_
# activates lo0 at startup
LOOP=yes
# activates eth0 at startup
ETHERNET=yes
# claims dhcp request on eth0
ETHDHCP=yes
# if fix addr is selected on eth0
ETHIPADDR=192.168.4.155
ETHNETMASK=255.255.255.0
ETHBROADCAST=192.168.4.255
ETHGATEWAY=192.168.4.1
# Disable Ethernet Power if no link detected
ETHAUTODETECT=no
# activates eth0:1 at startup
ETHERVIRT=no
# activates sl0 at startup
SLIP=yes
# Selector operator APN
GPRSAPN=data.tre.se
# Enter pin code if activated
GPRSPIN=
# Update /etc/resolv.conf to get dns facilities
GPRSDNS=yes
# PAP authentication
GPRSUSER=
GPRSPASSWORD=
# activates router at startup
ROUTER=yes
DEVOUT=eth0
DEVIN=ppp0
DHCPD=yes
DHCPDSTARTADDRPOST=90
DHCPDSTOPADDRPOST=120
# manual DNS server
DNSSERVER1=8.8.8.8
DNSSERVER2=8.8.4.4
#Bearer priority order
BEARERS_PRIORITY="ppp0,eth0,eth1"
That I have, I have to start gprs manually and set ppp0 as the default interface manually. After doing that, the 3G backhaul works perfectly. Why gprs isn’t starting and being set as the default root automatically, I do not know.
<!-- ############## connection parameters ############## -->
<!-- nb of second to retry to connect to server if connection failed-->
<CONNECT retry_timeout="10" />
<!-- port nunmber for local application kms connection -->
<CONNECT kms_port="35035" />
<!-- enable the autoconnect feature (YES/NO) -->
<CONNECT auto_connection="YES" />
Well all up & running, my gateway is receiving packets, and sending them to TTN… here the example of my node that sent hundreds of them already successfully through my both gateways… also the AA555A0008060760 gw (the kerlink)… http://thethingsnetwork.org/api/v0/nodes/02030800/
@niels
Is the kerlink sending status packages? Probably not as that would make the gateway appear on the API page and on ttnstatus.org. (tcpdump will show packets with readable (in the ascii part text containing “{“stat”” if it is)
For status messages you should have (fake) GPS enabled in the configuration. (For fake you’ll need to set the coordinates as well, but I think kerlink has real GPS??)
maybe it would be nice to be able to automatically alter the status messages in both the api and the TTN-specific packetforwarder software so that the “remark” on ttnstatus.org is also automatically filled… instead of having to manual: New Gateway Registration ?
i’ve seen local_conf.json files having stuff like:
"gateway_conf": {
/* Email of gateway operator, max 40 chars*/
"contact_email": "",
/* Public description of this device, max 64 chars */
"description": ""
}
Yes! and also the interactive map with long latitude. I beleve those field are only possible with the poly packed forwarder. But that’s it the one in de dota file I updated yesterday.
Greeting. Where I can configure PPPoE connection in Kerlink Gateway? Now, I can connecting with 3G (i have staion with 3g modem modification) and DHCP. But, when I haven’t DHCP-server, how my gateway will receive the Internet?
If you’re still figuring out how to configure the Kerlink to use GPRS/3G, things to consider are: choose your ip_link address in /knet/knetd.xml wisely as the auto connect mechanism depends on this. Also make sure the poly packet forwarder is restarted whenever there is an interface change (i.e. ppp0 comes up/goes down) as it will break your IP config if it isn’t.
I`m trying to add a Kerklink Gateway to the TheThingsNetwork but the local config file seems to be invalid. I cannot figure out how to get the gateway_ID correct. It is MAC based right?
WIRELESS & SENSING PRODUCTS
For example, if the gateway’s MAC address is 02:4B:08:04:00:53, the gateway_ID in local_conf.json will be “xxxxxxxx08040053”. The last 8 digits of the gateway_ID correspond to the last 8 digits of the MAC address.