[David Kruger]

These are just the IP addresses I was told to use, what the underlying network resembles, I can only guess. Regardless, it seems to be working… for now 🙂

You are right saying that /etc/network/interfaces is ignored. I discovered this while digging further today..

Awaiting support response to the query. Will post it here for interest sake. Or make a new case referring to the AEP model rather.

[David Kruger]

Thanks for the suggestion… looks like the conduit firmware neglects (or needs to be done manually) to add the default route. This could be fixed using

route add default gw [gw address]

Annoyed, because this is the second network issue I have encountered in the last week.

• This reply was modified 7 years, 3 months ago by David Kruger.

[David Kruger]

Note: I am using the AEP model.

I would also like a solution to this. Have the exact same issue.
/etc/network/interfaces:

# Wired interface
auto eth0
iface eth0 inet static
address 10.5.90.6
netmask 255.255.255.252
gateway 10.5.90.5
post-up echo “nameserver 8.8.8.8” > /etc/resolv.conf

Looking at /etc/resolv.conf after reboot, there is nothing but the original one line.

This is really annoying!!!

• This reply was modified 7 years, 3 months ago by David Kruger.
• This reply was modified 7 years, 3 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 7 years, 3 months ago by David Kruger.

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

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

[Author]

Posts