Ian Bester

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: MTCDT-LEU1-247A Firmware 6.3.0 network issues #33484
    Ian Bester
    Participant

    Current eth0 set-up:

    LAN, DHCP enabled

    in reply to: MTCDT-LEU1-247A Firmware 6.3.0 network issues #33483
    Ian Bester
    Participant

    ifconfig output:

    eth0      Link encap:Ethernet  HWaddr 00:08:00:4A:28:7D  
              inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:6243 errors:0 dropped:0 overruns:0 frame:0
              TX packets:6341 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:847621 (827.7 KiB)  TX bytes:4304898 (4.1 MiB)
              Interrupt:24 Base address:0xc000 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:110284 errors:0 dropped:0 overruns:0 frame:0
              TX packets:110284 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:13330938 (12.7 MiB)  TX bytes:13330938 (12.7 MiB)
    
    wlan0     Link encap:Ethernet  HWaddr 00:23:A7:C6:A6:90  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    nslookup google.com output:

    Server:		127.0.0.1
    Address:	127.0.0.1:53
    
    ** server can't find google.com: REFUSED
    
    ** server can't find google.com: REFUSED
    in reply to: LoRaWAN > Network Settings NOT on the left sidebar #27250
    Ian Bester
    Participant

    Hi Steve

    Yes, it does show in the home screen.

    -Ian

    in reply to: Can't connect via browser to new AEP #22166
    Ian Bester
    Participant

    Hi Steve

    Thanks. Yes, I’ve changed to a static IP on the same subnet, and I can ping 192.168.2.1. Still can’t reach it if try http or https://192.168.2.1

    Ian

    in reply to: Can't connect via browser to new AEP #22164
    Ian Bester
    Participant

    To further clarify.

    I can ping 192.168.2.1 (if I change my network config to a static IP of 192.168.2.28), and the gateway is still in 192.168.2.1 and on static IP.

    Still get the same error though and can’t connect to the GUI.

Viewing 5 posts - 1 through 5 (of 5 total)