WO2001076137A2 - Configuration et maintenance d'un pont local - Google Patents

Configuration et maintenance d'un pont local Download PDF

Info

Publication number
WO2001076137A2
WO2001076137A2 PCT/CA2001/000438 CA0100438W WO0176137A2 WO 2001076137 A2 WO2001076137 A2 WO 2001076137A2 CA 0100438 W CA0100438 W CA 0100438W WO 0176137 A2 WO0176137 A2 WO 0176137A2
Authority
WO
WIPO (PCT)
Prior art keywords
address
linking device
bridge
configuration message
configuration
Prior art date
Application number
PCT/CA2001/000438
Other languages
English (en)
Other versions
WO2001076137A3 (fr
Inventor
Tom Maher
Martin Gadbois
Martin Chabbert
Original Assignee
Eicon Technology Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Eicon Technology Corporation filed Critical Eicon Technology Corporation
Priority to AU2001244013A priority Critical patent/AU2001244013A1/en
Publication of WO2001076137A2 publication Critical patent/WO2001076137A2/fr
Publication of WO2001076137A3 publication Critical patent/WO2001076137A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
    • H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
    • H04Q11/0478—Provisions for broadband connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H04L2012/5625—Operations, administration and maintenance [OAM]
    • H04L2012/5626—Network management, e.g. Intelligent nets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming

Definitions

  • the invention relates to the field of bridge devices on networks and more particularly, to remotely configuring these bridge devices.
  • IP Internet protocol
  • the most basic form of address management is to manually assign an IP address to the new terminal by directly setting or programming the network address at the new terminal using knowledge (i.e. a list) of IP addresses already used on the network, so as to be able to select a new and available address.
  • Each terminal typically has a Media Access Control address (MAC address), which is a hardware address that uniquely identifies each node of a network.
  • MAC address Media Access Control address
  • the network manager or administrator is thus the "keeper" of the list of used addresses together with the MAC addresses of each device, and he or she is required to install any new terminal equipment on the network.
  • DIP Dual In-line Package
  • Bridges typically do the following: they listen to all traffic on the network, check source and destination MAC addresses of each packet, learn from experience to build and maintain routing tables in the bridge's RAM for the nodes on the network based on the source addresses, forward packets to all computers on all segments if the address is not in the routing table, discard the packet if the destination segment is the same as the source segment and forward the packet to the right segment if the address is in the routing table.
  • Bridges work at the data link layer, whereas routers work at the network layer. Bridges are protocol independent; routers are protocol dependent. Bridges are faster than routers because they do not have to read the protocol to glean routing information.
  • the Address Resolution Protocol is the process of mapping a
  • TCP/IP host's IP address to its hardware address on broadcast-based networks uses a local broadcast of the destination IP address to acquire the hardware address of the destination host or gateway. Once the hardware address is obtained, both the IP address and the hardware address are stored as one entry in the ARP cache.
  • the ARP cache is always checked for an IP address/hardware address mapping before initiating an ARP request broadcast.
  • An ARP request is initiated any time a host tries to communicate with another host.
  • the source host's IP address and hardware address are included in the request.
  • the ARP request is sent as a broadcast so that all local hosts can receive and process it. If a host does not find a match to its own IP address, it ignores the request.
  • the destination host which determines that the IP address in the request matches its own, sends an ARP reply directly to the source host with its hardware address. It then updates the ARP cache.
  • the ARP broadcast is for a router that can forward datagrams to the destination host's network.
  • the source host checks the local routing table for a route to a destination host or network. If no mapping is found, the source host determines the IP address of the default gateway. The source host then checks the ARP cache for the IP address/ hardware address mapping of the specified gateway.
  • An Ethernet LAN is a grouping of PCs that are directly connected together through an Ethernet link. These PCs all have different MAC addresses (assigned by manufacturing) and IP address (assigned by management, or the DHCP protocol). All PCs on a LAN must be on the same subnet (i.e. the first part of the address is the same, usually the three first bytes).
  • a PC wants to reach another PC on the same subnet, it will fill the packet with the real Source and Destination MAC addresses (it will have discovered this address with the ARP protocol), as well as Source and Destination IP addresses. If a PC wants to reach an IP address that is not on the same subnet, it will send the packet to the configured default Gateway. In this case, the IP part of the packet will be the same as if the machines were on the same subnet (i.e. source and destination IP addresses), but the Destination MAC address will be the one of the Gateway (or Router). Thus, the Router must be on the same subnet as the PCs on the LAN, because they need to be able to reach the router directly.
  • the router In the case of a bridging device, the router is on the other side of a WAN link (DSL for example).
  • the bridge's goal is to link the Router to the LAN.
  • the Bridge device For this to work, the Bridge device must be transparent (i.e. it must not modify the contents of the packets); it must only forward the packets on the WAN link. If this is achieved, the Router is virtually on the same LAN as the PCs. The PCs don't know that their Router is on the other side of a DSL link.
  • the Bridge Since the Bridge is transparent in this situation, it is not reachable from the PCs, thus, it is not possible to configure it.
  • Different methods of configuring terminal devices on a LAN have been proposed.
  • the first solution is to provide configuration/maintenance functions via another channel (e.g. a serial interface) thereby removing the need to use TCP/IP.
  • a configuration terminal would be directly connected to the device to configure using a serial interface and the appropriate changes would be made.
  • the second solution is to manually assign the device an IP address with a matching network address (e.g. via the first solution) using, for example, dip switches.
  • the third solution is to allow the service provider to dynamically assign a host address to the bridge, using for example DHCP.
  • the ISP assign an IP address to the bridge which is valid on the subnet as it would for any PC on the subnet.
  • the first and second methods make the product difficult to install because of a requirement for additional equipment and knowledge of the network on which the device is being installed.
  • the third method suffers from a serious limitation: the device uses up an IP address, which the service provider may charge for. If the PCs were on the same subnet as the Bridge, adding an IP stack in the Bridge that receives all the packets, and answers when packets are destined to it would be the easiest solution. In this case, the Bridge becomes just another station on the LAN.
  • the drawback to this solution is that the IP address of the PCs must be reconfigured manually every time a user wants to configure the Bridge.
  • an object of the present invention is to provide a configuration tool for devices on networks which does not require additional equipment.
  • Another object of the present invention is to provide a tool wherein local IP traffic destined for the bridge's configuration / maintenance IP address will not be sent to the gateway router, which is the other side of the bridge.
  • the innovation allows this traffic to be intercepted, handled, and responded to as if the datagram was delivered to the gateway and routed accordingly. Therefore routing by the gateway is faked making the device's configuration and maintenance tools accessible without being actually bridged or routed.
  • Yet another object of the present invention is to allow a PC to reach the
  • Bridge's configuration i.e. using Hyper Text Transport Protocol (HTTP), File Transport Protocol (FTP), Telnet, Syslog, etc), via the IP protocol, without modifying the transparency of the Bridge.
  • HTTP Hyper Text Transport Protocol
  • FTP File Transport Protocol
  • Telnet Telnet
  • Syslog Syslog
  • a method for remotely configuring a first linking device connecting a first network to at least a second linking device comprises the steps of: sending a configuration message from a terminal on the first network addressed to an address of the first linking device via the second linking device; detecting that the configuration message is addressed to the first linking device and intercepting the configuration message at the first linking device; processing the configuration message at the first linking device; and sending a response to the configuration message, from the first linking device to the terminal, using address information of the second linking device, whereby a response from a second linking device of the subnet is faked for a sender of the message and configuration of the first linking device having an address invalid on the first network is made possible.
  • the first linking device can be a bridge.
  • the second linking device can be one of a router or a gateway.
  • the configuration message can be an IP datagram.
  • the address information can be at least one of a MAC address and an IP address.
  • the address of the terminal and an address of the second linking device can further be stored.
  • the method can also comprise the steps of pushing the configuration message onto a stack of the first linking device; saving a terminal address and an address of the second linking device; responding to the terminal using the stack, the address of the second linking device and the terminal address.
  • a method and an apparatus for remotely configuring a bridge comprises the steps of identifying IP datagrams, communicated on a subnet, destined to an address of the bridge, wherein the address of the bridge is not valid on the subnet; and responding to the IP datagrams using information contained in the IP datagrams; wherein a response from a external router of the subnet is faked for a sender of the datagram and wherein configuration of the bridge having an address invalid on the subnet is made possible.
  • Another method is provided in which a source address and an external router address are stored from the IP datagram and wherein the source address and the external router address are used to respond to the IP datagram.
  • the source address can comprise at least one of a source IP address and a source MAC address and the external router address can comprise at least one of a router IP address and a router MAC address.
  • the address of the bridge can be an IP address.
  • a method for configuring devices on a network comprises the steps of 1) Inspecting all IP datagrams on the network before bridging them, 2) if the IP address matches the bridge's configuration/ maintenance IP address, then do not bridge the datagram and a) push the IP datagram onto the device's TCP/IP stack, b) save source IP address and Ethernet (MAC) address, c) save destination Ethernet (MAC) address, 3) Respond to the source of the datagram using the TCP/IP stack, the destination MAC address and the source MAC address, wherein routing by the gateway is faked making the device accessible without being actually bridged/routed.
  • a method is also provided in which the source IP address and MAC address are saved by updating the Address Resolution Protocol (ARP) cache.
  • ARP Address Resolution Protocol
  • the apparatus comprises a configuration message receiver for receiving a configuration message sent from a terminal on the first network and addressed to an address of the first linking device and transmitted via the second linking device; a configuration message catcher for detecting that the configuration message is addressed to the first linking device and intercepting the configuration message at the first linking device; a configuration manager for processing the configuration message at the first linking device; and a response sender for sending a response to the configuration message, from the first linking device to the terminal, using address information of the second linking device, whereby the response sender fakes a response from a second linking device of the subnet for a sender of the message and configuration of the first linking device having an address invalid on the first network is made possible.
  • the following terms are defined below.
  • datagram is intended to mean the unit of data, or packet, transmitted in a TCP/IP network. Each datagram contains source and destination addresses and data.
  • Internet address "Ethernet address”, “Hardware address” and "MAC address” are used as synonyms in the present disclosure and are intended to mean a unique number assigned to each Ethernet network adapter or device. It is a 48-bit number maintained by the IEEE (Institute of Electronics and Electrical Engineers). Hardware vendors obtain blocks of numbers that they can build into their cards.
  • bridge is intended to mean a device that connects two LAN segments together, which may be of similar or dissimilar types, such as Ethernet and Token Ring, possibly over a WAN interface.
  • FIG. 1 is a block diagram of the architecture of a system using an embodiment of the present invention
  • FIG. 2 is a flow chart of the steps involved in a method according to a preferred embodiment of the present invention
  • FIG. 3 illustrates the information which is received from the LAN, saved by the bridge and sent back to the LAN;
  • FIG. 4 is a screen shot of the configuration main menu accessible through a web browser connected to the bridge configuration manager.
  • a Local Area Network (LAN) 24 connects at least two devices, for example, at least one computer (shown here are two computers: computer 26 and computer 28) and a bridge 22.
  • the devices on the LAN can be clients (such as personal computers, terminals, etc.), servers, etc.
  • the bridge 22 connects the LAN to a router 20 through a Digital Subscriber Line (DSL) or Wide Area Network (WAN) line.
  • DSL Digital Subscriber Line
  • WAN Wide Area Network
  • the router 20 which preferably comprises a DHCP server, is connected to the Internet 29.
  • Computer 26 has a specific MAC address assigned by the manufacturer and has been assigned an IP address on the LAN.
  • the IP address is, for example, 172.30.68.2.
  • Computer 28 also has a personalized MAC address and has been assigned an IP address of 172.30.68.5. It is located on the same subnet as the computer 26 and therefore has a similar IP address (the first, second and third portions of the IP address are typically the same).
  • Bridge 22 has been assigned an IP address during manufacturing. This IP address does not necessarily correspond to an IP address valid on the LAN. In this case, the IP address assigned to the bridge was 192.168.1.1. This IP address is not valid on the example subnet.
  • the router has also been assigned an IP address valid on the subnet. The address is, for example, 172.30.68.1.
  • a typical bridge device 22 comprises the following items: a Bridge IP Module 16 used to manage IP communications in the bridge, a Bridge's Transparent Forwarding Module 18 used to forward packets, a table of known MAC addresses 19 used to compare the destination MAC addresses to a table identifying to which port the packet is destined (if known) and a Bridge's IP address 21. Configuration Managers 15 can be added but would be accessed using a serial connection.
  • the bridge 22 according to a preferred embodiment of the present invention comprises Configuration Managers 15 and a Local IP Detection Module 17 which are used to, respectively, configure the bridge and detect configuration instructions on the LAN in order to configure and maintain the bridge remotely.
  • the bridge In order to configure the bridge remotely and to communicate with it even when it is not configured correctly, the bridge is manufactured to respond to specific datagrams addressing it. ' Referring now to FIG. 2, the steps involved in a preferred embodiment of the present invention are illustrated. All IP datagrams on the LAN side are inspected by the bridge 30, even when the bridge is not configured. An example of a datagram 64 is shown in FIG. 3. The datagram 64 sent from a computer on the LAN which wishes to communicate with another device is first handled by the ARP.
  • the ARP will fetch the MAC addresses of the router and the source computer's new datagram will typically comprise a header 48, a source IP address 49 indicating from which device the datagram is being sent, a source MAC address 50, a destination IP address 51 indicating the device to which the message is being sent the router, a MAC address 54 and the content of the message 55.
  • the Local IP Detection Module 17 recognizes that the message containing its IP address as the destination IP address is in fact a configuration message for its Configuration Managers 15 even if the message is being sent to » the router 20.
  • the IP datagram is pushed up into the device's TCP/IP stack 34.
  • the source IP address and MAC addresses are saved for later use 36.
  • the router MAC address is also saved for later use 38.
  • the Local IP Detection Module prepares a datagram which borrows information from the datagram received.
  • the Source IP address 58 is, taken from the Bridge's IP address 21 , the Source MAC address 59 is taken from the router MAC address 54 of the datagram received, the Destination IP address 60 is taken from the source IP address 49 of the datagram received and the Destination MAC address 61 is taken from the source MAC address 50 of the datagram received.
  • Responses from the TCP/IP stack are sent on the local LAN side of the bridge 40.
  • the result of this process according to a preferred embodiment of the present invention is that local IP traffic destined for the bridge's configuration/maintenance IP address will not be sent to the gateway router, which is on the other side of the bridge.
  • the innovation allows this traffic to be intercepted, handled, and responded to as if the datagram was delivered to the gateway and routed accordingly. Therefore routing by the gateway is faked, making the device accessible without the packet being actually bridged/routed.
  • the bridge If the destination IP address does not match the bridge's IP address 32, the bridge (if already configured) will forward the packet to all of its ports except the port from which the message came from only if the destination MAC address is not in its table of known MAC addresses. The gateway will then send a response back to the bridge which will direct it to the right device on the LAN 44. If the address is in the table of known MAC addresses, the packet will be forwarded on the appropriate port of the bridge, and therefore, to the appropriate subnet.
  • the bridge If the bridge is not configured yet, the datagram not corresponding to the bridge's configuration / maintenance IP address will be ignored. When not configured, the bridge does not forward any packet. It is in a sleep mode from which it will be awaken when configured.
  • the destination IP address is the address of the bridge's configuration/maintenance.
  • the source IP address and MAC address of the datagrams can also be saved by updating the ARP cache of the bridge or by any other type of storage in the memory of the bridge.
  • Table 1 is a excerpt from a telnet session with a configuration manager of a bridge.
  • the telnet session illustrates possible remote configuration instructions that can be performed on the configuration manager of the bridge.
  • Table 2 is a list of potentially available instructions in a telnet session with the configuration manager of the bridge. It will be understood that this list comprises functions which are not necessary to configure a bridge and which are used to monitor the design and management of its modules. The list could also be completed by adding other functions depending on the options of the bridge.
  • DISABLE BRIDGE disables bridge DISABLE DHCP STATICMAP disable support for static address assignment DISABLE IP FORWARDING disables IP forwarding option DISABLE LOG MODULE disables logging for a module DISABLE LOG OUTPUT disables logging to a destination DISABLE TFTP SERVER disable internal tftp server DISABLE TIMEPROTOCOL disable time protocol ENABLE ADSL INTERNAL BER TESTER enables ADSL internal BER tester ENABLE ADSL TRELLIS CODING enables trellis coding
  • ADSL debug config element SET ADSL FAST MIN BITRATE DOWN sets/shows ADSL debug config element
  • ADSL FAST PLANNED BITRATE DOWN sets/shows ADSL debug config element
  • ADSL FAST PLANNED BITRATE UP sets/shows ADSL debug config element
  • ADSL debug config element SET ADSL INTERLEAVED MAX BITRATE DOWN sets/shows ADSL debug config element SET ADSL INTERLEAVED MAX BITRATE UP sets/shows ADSL debug config element SET ADSL INTERLEAVED MIN BITRATE DOWN sets/shows ADSL debug config element SET ADSL INTERLEAVED MIN BITRATE UP sets/shows ADSL debug config element
  • ADSL debug config element SET ADSL INTERLEAVED PLANNED BITRATE DOWN sets/shows ADSL debug config element SET ADSL INTERLEAVED PLANNED BITRATE UP sets/shows ADSL debug config element SET ADSL MAX ADDITIONAL NOISE MARGIN DOWN sets/shows ADSL debug config element SET ADSL MAX ADDITIONAL NOISE MARGIN UP sets/shows ADSL debug config element SET ADSL MAX AGGR PWR LEVEL DOWN sets/shows ADSL debug config element SET ADSL MAX AGGR PWR LEVEL UP sets/shows ADSL debug config element SET ADSL MAX PDS DOWN sets/shows ADSL debug config element
  • ADSL debug config element SET ADSL MIN NOISE MARGIN UP sets/shows ADSL debug config element
  • ADSL debug config element SET ADSL RAUPSHIT INTERVAL DOWN sets/shows ADSL debug config element SET ADSL RAUPSHIT INTERVAL UP sets/shows ADSL debug config element
  • ADSL debug config element SET ADSL RAUPSHIT MARGIN DOWN sets/shows ADSL debug config element SET ADSL RAUPSHIT MARGIN UP sets/shows ADSL debug config element
  • SHOW BRIDGE CONFIGURATION shows bridge configuration
  • SHOW BRIDGE PORTS shows ports the bridge is binded to
  • SHOW DATE displays the current system date and time
  • SHOW DHCP CONFIGURATION displays the DHCP server configuration
  • SHOW DHCP STATICMAP display the list of defined static DHCP addresses
  • SHOW ILMI CONFIG shows ILMI config
  • SHOW PROFILES displays the settings for all profiles.
  • SHOW TIME displays the system date and time
  • SHOW TRACE show recorded traces for specified module(s)
  • FIG. 4 illustrates a screen shot of an example of a Configuration Main Menu 50 of such a web browser interface. It comprises an Overview 52 and an Administration 54 section.
  • the Overview section 52 allows quick verification of the status 56 of the bridge (in this example, the status is "ready"). Also, the current firmware version 58 is displayed.
  • the aspects are : the ATM connections 60, the System 62, the Security 64, the ADSL Connections 66, the Maintenance 68 and the Support Information 70.
  • a "Reset” button 72 and a "Log Out” button 74 are also provided.
  • the ATM Configuration Menu 60 preferably allows to define the following parameters : the VCC number, the VPI, the VCI, whether the bridge is enabled and the encapsulation.
  • the System Parameters Menu 62 allows to define the LAN IP address, the time and date and whether spanning trees are enabled.
  • the Security Parameters Menu 64 allows to define the System name, the login password, whether inbound access is disabled and whether only IP traffic is allowed.
  • the ADSL parameters Menu 66 preferably allows to define the mode and the data path type.
  • the Firmware Maintenance Menu preferably allows to download the most updated version of the firmware, to save an image of the currently installed firmware to a file on the administrator's computer and to load in a firmware image onto the configuration managers.
  • the Configuration Maintenance Menu allows to save an image of the current configuration to a file on the administrator's computer, to restore a saved configuration and to reset the configuration to a factory default.
  • embodiments of this invention could be used to configure routers and gateways which act as links between networks. However, it is most advantageous for bridging devices because of their transparency.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un trafic local IP à destination d'une adresse IP de maintenance / configuration d'un pont qui ne sera pas envoyé vers un routeur de filtrage situé de l'autre côté du pont. Ladite invention permet d'intercepter, de traiter ledit trafic et d'y répondre, comme si le datagramme était remis à la passerelle et acheminé de façon approprié. Le routage par la passerelle est ainsi simulé, de sorte que les outils de maintenance et de configuration du dispositif sont rendus accessibles sans que le pontage/routage ait véritablement été effectué.
