On 11 Jan, 16:26, J David Ellis <nos...@home.org> wrote:
> Chrisjoy wrote:
> > On 10 Jan, 23:25, J David Ellis <nos...@home.org> wrote:
> > (snip)
>
> yesterday's reply to this failed to post. so here's another attempt...
>
> > 1) Try to ping 74.125.77.103.
> > If you're able to do so, you know you've got network conectivity.
>
> this produces four "request timed out" messages.
Then we can conclude you got no network connectivity. You told us that
this is only a problem when you add the last box in the path. Let us
call this box C, and the box closer to the net for B. For C to forward
packets to B, it needs IP on LAN side, IP on WAN side, subnet mask on
both, defalt gateway and at least one dns IP, OR it needs to be
transparent running as a dumb bridge. When running as a bridge, it
cannot filter any traffic, specially not DHCP and arp. Not in either
way. Other than that, WAN side must point to internet and LAN away
from internet using cables or wirless. Log into the box and look if
the box got necessary info. If ran as a bridge, you need to give
yourself (dell) a static IP in the subnet of the bridge connecting to
it's IP. If box are running as a router, you can connct to the dell's
default gateway, as this would be the box C if C is running a DHCP
server. A part of a reasonable troubleshoot you may want to put box C
in router mode, to see if it's working as such.
> > Then you can check out dns. Set LAN interface on your dell client to
> > 64.118.98.90.
>
> entering this ip address causes the subnet mask to be set to 255.0.0.0 instead
> of the usual 255.255.255.0 and the surf-gogle attempt yields "Firefox can't find
> the server atwww.google.com"
This should be used as your primary dns IP address and not as the IP
on the interface, but it doesn't matter you misunderstood this, cause
this was only meaningful if you were able to ping that google.com IP.
> if the current state of things changes, i'll be overjoyed to describe it as an
> "elegant/dynamical setup." :=)
I think we need some time to get there.
> on thing has changed since testing began. when the dell 'ethernet adapterlocal
> area connection' is enabled with 'obtain ip address automatically', the time to
> get the address has substantially increased. it used to take about five seconds
> to get an ip address 192.168.2.nnn, an alfa bridge address i think, and it now
> takes about a minute. the dell now gets:
>
> Connection-specific DNS Suffix *. :
> Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
> Physical Address. . . . . . . . . : 00-18-8B-DA-71-1A
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Autoconfiguration IP Address. . . : 169.254.1.38
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 169.254.1.38
>
> i wonder which which dhcp server is providing this?
Non. 169.254.*.* addresses are default randomized IP addresses when a
dhcp client does not get connected to DHCP server and got no fresh
lease.
|
Similar Threads
Linear Mode
