[U-Boot] ip address confusion.

[U-Boot] ip address confusion.

[David Collier]

Our office network runs on 

10.213.1.1/24

so all addresses in 10.212 and 10.213 should be local.

and I have a TFTP server on 10.213.1.105

if I set my office pc to 10.212.0.99 I can ping 10.213.1.105

so far so good

-----------------------------------------
if I set u-boot up so the printenv at power-on looks like

ethaddr=00:90:46:20:000:99
eth1addr=00:90:46:20:100:99
ipaddr=10.212.000.99
serverip=10.213.1.105
gatewayip=10.213.1.1
netmask=255.254.0.0
bootfile=99/uImage
ethact=macb1

then if I do

    ping 10.213.1.105

it fails.

but after setting 

    setenv ipaddr 10.213.0.99

it works

Can anyone suggest why?

David Collier

www.dexdyne.com

[U-Boot] ip address confusion.

[Jerry Van Baren]

David Collier wrote:
> Our office network runs on 
> 
> 10.213.1.1/24

10.213.1.1/15 per your netmask.

> so all addresses in 10.212 and 10.213 should be local.
> 
> and I have a TFTP server on 10.213.1.105
> 
> if I set my office pc to 10.212.0.99 I can ping 10.213.1.105
> 
> so far so good
> 
> -----------------------------------------
> if I set u-boot up so the printenv at power-on looks like
> 
> ethaddr=00:90:46:20:000:99
> eth1addr=00:90:46:20:100:99
> ipaddr=10.212.000.99
> serverip=10.213.1.105
> gatewayip=10.213.1.1
> netmask=255.254.0.0
> bootfile=99/uImage
> ethact=macb1
> 
> then if I do
> 
>     ping 10.213.1.105
> 
> it fails.
> 
> but after setting 
> 
>     setenv ipaddr 10.213.0.99
> 
> it works
> 
> Can anyone suggest why?

It smells like your netmask is not what you think it is.  The difference 
in the addresses is .212. vs. .213. and it sounds like a gateway issue. 
  Note that your gateway is in .213. land so, if your netmask is 
255.255.0.0, the gateway will not be reachable from .212. land.

Please capture your console interaction and post it directly.  Your list 
above is playing Chinese Whispers, resulting in unreliable communications.
   <http://en.wikipedia.org/wiki/Chinese_whispers>
You may also want to do a printenv before and after (critical) commands 
to verify things didn't change on you.

FWIIW, when someone asks me "why doesn't the system do X" or says "the 
system did X", I *always* say "show me" - users often filter out 
important information because they don't realize that it is important... 
which is exactly why the system isn't doing X and exactly why the user 
is surprised by that.

> David Collier

gvb

[U-Boot] ip address confusion.

[Ben Warren]

David,

On Fri, Oct 23, 2009 at 5:32 AM, David Collier
<from_denx_uboot@dexdyne.com>wrote:

>
> Our office network runs on
>
> 10.213.1.1/24
>
> so all addresses in 10.212 and 10.213 should be local.
>
As Jerry mentioned, this is not correct.  10.212 and 10.213 are on different
subnets if your mask is 24 bits in size:

10.212 = 0b00001010.0b11010100
10.213 = 0b00001010.0b11010101

As you can see, they only have 15 bits in common, so for them to be in the
same subnet (no routing required) your network would have to be
10.212.0.0/15 at the minimum.

>
> and I have a TFTP server on 10.213.1.105
>
> if I set my office pc to 10.212.0.99 I can ping 10.213.1.105
>
If this is so and the netmask listed above is correct, there's probably a
router on 10.212.  Running traceroute will tell you for sure.

>
> so far so good
>
> -----------------------------------------
> if I set u-boot up so the printenv at power-on looks like
>
> ethaddr=00:90:46:20:000:99
> eth1addr=00:90:46:20:100:99
> ipaddr=10.212.000.99
> serverip=10.213.1.105
> gatewayip=10.213.1.1

Try setting this to 10.212.1.1 and see what happens.

> netmask=255.254.0.0
> bootfile=99/uImage
> ethact=macb1
>
> then if I do
>
>    ping 10.213.1.105
>
> it fails.
>
> but after setting
>
>    setenv ipaddr 10.213.0.99
>
No surprise.

>
> it works
>
> Can anyone suggest why?
>
> David Collier
>
> regards,
Ben

[U-Boot] ip address confusion.

[David Collier]

pardon me everyone - I'm an idiot.

Sorry.

David



In article <memo.20091023133244.2092V@postmaster+dexdyne.com.cix.co.uk>,
from_denx_uboot at dexdyne.com (David Collier) wrote:

> *From:* "David Collier" <from_denx_uboot@dexdyne.com>
> *To:* u-boot at lists.denx.de
> *Date:* Fri, 23 Oct 2009 13:32 +0100 (BST)
> 
> Our office network runs on 
> 
> 10.213.1.1/24
> 
> so all addresses in 10.212 and 10.213 should be local.
> 
> and I have a TFTP server on 10.213.1.105
> 
> if I set my office pc to 10.212.0.99 I can ping 10.213.1.105
> 
> so far so good
> 
> -----------------------------------------
> if I set u-boot up so the printenv at power-on looks like
> 
> ethaddr=00:90:46:20:000:99
> eth1addr=00:90:46:20:100:99
> ipaddr=10.212.000.99
> serverip=10.213.1.105
> gatewayip=10.213.1.1
> netmask=255.254.0.0
> bootfile=99/uImage
> ethact=macb1
> 
> then if I do
> 
>     ping 10.213.1.105
> 
> it fails.
> 
> but after setting 
> 
>     setenv ipaddr 10.213.0.99
> 
> it works
> 
> Can anyone suggest why?
> 
> David Collier
> 
> www.dexdyne.com
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 


David Collier

www.dexdyne.com

[U-Boot] ip address confusion.

[David Collier]

right - pardon my stupidity... I mis-typed above...

I've dug into this and I can tftp fine to the server, but it doesn't
respond to ping - so I guess it's a setup issue on the ping server s/w

Thanks all for your patience

D.