Re: connecting a device that supports IP address, but not subnet mask or gateway to a network with multiple vlans



In article <1175195796.721656.266050@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "Ned" <nedhart@xxxxxxxxxxx> writes:
There are devices (time clocks) connected to our network that can be
configured with an IP address but DO NOT support subnet mask or
default gateway. Somehow they work, even though we are using multiple
vlans and default gateways. Our current network consists of switches
made by Marconi, I think they are ATM doing something called LANE (Lan
emulation). I am moving to Cisco switches this weekend, 4507 at the
core. Does anyone know if these devices will continue to work on a
Cisco network without an option to configure a subnet mask and default
gateway?

The key feature that you need to support this kind of device is
proxy ARP. It is enabled by default (at least on the Cisco router I just
tested on) under interface configuration mode.

If you want to be doubly sure that it is enabled, you could go into
interface configuration mode and turn it on, for instance:

interface vlan37
description An interface with brain-dead printers that need proxy ARP
ip address 192.168.37.1 255.255.255.0
ip proxy-arp


interface vlan38
description An interface with network gear made in the last ten years
ip address 192.168.38.1 255.255.255.0
no ip proxy-arp


What these devices that have no subnet mask, a badly configured subnet
mask or no default gateway will generally do is to assume that all
target IP addresses are local. So they will send an ARP request.
If there is a Cisco router on the segment and it has proxy-arp enabled,
and if it has a route in its routing table toward the requested IP
address, the router will respond to this ARP request with the MAC
address of the router. The device will then forward the IP datagram
to the Cisco router and the router will take care of delivery from
that point on.
.



Relevant Pages

  • Re: connecting a device that supports IP address, but not subnet mask or gateway to a network with m
    ... default gateway. ... Cisco network without an option to configure a subnet mask and default ... tested on) under interface configuration mode. ...
    (comp.dcom.sys.cisco)
  • Re: W2k to W98 nnetwork not working
    ... Notice that there is no default gateway for the Win2K machine. ... TCPIP configuration for this network adapter. ... If you simply get the gateway addresses for both systems and subnet mask on ...
    (microsoft.public.win2000.networking)
  • Re: Cisco 501
    ... > Default Gateway: 194.97.248.39 ... > translate any addresses. ... > Subnet Mask: 255.255.255.0 ... outside interface and an RFC 1918 address on the inside interface, ...
    (comp.dcom.sys.cisco)
  • Re: Liunx and DSL routing
    ... > traffic from other hosts to your host and from your host to other hosts. ... The "outside" refers to telneting the gateway from another WAN ... I'm trusting the Web interface too much and assuming that it can ... provide full configuration if required and will prevent bad ...
    (comp.os.linux.networking)
  • Re: RRAS with multiple NICs
    ... W2K is designed to reliably use only one default gateway at a time with a second one ... The link below explains the configuration of default gateways on multihomed ... also that "packet filtering" will be configured on one adapter which you can verify ... > This gives two routes for address 0.0.0.0, one for each interface. ...
    (microsoft.public.win2000.ras_routing)