[comp.protocols.tcp-ip] Kenmore MicroWave Oven For Sale

david@ms.uky.edu (David Herron -- One of the vertebrae) (07/19/89)

What sort of TCP/IP does it have??
-- 
<- David Herron; an MMDF guy                              <david@ms.uky.edu>
<- ska: David le casse\*'      {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<-
<- WARNING: Hunting season is now open in West Virginia!

welch@giza.cis.ohio-state.edu (Arun Welch) (07/19/89)

In article <12201@s.ms.uky.edu>, david@ms.uky.edu (David Herron -- One of the vertebrae) writes:
> What sort of TCP/IP does it have??

I dunno, but my guess is it's an NTP chimer, from the clock...:-)

...arun


----------------------------------------------------------------------------
Arun Welch
Lisp Systems Programmer, Lab for AI Research, Ohio State University
welch@tut.cis.ohio-state.edu

nelson@sun.soe.clarkson.edu (Russ Nelson) (07/19/89)

In article <12201@s.ms.uky.edu> david@ms.uky.edu (David Herron -- One of the vertebrae) writes:

   What sort of TCP/IP does it have??

I think that they took the old CP/M version of Karn's code and ported it
to an 8051.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])|(70441.205@compuserve.com)

wisner@mica.Berkeley.EDU (Bill Wisner) (07/19/89)

But what good is it if it doesn't speak TCP/IP?

Bill Wisner		wisner@mica.berkeley.edu	     ucbvax!mica!wisner
I'm not poricthys notatus either.

bob@giza.cis.ohio-state.edu (Bob Sutterfield) (07/19/89)

One step closer to ToasterNet...

roy@phri.UUCP (Roy Smith) (07/19/89)

>    What sort of TCP/IP does it have??
> I think that they took the old CP/M version of Karn's code and ported it
> to an 8051.

Does it have the slow-start (defrost?) algorithm?
-- 
Roy Smith, Public Health Research Institute
455 First Avenue, New York, NY 10016
{att,philabs,cmcl2,rutgers,hombre}!phri!roy -or- roy@alanine.phri.nyu.edu
"The connector is the network"

kwe@bu-cs.BU.EDU (kwe@bu-it.bu.edu (Kent W. England)) (07/20/89)

In article <42958@bbn.COM> djw@BBN.COM (David Waitzman) writes:
>The microwave obviously speaks TCP:
>Here is the "traceroute" output to kenmore.kitchen.net from here:
>
>traceroute to kenmore.kitchen.net (224.1.54.1), 30 hops max, 40 bite packets
> 1  circe.bbn.com (128.89.0.247)  0 ms  0 ms  10 ms
> 2  128.89.0.1 (128.89.0.1)  60 ms  70 ms  70 ms
> 3  * * *
> 4  pc.livingroom.house.ny.us (225.9.5.4)  90 ms  90 ms  90 ms
> 5  fridge.kitchen.net (224.4.5.3) 140 ms  150 ms  140 ms
> 6  pc.livingroom.house.ny.us (225.9.5.4)  160 ms  170 ms  160 ms
> 7  fridge.kitchen.net (224.4.5.3) 300 ms  310 ms  300 ms
> 8  pc.livingroom.house.ny.us (225.9.5.4)  320 ms  330 ms  320 ms
> 9  fridge.kitchen.net (224.4.5.3)  340 ms  350 ms  340 ms
>10  kenmore.kitchen.net (224.1.54.1)  360 ms  370 ms  360 ms
>
>Note the temporary routing loop from the pc to the fridge.  Anyone have
>any ideas on why?
>
>-david


	I ran an snmpsrc on kitchen.net and found this:

bu-netcop{kwe}44> snmpsrc livingroom-gw kitchen-net
Copyright (C) 1988 NYSERNet INC

Looking for source of routing of kitchen-net....

gateway=livingroom-gw   next-hop=kitchen-gw     metric=3      remote rip
gateway=kitchen-gw      next-hop=bedroom-gw     metric=205871 remote criscoIgrp
gateway=bedroom-gw      next-hop=livingroom-gw  metric=277889 remote boudoir
receive timed out.  Retrying....
bu-netcop{kwe}45>

	Obviously this kind of appliance networking has some bugs to
be ironed out.  I understand that some appliances do not yet implement
split horizon, in particular some refrigerators.  Perhaps if they
tried a link state algorithm...  Fortunately they decided to do SNMP
(after fierce lobbying from Marty Schoffstall) and didn't wait for
CMIP or else we wouldn't have been able to figure things out this far.

	--Kent England, Boston University

medin@NSIPO.NASA.GOV ("Milo S. Medin", NASA ARC NSI Project Office) (07/20/89)

Of course, this is an illegal activity, as net 224 is reserved for 
Multicast addresses.  In particular 224.0.0.5 and 224.0.0.6 are 
assigned to the OSPF IGP routing protocol.  I believe also that it
is illegal to forward a packet from or to net 224 as this is part
of the range of addresses are that are explicitly single-hop!

					Thanks,
					   Milo

zweig@p.cs.uiuc.edu (07/23/89)

> Written  Jul 19, 1989 by medin@NSIPO.NASA.GOV in comp.protocols.tcp-ip
> 
> Of course, this is an illegal activity, as net 224 is reserved for 
> Multicast addresses.  In particular 224.0.0.5 and 224.0.0.6 are 
> assigned to the OSPF IGP routing protocol.  I believe also that it
> is illegal to forward a packet from or to net 224 as this is part
> of the range of addresses are that are explicitly single-hop!
         ^^^^^
	 Speaking of kitchen-appliances....
> 
> 					Thanks,
> 					   Milo

-Johnny Z ;-)

djw@bbn.com (David Waitzman) (08/15/89)

The microwave obviously speaks TCP:
Here is the "traceroute" output to kenmore.kitchen.net from here:

traceroute to kenmore.kitchen.net (224.1.54.1), 30 hops max, 40 bite packets
 1  circe.bbn.com (128.89.0.247)  0 ms  0 ms  10 ms
 2  128.89.0.1 (128.89.0.1)  60 ms  70 ms  70 ms
 3  * * *
 4  pc.livingroom.house.ny.us (225.9.5.4)  90 ms  90 ms  90 ms
 5  fridge.kitchen.net (224.4.5.3) 140 ms  150 ms  140 ms
 6  pc.livingroom.house.ny.us (225.9.5.4)  160 ms  170 ms  160 ms
 7  fridge.kitchen.net (224.4.5.3) 300 ms  310 ms  300 ms
 8  pc.livingroom.house.ny.us (225.9.5.4)  320 ms  330 ms  320 ms
 9  fridge.kitchen.net (224.4.5.3)  340 ms  350 ms  340 ms
10  kenmore.kitchen.net (224.1.54.1)  360 ms  370 ms  360 ms

Note the temporary routing loop from the pc to the fridge.  Anyone have
any ideas on why?

-david