Conduit not communicating on subnet

Home › Forums › Conduit: AEP Model › Conduit not communicating on subnet

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • December 6, 2017 at 4:47 pm #22028
    David Kruger
    Participant

    Hi,

    I have an AEP condiut with which I have configured eth0 as follows:

    Addr: 192.168.2.6/30

    My PC (directly connected) using 192.168.2.5 cannot see the conduit. Pinging it returns ‘connect: Network is unreachable‘, Am I missing something here? I haven’t configured anything additional. To gain access to the web interface again, I use the debug port to login and update the netmask to 255.255.255.0.

    Thanks in advance

    AEP version: 1.4.3

    December 6, 2017 at 5:07 pm #22031
    John Klug
    Moderator

    255.255.255.0 would correspond to 192.168.2.6/24

    Not sure if it will fix the issue, but it might

    December 6, 2017 at 7:34 pm #22032
    David Kruger
    Participant

    Problem is that the ISP where the conduit is kept has only allocated that subnet (192.168.2.4/30) consisting of 2 host addresses for me. I cannot use /24 or 255.255.255.0.

    I’m restricted to use only:
    192.168.2.5 and
    192.168.2.6

    • This reply was modified 7 years, 4 months ago by David Kruger.
    December 7, 2017 at 4:05 am #22037
    Alexandros Rapsomanikis
    Participant

    I believe you should configure a default gateway for both of your devices – PC and Conduit.

    Are you trying to connect to your conduit remotely? I’m asking this because the address your ISP is giving out is a private subnet and unless you’re connected to the same router or port forwarding is not enabled, you won’t be able to access it.

    December 7, 2017 at 7:30 am #22041
    David Kruger
    Participant

    Hi Alexandros

    The gateway is only used to contact anything outside the subnet, in my case, I am contacting an address inside as follows:

    PC (192.168.2.5/30) <—————–> Conduit (192.168.2.6/30)

    This should work just the same as (which works):

    PC (192.168.2.5/24) <—————–> Conduit (192.168.2.6/24)

    the second part of your reply will only apply once I add it to the ISPs router (which i have access to). For security reasons, they give me the subnet, in which one address will point to gateway and the other will be the local address of the conduit. The conduit will then interact with a public IP using the configured gateway. But this has nothing to do with the current setup.

    • This reply was modified 7 years, 4 months ago by David Kruger.
    December 8, 2017 at 6:44 am #22062
    David Kruger
    Participant

    So it seems that after the conduit is booted, and I issue:

    ifconfig eth0 down
    ifconfig eth0 up

    I suddenly get access to the conduit at 192.168.2.6/30.

    Is there maybe a way to do this automatically during boot as a work around?

    EDIT: I have implemented a crontab on boot and every two minutes to check connectivity and if the other host is not responding, I cycle eth0. This works well, but I feel like it is totally unnecessary.

    • This reply was modified 7 years, 4 months ago by David Kruger.
  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.