PCT/CA2001/000438 2000-03-31 2001-03-30 Configuration et maintenance d'un pont local WO2001076137A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001244013A AU2001244013A1 (en) 2000-03-31 2001-03-30 Local bridge configuration and maintenance

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US19337600P 2000-03-31 2000-03-31
US60/193,376 2000-03-31

Publications (2)

Publication Number Publication Date
WO2001076137A2 true WO2001076137A2 (fr) 2001-10-11
WO2001076137A3 WO2001076137A3 (fr) 2002-04-04

Family

ID=22713387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2001/000438 WO2001076137A2 (fr) 2000-03-31 2001-03-30 Configuration et maintenance d'un pont local

Country Status (2)

Country Link
AU (1) AU2001244013A1 (fr)
WO (1) WO2001076137A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007016809A1 (fr) * 2005-08-05 2007-02-15 Zte Corporation Procede de gestion de dispositif de pontage
CN1306761C (zh) * 2003-05-27 2007-03-21 华为技术有限公司 一种互联网上传送以太网报文的方法
CN100418324C (zh) * 2004-03-19 2008-09-10 富士通株式会社 利用多个令牌的通信网络中的数据传输
US20220272067A1 (en) * 2021-02-24 2022-08-25 Ricoh Company, Ltd. Communication control apparatus, communication system, communication control method, and non-transitory recording medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0791880A1 (fr) * 1996-02-20 1997-08-27 Compaq Computer Corporation Procédé et dispositif pour la configuration guidée de dispositifs de réseau et dispositifs interréseaux
US6012100A (en) * 1997-07-14 2000-01-04 Freegate Corporation System and method of configuring a remotely managed secure network interface
US6023724A (en) * 1997-09-26 2000-02-08 3Com Corporation Apparatus and methods for use therein for an ISDN LAN modem that displays fault information to local hosts through interception of host DNS request messages

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0791880A1 (fr) * 1996-02-20 1997-08-27 Compaq Computer Corporation Procédé et dispositif pour la configuration guidée de dispositifs de réseau et dispositifs interréseaux
US6012100A (en) * 1997-07-14 2000-01-04 Freegate Corporation System and method of configuring a remotely managed secure network interface
US6023724A (en) * 1997-09-26 2000-02-08 3Com Corporation Apparatus and methods for use therein for an ISDN LAN modem that displays fault information to local hosts through interception of host DNS request messages

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1306761C (zh) * 2003-05-27 2007-03-21 华为技术有限公司 一种互联网上传送以太网报文的方法
CN100418324C (zh) * 2004-03-19 2008-09-10 富士通株式会社 利用多个令牌的通信网络中的数据传输
WO2007016809A1 (fr) * 2005-08-05 2007-02-15 Zte Corporation Procede de gestion de dispositif de pontage
US20220272067A1 (en) * 2021-02-24 2022-08-25 Ricoh Company, Ltd. Communication control apparatus, communication system, communication control method, and non-transitory recording medium
US11516178B2 (en) * 2021-02-24 2022-11-29 Ricoh Company, Ltd. Controlling multi-function printer communication in network segments via a bridge device

