[sf-lug] Connectivity problem

[Alex Kleider]

Rick,

Thank you very much for your response.

I followed up on all your suggestions and everything appeared to be as it should be.

Out of desperation I simply "down" and "up"ed the interface:

ifdown etho

ifup eth0

and after that all worked as it should. 

It appears that for reasons I can't fathom, /etc/network/interfaces 
isn't properly read during boot time (even though it is read enough such that ifconfig gives results indicating that all is well.) Forcing a re-read by putting 
ifdown and ifup in /etc/rc.local makes things work properly.  

I've heard people criticizing Debian's ARM packages and this may be an example of what they are talking about.  I've also had a problem with automounting of USB connected devices.
Thanks again.

alex

a_kleider at yahoo.com

--- On Thu, 7/12/12, Rick Smith <rick at rbsmith.com> wrote:

From: Rick Smith <rick at rbsmith.com>
Subject: Re: [sf-lug] Connectivity problem
To: alex at kleico.net
Cc: "Alex Kleider" <a_kleider at yahoo.com>, sf-lug at linuxmafia.com
Date: Thursday, July 12, 2012, 4:55 PM

In Linksys, you will need to add a static route for
10.0.11.0/24 to 172.24.16.100

In DreamPlug, you will need
     cat /proc/sys/net/ipv4/ip_forward
to output non-zero, which means traffic can be routed from one network 
to another inside the DreamPlug.  If it is zero, then:
     sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"

Also check its route table
     /sbin/route -n
And see that the default route (0.0.0.0) is to 172.24.16.254
If it is not:

     route add default gateway 172.24.16.254

Then from the laptop, ping 10.0.11.1 and 172.24.16.254 and then yahoo.com
Does that get you closer?

Rick Smith

On 07/12/2012 08:56 AM, Alex Kleider wrote:
>
> Here's a configuration problem I don't understand.
> The network is as follows:
> Internet comes in as a fixed IP on the external interface of a Linksys
> WRG54G(v6) router with settings all pretty much at defaults.
> Its internal interface has IP 172.24.16.254 serving a Class C
> 172.24.16.0/24 network.
> On that network is a DreamPlug with ethernet connected
> at fixed IP 172.24.16.100.
> This DreamPlug also has a WiFi interface which serves as a wifi Access Point
> with fixed IP 10.0.11.1 serving another Class C 10.0.11.0/24 network.
> When connected to that access point with my laptop as a client I get
> (by DHCP) IP 10.0.11.100 (as I should.)
>  From this laptop I get the correct response to the following commands:
> $ dig @127.0.0.1 linuxmafia.com +short
> $ dig @10.0.11.1 linuxmafia.com +short
> but
> $ dig @172.24.16.254 linuxmafia.com +short
> fails.
> $ ping yahoo.com
> provides me with yahoo's IP address but the ping does not go through and
> the lap top can not make use of the internet.
> I can't understand how this could be.
> Has anyone any suggestions as to what might be happening or how to trouble
> shoot further?
> (Thanks, by the way, to Rick Moen who taught us/me on this list some years
> ago how to use the dig command.)
>
>
>
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20120713/a901cfc5/attachment.html>