some_dev

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • July 16, 2019 at 4:20 am in reply to: Route table not persisting with openvpn client #28226
    some_dev
    Participant

    UPDATE:

    I have changed to using the GUI with a ‘CUSTOM’ open-vpn tunnel.
    Running over several hours shows that this problem is still present with this setup. Route are simply not persisting.
    I am thinking this could be a bug as this problem has occured with another multitech also.

    July 16, 2019 at 4:16 am in reply to: How connect a MultiConnect Conduit AP whit Loraserver #28225
    some_dev
    Participant

    Hi Marcelo,

    As I understand it you need to convert it to a packet forwarder.http://www.multitech.net/developer/software/lora/aep-lora-packet-forwarder/

    Otherwise the multitech behaves as a gateway and conflicts with the loraserver gateway bridge.
    The rest will be on the lora server docs.

    July 16, 2019 at 4:13 am in reply to: Problem factory reset mtcap AEP #28224
    some_dev
    Participant

    What’s stopping you from using the reset button?

    http://www.multitech.net/developer/software/aep/reset-button-behavior-for-aep/

    April 21, 2019 at 2:13 pm in reply to: MTCDT-LEU1-247A not being assigned default gateway #27672
    some_dev
    Participant

    Jeff,

    I shoudl ahve mentioned that I configured those settings on br0 whilst changing from another setting for testing. Was a matter of not being allowed to leave it blank.

    I’ll probably have to contact support directly on this one.

    April 18, 2019 at 7:03 am in reply to: MTCDT-LEU1-247A not being assigned default gateway #27654
    some_dev
    Participant

    Quick update;
    Setting static IP and gateway configs for eth0 has worked as a work around.

    April 18, 2019 at 3:49 am in reply to: MTCDT-LEU1-247A not being assigned default gateway #27653
    some_dev
    Participant

    Device in question ifconfig -a
    admin@mtcdt:~# ifconfig -a
    br0 Link encap:Ethernet HWaddr AA:D4:35:0F:3E:D2
    inet addr:127.0.0.1 Bcast:127.0.0.255 Mask:255.255.255.0
    inet6 addr: fe80::a8d4:35ff:fe0f:3ed2%3069557456/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B) TX bytes:648 (648.0 B)

    eth0 Link encap:Ethernet HWaddr 00:08:00:4A:44:13
    inet addr:192.168.88.58 Bcast:192.168.88.255 Mask:255.255.255.0
    inet6 addr: fe80::208:ff:fe4a:4413%3069557456/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:22524 errors:0 dropped:690 overruns:0 frame:0
    TX packets:4233 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1915359 (1.8 MiB) TX bytes:2511665 (2.3 MiB)
    Interrupt:23 Base address:0xc000

    gre0 Link encap:UNSPEC HWaddr 00-00-00-00-33-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:1476 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    gretap0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    BROADCAST MULTICAST MTU:1462 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)

    ip_vti0 Link encap:UNSPEC HWaddr 00-00-00-00-33-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:1364 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1%3069557456/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:37007 errors:0 dropped:0 overruns:0 frame:0
    TX packets:37007 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:5709876 (5.4 MiB) TX bytes:5709876 (5.4 MiB)

    sit0 Link encap:IPv6-in-IPv4
    NOARP MTU:1480 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-33-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:1480 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    wwan0 Link encap:Ethernet HWaddr BA:48:ED:41:9C:81
    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)

    April 18, 2019 at 3:48 am in reply to: MTCDT-LEU1-247A not being assigned default gateway #27652
    some_dev
    Participant

    Working device ifconfig -a
    admin@localhost:~# ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:08:00:4A:45:35
    inet addr:192.168.88.71 Bcast:192.168.88.255 Mask:255.255.255.0
    inet6 addr: fe80::208:ff:fe4a:4535%3069057744/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:94210 errors:0 dropped:891 overruns:0 frame:0
    TX packets:38462 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:7410119 (7.0 MiB) TX bytes:12882785 (12.2 MiB)
    Interrupt:23 Base address:0xc000

    gre0 Link encap:UNSPEC HWaddr 00-00-00-00-35-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:1476 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    gretap0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    BROADCAST MULTICAST MTU:1462 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)

    ip_vti0 Link encap:UNSPEC HWaddr 00-00-00-00-35-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:1364 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1%3069057744/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:87544 errors:0 dropped:0 overruns:0 frame:0
    TX packets:87544 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:17471915 (16.6 MiB) TX bytes:17471915 (16.6 MiB)

    sit0 Link encap:IPv6-in-IPv4
    NOARP MTU:1480 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    tunl0 Link encap:UNSPEC HWaddr 00-00-00-00-35-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:1480 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:0
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    April 18, 2019 at 3:27 am in reply to: MTCDT-LEU1-247A not being assigned default gateway #27649
    some_dev
    Participant

    Working device::
    route -n:
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 192.168.88.1 0.0.0.0 UG 0 0 0 eth0
    192.168.88.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

    I’ll include the (ifconfig -a)s in a seperate post

    Device in question::
    route -n:
    Destination Gateway Genmask Flags Metric Ref Use Iface
    127.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
    192.168.88.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

    For the device in question, cellular is not enabled.
    Looks like this could take a while alright.

    • This reply was modified 5 years ago by some_dev.
    • This reply was modified 5 years ago by some_dev.
    April 17, 2019 at 9:35 am in reply to: MTCDT-LEU1-247A not being assigned default gateway #27630
    some_dev
    Participant

    Jeff Hatch,

    Thanks for getting back so quick.
    It is the device that is not being assigned the gateway that has the extra interfaces.
    Overview of device in question(Note, WIFI is off):

    eth0–> LAN; ETHER; DHCP Client; 192.168.88.58/24; Bridge: —
    ppp0–> WAN; PPP; PPP
    wlan0–> WAN; WIFI_AS_WAN; DHCP Client; IP Addr: <blank>; Bridge: —
    wlan1–> LAN; WIFI_AP; IP Mode: DHCP Client; IP Addr:<blank>; Bridge:br0
    br0–> LAN, BRIDGE, Static, IP Addr: 0.0.0.0/24, Bridge: br0

    Working device:
    eth0–> LAN; ETHER; DHCP Client; 192.168.88.71/24; Bridge: —
    br0–> LAN; BRIDGE; IP Mode:<blank>; IP Addr: <blank>; Bridge: br0

    All WANs are disabled on both devices.
    What is weird to me is that all the wifi and PPP interfaces are displayed despite being disabled.

    Let me know if you require more details.

    • This reply was modified 5 years ago by some_dev.
    • This reply was modified 5 years ago by some_dev.
    • This reply was modified 5 years ago by some_dev.
    • This reply was modified 5 years ago by some_dev.
    • This reply was modified 5 years ago by some_dev.
    • This reply was modified 5 years ago by some_dev. Reason: Clarity
  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)