Also Published As

Publication number Publication date
AU2001244013A1 (en) 2001-10-15
WO2001076137A3 (fr) 2002-04-04

Similar Documents

Publication Publication Date Title
US8125915B2 (en) Remote management of a bridge device
US20020112076A1 (en) Internet protocol-based computer network service
CN102025792B (zh) 路由器及其ip地址设置方法
JP2010502067A (ja) ネットワークにアクセスするためにインターフェースを特定し選択する方法および装置
JP4873960B2 (ja) アプリケーションサーバ機能を促進するための方法およびアプリケーションサーバ機能を含むアクセスノード
EP2248328B1 (fr) Mécanisme de découverte d'adresse mac d'un port de passerelle dans des réseaux ethernet
US20030018804A1 (en) Method and apparatus for deriving a standard MAC address from physical location
WO2001075626A9 (fr) Configuration de pont entre ip et web
WO2001076137A2 (fr) Configuration et maintenance d'un pont local
Cisco Quick Software Configuration
Cisco Quick Software Configuration
Cisco Quick Software Configuration
Cisco Quick Software Configuration
Cisco Quick Software Configuration
Cisco Debug Commands
Cisco Debug Commands
Cisco Managing Switches
Cisco AppleTalk Commands
Cisco AppleTalk Commands
Cisco Release Notes for the Cisco AS5300 for Cisco IOS Release 11.2(9)XA
Cisco Release Notes for the Cisco AS5300 for Cisco IOS Release 11.2(9)XA
Cisco Release Notes for the Cisco AS5300 for Cisco IOS Release 11.2(9)XA
Cisco Release Notes for the Cisco AS5300 for Cisco IOS Release 11.2(9)XA
Cisco Cisco IOS Command Modes
Cisco AppleTalk Commands

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP