Conduit not communicating on subnet

[David Kruger]

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

[John Klug]

255.255.255.0 would correspond to 192.168.2.6/24

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

[David Kruger]

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 6 years, 4 months ago by David Kruger.

[Alexandros Rapsomanikis]

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.

[David Kruger]

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 6 years, 4 months ago by David Kruger.

[David Kruger]

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 6 years, 4 months ago by David Kruger.

[Author]

Posts