JP4621259B2 - Packet transfer control method - Google Patents

Description

The present invention relates to a packet transfer apparatus and a packet transfer control method , and more particularly, provided with a function for limiting the number of user terminals connected to an ISP (Internet Service Provider) in an access network connected to the Internet, which is a wide area network. The present invention relates to a packet transfer apparatus and a packet transfer control method .

  With the widening of access lines from user terminals to the Internet and the widespread use of home appliances equipped with network functions, multiple terminals owned by a single user are simultaneously connected to an ISP (Internet Service Provider) management server. The demand is increasing. Here, “single user” means a user as a contract unit of Internet connection service in ISP, and generally indicates an individual household connected to ISP through one access line.

  In order to connect a user terminal to the Internet, it is necessary to assign an IP (Internet Protocol) address to each user terminal. The IP address is generally assigned according to a communication protocol such as DHCP (Dynamic Host Configuration Protocol) or PPPoE (Point-to-Point Protocol over Ethernet).

  DHCP is a communication protocol for dynamically assigning an appropriate IP address to a user terminal as a terminal on the subnetwork when the user terminal is connected to a layer-2 subnetwork. PPPoE connects a point-to-point virtual layer 2 session (PPPoE session) over an Ethernet (registered trademark) line between a BAS (Broadband Access Server) belonging to each ISP and a user terminal. Is a communication protocol. In this case, an IP address is assigned to each user terminal by a PPP (Point-to-Point Protocol) protocol via a PPPoE session.

  When a single user owns a plurality of terminals, each user terminal is connected to an access network via a home router (layer 3 packet relay device) installed in the user's house, for example, There is a connection form that is connected to an access network through a hub that is a packet relay device of No. 2. In DHCP or PPPoE, a client to which an ISP management server assigns an IP address is a home router in the former connection form and an individual user terminal in the latter connection form.

  For example, when DHCP is applied, the IP address is assigned only to the home router in the former connection form, but in the latter connection form, individual IP addresses are assigned to a plurality of terminals owned by the user. When PPPoE is applied to the latter connection form, a plurality of terminals owned by the user can individually connect PPPoE sessions. In a communication environment to which PPPoE is applied, a single client (user terminal or home router) may require a plurality of PPPoE sessions. For example, a case where a different service is used for each PPPoE session, or a case where the same client is connected to a plurality of different ISPs.

  As described above, the number of IP addresses that the ISP assigns to each user, the number of PPPoE sessions connected by the same user, the number of terminals owned by the user, the presence or absence of a home router, the type of service that the user wants to use, etc. Varies depending on conditions. However, if an unlimited number of IP address assignment requests and PPPoE session connection requests are received from each user, the load on the BAS or DHCP server that is the ISP management server increases. In addition, when a specific user uses a large number of IP addresses, communication resources that can be enjoyed among users will be unfair due to the occupation of communication resources. Therefore, the number of IP addresses that can be allocated and simultaneous connections are possible for each user. You need to limit the number of sessions.

  For example, a network configuration in which a user terminal and an ISP management server (DHCP server or BAS) are connected by an individual access line (physical line or logical line such as VLAN: Virtual Local Area Network) for each user In this case, it is possible to limit the number of assigned IP addresses and the number of connected sessions for each user by managing the assigned IP addresses and the number of sessions for each access line on the management server side.

However, a network configuration in which a layer 2 switch (L2SW) is arranged between the access line to which the user terminal is connected and the management server, and traffic of a plurality of users is aggregated to a single access line by this L2SW and transferred to the management server. In this case, the management server cannot identify individual access lines for each user. In this case, it becomes impossible on the management server side to limit the number of assigned IP addresses and the number of connected sessions for each user.

In the access network configuration to which the above-described L2SW is applied, for example, the following is known as a conventional technique for limiting the number of assigned IP addresses and the number of sessions for each user.
(1) An access line in which an ISP management server (DHCP server or BAS) is linked to an L2SW, and the L2SW that has received a session connection request packet or an IP address allocation request packet from a user terminal receives the request packet from the user server A method to notify the identification information.
(2) When performing user authentication accompanying the session connection procedure, the authentication server stores the number of IP addresses assigned for each user and the number of connected sessions, and these numbers reach the upper limit. A method for rejecting new session connection requests from successful users.
As a known document describing the method (1) in a communication environment to which DHCP is applied, for example, there is Patent Document 1.

JP 2000-112852 A

  However, the above-described conventional methods (1) and (2) are both applied to a management server (DHCP server, BAS or authentication server) belonging to an ISP, and the number of IP addresses assigned to users by L2SW alone. It does not limit the number of connected sessions. Since the conventional method (1) is based on the premise of cooperation between the L2SW and the management server, for example, the L2SW is operated by a business entity independent of the ISP to which the management server belongs, and the cooperation between the L2SW and the management server is performed. If the operation (notification of access line identification information) cannot be guaranteed, it will be difficult to implement.

  Also, since a plurality of L2SWs are connected to the ISP management server, and the ISP management server accepts session connection requests and IP address assignment requests from a large number of user terminals via these L2SWs, (1) and (2) have a problem that the processing load for restricting connected user terminals is concentrated on the management server.

  An object of the present invention is to provide a packet transfer apparatus (L2SW) that can reduce the load of an ISP management server and limit the number of assigned IP addresses and the number of PPPoE sessions for each user.

In order to achieve the above object, the packet transfer apparatus of the present invention provides:
A plurality of first interface units each accommodating an access line connected to at least one user terminal, and a management server for managing communication control information necessary for communication between the user terminal and the wide area network It consists of a second interface part and a control part.
The control unit corresponds to the fixed address of the user terminal, and a connection port identifier that identifies the first interface unit to which the user terminal is connected, and is dynamically assigned to the user terminal from the management server. Comprises a management table consisting of a plurality of table entries indicating the relationship with specific header information applied to each user packet,
During execution of a predetermined communication protocol procedure that each user terminal executes with the management server prior to communication with the wide area network, the control unit is configured to send specific header information to the user terminal based on the management table. It is determined whether allocation is possible, and for a user terminal for which it is determined that allocation of specific header information is impossible, a received packet from the user terminal or a received packet from the management server addressed to the user terminal is discarded. To do.

  More specifically, in the packet transfer apparatus of the present invention, when the control unit receives the first packet in a predetermined communication protocol procedure from the user terminal, the specific header to the user terminal is based on the management table. For the user terminal for which it is determined whether or not the information can be allocated, and for which the specific header information is determined to be allocated, a new table entry corresponding to the fixed address of the user terminal is added to the management table, and the management server The specific header information notified to the user terminal is registered in the table entry.

  When the predetermined communication protocol procedure described above is, for example, PPPoE (Point-to-Point Protocol over Ethernet), the fixed address registered in the management table is the MAC address of the user terminal, and the specific header information is the PPPoE session identifier. In this case, when the number of PPPoE session identifiers having the same connection port identifier registered in the management table has reached a predetermined value, the control unit is connected to the first interface unit having the connection port identifier. It is determined that a connection request for a new PPPoE session generated from the terminal cannot be accepted, and the PPPoE discovery stage packet transmitted from the user terminal is discarded. The control unit accepts a plurality of PPPoE session connection requests from the same user terminal when the number of PPPoE session identifiers having the same connection port identifier registered in the management table is within a predetermined value, and the user terminal And relay the PPPoE packet to the management server.

  When the predetermined communication protocol procedure is, for example, DHCP (Dynamic Host Configuration Protocol), the fixed address registered in the management table is the MAC address of the user terminal, and the specific header information is the IP address of the user terminal. In this case, when the number of table entries having the same connection port identifier registered in the management table has reached a predetermined value, the control unit receives from the user terminal connected to the first interface unit having the connection port identifier. The generated IP address assignment request is determined to be unacceptable, and the DHCP packet for acquiring the IP address transmitted from the user terminal is discarded.

  According to the present invention, since the packet transfer device (L2SW) arranged between the ISP management server and a plurality of user terminals can be limited, the number of assigned IP addresses and the number of connection sessions for each access line can be limited. It is possible to reduce the load concentration on the management server.

  Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 shows a first embodiment of a network configuration including a packet transfer apparatus (layer 2 switch: L2SW) 10 of the present invention.
The network shown here includes a plurality of user networks NW (NW-A, NW-B, NW-C,...) Accommodated in the L2SW 10 and an Internet IPNW. The L2SW 10 is a BAS managed by the ISP. (Broadband Access Server) 30 is connected to the Internet IPNW. An authentication server 31 is connected to the BAS 30 in order to authenticate the user who requested the Internet connection. However, the function of the authentication server 31 may be built in the BAS 30. The user network NW includes a plurality of user terminals 20 (20-A1 to 20-A2, NW-A, NW-C, for example). 20-C1 to 20-C3) are connected to the L2SW 10 via the home hub 21 (21A, 21C) and, like the NW-B, the user terminal 20-B1 is connected via the access line 50B. Some are directly connected to the L2SW 10.
Here, for example, a home router may be arranged at the position of the user terminal 20-B1, and a plurality of user terminals (not shown) may be connected to the access line 50B via the home router. Similarly, a plurality of user terminals may be connected to any branch line of the home hub 21 via a home router. Therefore, in the following description, it is assumed that the user terminal 20 includes such a home router.

  The L2SW 10 is connected to each input / output port (input / output line interface) that accommodates the access lines 50a, 50b, 50c,... Connected to these user networks and the connection line 50u to the BAS 30. Port IDs (Pa, Pb, Pc,... Pu) are assigned.

  Each user terminal 20 executes a PPPoE session connection procedure with the BAS 30 via the L2SW 10. When the connection of the PPPoE session, the user authentication by the authentication server 31 and the IP address assignment are successful, each user terminal 20 applies the session identifier (S-ID) and the assigned IP address, and the user to the Internet through the PPPoE session. Packet transmission is possible. The BAS 30 decapsulates the user packet received from the PPPoE session, relays it to the Internet IPNW in the IP packet format, encapsulates the IP packet received from the Internet IPNW with the PPPoE header, and relays it to the PPPoE session corresponding to the destination address.

  The present embodiment is characterized in that the L2SW 10 includes a PPPoE session management table 40, and refers to this table to control the transfer of communication packets between each user terminal and the BAS 30. In the PPPoE session management table 40, as described in detail in FIG. 3, the connection port ID and the identifier of the connected session (session ID) are associated with the fixed address (MAC address) of the user terminal that requested the PPPoE session connection. ) Is stored.

  When the L2SW 10 receives the PPPoE packet from the user terminal 20 or the BAS 30, it determines not only the layer 2 header (MAC) information attached to the received packet but also the type of the PPPoE message, and then follows the PPPoE session management table 40. Perform packet transfer control. For example, when a connection request packet for a new PPPoE session is received from a user terminal, the L2SW 10 refers to the PPPoE session management table 40 and the upper limit in which the number of connected sessions between the user terminal and the BAS 30 is determined in advance. Determine whether the value has been reached.

  If the number of connected sessions has not reached the upper limit value, the L2SW 10 registers a new table entry having the MAC address of the user terminal in the PPPoE session management table 40 and transfers the received packet to the BAS 30. When the number of connected sessions has reached the upper limit value, the L2SW 10 prevents the same user terminal from connecting a session exceeding the upper limit value by discarding the received packet. In order to prevent a new session connection, the L2SW 10 does not register a new table entry in the PPPoE session management table 40, but forwards a connection request packet for the PPPoE session to the BAS 30 and receives a response packet from the BAS 30. In this case, the received packet may be discarded because the table entry corresponding to the response packet is not registered in the PPPoE session management table 40.

FIG. 2 is a block diagram showing an embodiment of the L2SW 10 of the present invention.
The L2SW 10 includes a processor (control unit) 11, a memory 12 storing various programs executed by the processor 11, a data memory 13, a plurality of pairs of input line interfaces 14-i and output line interfaces 15- i (i = 1 to n) and an internal bus 16 for connecting these elements. The memory 12 is provided with an upstream PPPoE packet processing routine 100, a downstream PPPoE packet processing routine 200, and a timeout monitoring routine 300 as programs related to the present invention. In addition, the memory 13 includes a PPPoE session management table 40 described above and a routing table that defines, for example, routing information necessary for packet transfer as other tables.

The input line interface 14-i and the output line interface 15- i are connected to any of the lines 50A to 50U shown in FIG. 1, and are assigned port IDs (Pa to Pu), respectively. A received signal from the access line 50 is processed by the input line interface 14-i, converted into a received packet, and temporarily stored in the input buffer.

  The processor 11 cyclically accesses these input line interfaces and sequentially reads received packets from the input buffer. The processor 11 processes the received packet from the input line interface that accommodates the access lines 50A to 50C connected to the user network by the upstream PPPoE packet processing routine 100, and the input that accommodates the connection line with the BAS 30. Packets received from the line interface 14-n are processed by the downstream PPPoE packet processing routine 200. The upstream PPPoE packet processing routine 100 and the downstream PPPoE packet processing routine 200 will be described in detail later with reference to FIGS.

FIG. 3 shows an example of the PPPoE session management table 40.
The PPPoE session management table 40 corresponds to the MAC address 41 of the user terminal 20 and includes a plurality of table entries 400-1, 400-2 having a connection port ID column 42, a session ID column 43, and a timeout time column 44. It consists of ...

  The connection port ID column 42 indicates the port ID of the input line interface 14 in which the access line 50 connected to the user terminal having the MAC address 41 is accommodated. The session ID column 43 indicates an identifier of a PPPoE session that has already been connected between the user terminal and the BAS 30. In this embodiment, there is a limit to the number of PPPoE sessions that can be simultaneously connected to individual user terminals, and session IDs are registered in each table entry 400 within a predetermined upper limit range. In the timeout time column 44, a timeout time for automatically disconnecting the PPPoE session is registered in association with the session ID.

  In the PPPoE session management table 40, when the L2SW 10 receives a connection request packet (PPPoE Active Discovery Initiation: PADI) of the first PPPoE session from the user terminal, the MAC address 41 and the connection port ID of the user terminal are stored in the MAC address 41. A new table entry including the input port ID of the connection request packet is added to the column 42. In the session ID column 43, a reservation code indicating that the session ID allocation waiting state from the BAS 30 is waited is set, and in the timeout time column 44, a timeout time obtained by adding a predetermined time to the current time is set. The addition of a new table entry to the PPPoE session management table 40 described above is performed by the upstream PPPoE packet processing routine 100.

When a table entry having the source MAC address of the packet already exists when the PADI packet is received, no new table entry is added to the PPPoE session management table 40, and the existing table entry is The session ID (reservation code) and timeout time value described above are added. The upstream PPPoE packet processing routine 100 refers to the PPPoE session management table 40 each time a PADI packet is received, and checks the number of session IDs corresponding to the transmission source MAC address of the received packet, thereby obtaining the number of registered session IDs. The value of the time-out time field 44 that blocks a connection request for a new PPPoE session from a user terminal that has already reached the upper limit value is the value of the upstream PPPoE packet processing routine 100 and the downstream PPPoE packet each time a communication packet is received in the PPPoE session. It is updated by the processing routine 200. The time monitoring routine 300 periodically checks the timeout time column 44 and automatically deletes the session ID that has reached the timeout time from the PPPoE session management table 40. When the session ID column 43 becomes empty due to deletion of one session ID, the table entry itself is deleted from the PPPoE session management table 40.

  Here, a different time-out time 44 value is set for each session ID, but the time-out time may be shared by a plurality of session IDs in the same table entry. In this case, when packet communication is interrupted in all PPPoE sessions connected by the same user terminal, a timeout occurs and the table entry is deleted from the PPPoE session management table 40.

  In FIG. 1, the MAC and S-ID values displayed accompanying each user terminal 20 indicate the MAC address of each user terminal and the session ID of the PPPoE session to which the user terminal is connected. Table entries 400-1 to 400-4 in FIG. 3 indicate the connection states of the PPPoE sessions by the user terminals 20-A1, 20-B1, 20-C1, and 20-C2, respectively.

FIG. 4 shows a PPPoE packet format.
The PPPoE packet includes a MAC header 81, a PPPoE header 82, and a PPPoE payload 83. The MAC header 81 includes a destination MAC address 811 and a source MAC address 812 indicating the destination and source addresses of the packet in the subnet section, a type 813 indicating the format of the packet following the MAC header, and other information. . In the case of a PPPoE packet, the value of type 813 indicates that the PPPoE header 82 is located next to the MAC header 81.

  The PPPoE header 82 includes a packet type code 821, a session identifier (S-ID) 822, and other information items. The type of packet (message) included in the PPPoE payload 83 is specified by the value of the packet type code 821. In the case of a PPPoE packet that is transmitted when the session ID value is undetermined, for example, PADI, PADO (PPPoE Active Discovery Offer), and PADR, a value indicating that the session ID has not been determined is set in S-ID 822. The In the case of PPPoE packets that are transmitted when the session ID has already been determined, for example, PADS (PPPoE Active Discovery Session-confirmation), PADT (PPPoE Active Discovery Terminate), and session stage communication packets, depending on the value of S-ID 822 A PPPoE session can be identified.

  The communication packet in the PPPoE discovery stage includes various parameter values related to the new session in the PPPoE payload 83, and the communication packet after the PPPoE session stage includes various PPP packets in the PPPoE payload 83.

FIG. 5 shows a communication sequence showing the operation of the L2SW 10 when the user terminal 20 connects a new PPPoE session with the BAS 30.
5, steps SQ1 to SQ8 are PPPoE discovery stage communication sequences related to the present invention, and steps SQ9, SQ10, and SQ11 are PPPoE session stage communication sequences performed through a PPPoE session connected in the PPPoE discovery stage. Is shown.

  When a new PPPoE session is connected, the user terminal 20 transmits a PPPoE PADI (PPPoE Active Discovery Initiation) packet to the BAS 30 (SQ1). When receiving the PADI packet, the L2SW 10 refers to the PPPoE session management table 40 and checks the number of connection sessions for each user specified by the transmission source MAC address and connection port ID of the received packet (S10). Here, if there is no table entry whose MAC address 41 matches the source MAC address in the PPPoE session management table 40, the L2SW 10 adds a new table entry with the source MAC address as the MAC address 41, The received packet is transferred to the BAS 30 (SQ2).

  If there is already a table entry whose MAC address 41 matches the source MAC address in the PPPoE session management table 40, the L2SW 10 reserves the session ID column if the number of connected sessions has not reached the upper limit. The received packet is transferred to the BAS 30, and if the number of connected sessions has reached the upper limit, the received packet is discarded. However, the received PADI packet may be transferred to the BAS 30, and when the response packet is received from the BAS 30, the response packet may be discarded because the number of connected sessions has reached the upper limit.

  Upon receiving the PADI packet, the BAS 30 returns a PPPoE PADO (PPPoE Active Discovery Offer) packet as a response packet (SQ3). When the L2SW 10 receives the PADO packet from the BAS 30, the L2SW 10 checks whether or not a table entry corresponding to the destination MAC address of the received packet is registered in the PPPoE session management table 40 (S11). If the table entry having the destination MAC address has been registered and the session ID column has been reserved, the L2SW 10 outputs the received packet to the output line interface having the port ID corresponding to the destination MAC address. As a result, the PADO packet is transferred to the requesting user terminal 20 (SQ4). When the session ID column is not reserved or when the table entry corresponding to the destination MAC address is not registered, the L2SW 10 discards the received packet.

  The user terminal 20 that has received the PADO packet then transmits a PPPoE PADR (PPPoE Active Discovery request) packet to the BAS 30 (SQ5). When the L2SW 10 receives the PADR, the L2SW 10 checks the PPPoE session management table 40 (S12). When the table entry whose MAC address 41 matches the transmission source MAC address of the received packet has been registered, and the session ID column is reserved. The received packet is transferred to the BAS 30 (SQ6). If the table entry corresponding to the transmission source MAC address is not registered or there is no reservation in the session ID column, the L2SW 10 discards the received packet.

  When receiving the PADR packet, the BAS 30 returns a PPPoE PADS (PPPoE Active Discovery Session-configuration) packet as a response packet (SQ7). When receiving the PADS packet from the BAS 30, the L2SW 10 searches the PPPoE session management table 40 for a table entry corresponding to the destination MAC address of the received packet, and registers the session ID indicated by the received PADS packet in this table entry (S13). After that, the PADS packet is transferred to the user terminal 20 (SQ8). Even when a PADS packet is received, if the table entry corresponding to the source MAC address is not registered or there is no reservation in the session ID column, the L2SW 10 discards the received packet.

After receiving the PADS packet, the user terminal 20 makes a PPP connection with the BAS 30.
By executing the PPP link establishment procedure (SQ9), user authentication procedure (SQ10), and IP address assignment procedure (SQ11) in the oE session stage, an Internet communication state is established.

  FIG. 6 shows a communication sequence of data packets in the PPPoE session stage. A data packet (PPP packet) transmitted and received by the user terminal 20 is encapsulated by a PPPoE header including a session ID 822.

  When the user terminal 20 transmits a data packet (SQ21), the L2SW 10 that has received the data packet checks the PPPoE session management table 40 (S20), and enters the session of the received packet in the table entry corresponding to the transmission source MAC address of the received packet. After confirming that the ID has been registered, the received packet is transferred to the BAS 30 (SQ22). When the table entry corresponding to the transmission source MAC address is not registered, or when the session ID indicated by the received packet is not registered in the table entry, the L2SW 10 discards the received packet. When the BAS 30 receives the data packet from the L2SW 10, it decapsulates it and transfers it to the Internet.

  On the other hand, a data packet transmitted from the Internet (for example, a Web server) to the user terminal 20 is encapsulated by the BAS 30 with a PPPoE header including the session ID 822 and transmitted to the L2SW 10 (SQ23). When the L2SW 10 receives the data packet from the BAS 10, the L2SW 10 checks the PPPoE session management table 40 (S21), and confirms that the session ID of the received packet has been registered in the table entry corresponding to the destination MAC address of the received packet. The received packet is transferred to the user terminal 20 (SQ24). If the table entry corresponding to the destination MAC address is not registered, or if the session ID indicated by the received packet is not registered in the table entry, the L2SW 10 discards the received packet.

FIG. 7 shows a communication sequence when a PPPoE session is disconnected.
The PPPoE session disconnection sequence is divided into a PPPoE session stage SQ30 and a subsequent PPPoE discovery stage.

  When disconnecting a session from the user terminal 20 side, the user terminal performs a PPPoE session stage SQ30 (IP address release procedure and PPP link disconnection procedure) with the BAS 30, and then sends a PPPoE PADT to the BAS 30. A (PPoE Active Discovery Terminate) packet is transmitted (SQ31). Upon receiving the PADT packet, the L2SW 10 searches the PPoE session management table 40 for a table entry corresponding to the transmission source MAC address of the received packet, deletes the session ID indicated by the received packet (S31), and then converts the received packet to the BAS30. (SQ32).

When the session ID field 43 of the table entry becomes empty due to the deletion of the session ID, the L2SW 10 deletes the table entry itself from the PPoE session management table 40.
Even when the PPPoE session is disconnected from the BAS 30 side, the data deletion of the PPoE session management table 40 and the transfer of the PADT packet are performed in the same procedure as in FIG.

FIG. 8 shows a flowchart of the upstream PPPoE packet processing routine 100.
When the processor 11 of the L2SW 10 reads the received packet from the input line interface 14 connected to the user network NW, the processor 11 searches the PPPoE session management table 40 for a table entry in which the MAC address 41 matches the source MAC address of the received packet. (Step 101). As a result of the search (102), if there is no table entry with a matching MAC address, the processor 11 determines the type of the received packet (103). If the received packet is not a PADI packet, the received packet is discarded ( 121) This routine is terminated.

  When the received packet is a PADI packet, the processor 11 counts the number of sessions registered in the PPPoE session management table 40 with the same connection port ID 42 as the input port ID of the received packet, and the number of sessions is a predetermined upper limit value. It is determined whether or not MAX has been reached (104). If the number of sessions has reached the upper limit value, the processor 11 discards the received packet (121) and ends this routine.

If the number of sessions is less than the upper limit value, the processor 11, the MAC address 41 includes an input port ID and the source MAC address of the received packet to the connection port ID 42, a new reserved one empty field session ID column 43 A table entry is generated and added to the PPPoE session management table 40 (105). Thereafter, the processor 11 updates the time-out time 44 corresponding to the reserved session ID field (119), and relays the received packet to the output line interface 15-n accommodating the connection line 50U with the BAS 30 (120). ), This routine is terminated.

  In step 102, when a table entry in which the MAC address 41 matches the transmission source MAC address of the received packet is searched, the processor 11 compares the connection port ID 42 indicated by the searched table entry with the input port ID of the received packet. (106). If the port IDs match, the processor 11 determines the type of the received packet (108). If the port IDs do not match, the processor 11 determines that the mobile user terminal has moved to another user network and transmitted the packet, and determines the value of the connection port ID 42 in the table entry as the input port ID of the received packet. Then, the type of the received packet is determined (108). However, if the port IDs do not match, the received packet may be discarded (121) as shown by the broken line, and this routine may be terminated.

  If the received packet is a PADI packet in step 108, the processor 11 counts the number of sessions (number of session IDs) registered in the PPPoE session management table 40 with the same connection port ID 42 as the input port ID of the received packet. It is determined whether the number of sessions has reached a predetermined upper limit value (109). If the number of sessions has reached the upper limit value, the processor 11 discards the received packet (121) and ends this routine. If the number of sessions is less than the upper limit, the processor 11 reserves one empty feed in the session ID field 43 (110), updates the corresponding timeout time (119), and relays the received packet to the BAS 30. (120) This routine is terminated.

  If the received packet is not a PADI packet, the processor 11 determines whether the received packet is a PADR packet (111). If the received packet is a PADR packet, the processor 11 checks the session ID field of the retrieved table entry (112). If the session ID field is not reserved, the processor 11 discards the received packet (121), and this routine. Exit. If the session ID field is reserved, the processor 11 updates the timeout time (119), relays the received packet to the BAS 30 (120), and ends this routine.

  If it is determined in step 111 that the received packet is not a PADR packet, the processor 11 determines whether the received packet is a PADT packet (113). If the received packet is a PADT packet, the processor 11 determines whether or not the session ID to be disconnected indicated by the received PADT packet is registered in the session ID column 43 of the table entry (114). If the session ID to be disconnected is not registered in the table entry, the processor 11 discards the received packet (121) and ends this routine.

  When the disconnection target session ID is registered in the table entry, the processor 11 deletes the disconnection target session ID from the table entry (115), and determines the number of remaining sessions (ID number) of the table entry (116). If the number of remaining sessions is not zero, the processor 11 relays the received packet to the BAS 30 (120) and ends this routine. When the number of remaining sessions in the table entry becomes zero due to deletion of the session ID, the processor 11 deletes the table entry itself from the PPPoE session management table 40 (117), and relays the received packet to the BAS 30 (120). This routine is terminated.

  If the received packet is not a PADT packet in step 113, the processor 11 determines whether or not the session ID indicated by the received packet is registered in the session ID column 43 of the table entry (118). If the session ID is not registered in the table entry, the processor 11 discards the received packet (121) and terminates this routine. If the session ID is registered in the table entry, the processor 11 The timeout time corresponding to the indicated session ID is updated (119), the received packet is relayed to the BAS 30 (120), and this routine is terminated.

FIG. 9 shows a flowchart of the downlink PPPoE packet processing routine 200.
When the processor 11 of the L2SW 10 reads the received packet from the input line interface 14-n connected to the BAS 30, the processor 11 searches the PPPoE session management table 40 for a table entry in which the MAC address 41 matches the destination MAC address of the received packet ( Step 201). As a result of the search (202), if there is no table entry corresponding to the destination MAC address, the processor 11 discards the received packet (216) and ends this routine.

  When a table entry corresponding to the destination MAC address is retrieved, the processor 11 determines the type of the received packet. If the received packet is a PADO packet (203), the processor 11 checks the session ID field 43 of the table entry (204), and if not reserved, discards the received packet (216) and terminates this routine. To do. If the session ID column 43 is reserved, the processor 11 updates the timeout time corresponding to the reservation field (214), and any output line interface 15 for connecting the received packet to the user network corresponding to the destination MAC address. (215), and this routine is finished.

  When the received packet is a PADS packet (205), the processor 11 determines whether or not the assigned session ID indicated by the PADS packet has already been registered in the table entry (206). If registered, the processor 11 updates the timeout time value corresponding to the session ID in the timeout time field 44 of the table entry (214), and the received packet is a user network corresponding to the destination MAC address. It relays to one of the output line interfaces 15 for connection (215), and this routine is finished.

  In step 206, if the assigned session ID is not registered in the table entry, the processor checks the session ID field 43 of the table entry (207), and if not reserved, discards the received packet (216), This routine ends. If the session ID column 43 is reserved, the processor 11 registers the assigned session ID indicated by the PADS packet in the session ID column 43 (208), updates the timeout time corresponding to the session ID (214), and receives it. The packet is relayed to any one of the output line interfaces 15 for connection to the user network corresponding to the destination MAC address (215), and this routine is finished.

  If the received packet is not a PADS packet in step 205, the processor 11 determines whether or not the session ID of the received packet has been registered in the session ID column 43 of the table entry (209). If the session ID of the received packet has not been registered, the processor 11 discards the received packet (216), and ends this routine. If it has been registered, the processor 11 determines whether the received packet is a PADT packet. (210).

  If the received packet is a PADT packet, the processor 11 deletes the session ID indicated by the PADS packet from the table entry (211), and checks the number of remaining sessions (number of session IDs) in the table entry (212). If the number of remaining sessions is not zero, the received packet is relayed to one of the output network interfaces 15 for connection to the user network corresponding to the destination MAC address (215), and this routine is terminated. When the number of remaining sessions becomes zero, the processor 11 deletes the table entry itself from the PPPoE session management table 40 (213), and then executes step 215.

  In step 210, when the received packet is a packet other than PADT (for example, a data packet), the processor 11 updates the timeout time corresponding to the session ID indicated by the received packet (214), and the received packet is associated with the destination MAC address. Relay to any one of the output line interfaces 15 for user network connection (215), and this routine is terminated.

  FIG. 10 shows a second embodiment of the network configuration including the packet transfer apparatus (layer 2 switch: L2SW) 10 of the present invention. Compared with FIG. 1, the network of this embodiment is characterized in that the L2SW 10 includes an IP address management table 70 and is connected to the Internet IPNW via the router 32.

Here, the router 32 has a function as a DHCP server that assigns / releases an IP address with an expiration date to the user terminal 20 in accordance with DHCP (Dynamic Host Configuration Protocol). However, a DHCP relay agent may be arranged at the position of the router 32. In this case, a DHCP server is arranged separately from the router 32, and the user terminal 20 and the DHCP server transmit and receive DHCP packets via the router 32 (DHCP relay agent).
In this embodiment, the L2SW 10 controls the packet communication between the user terminal 20 and the router 32 by using the IP address management table 70 to limit the number of IP addresses allocated to the user terminal for each access line.

FIG. 11 is a block diagram of the L2SW 10 applied to the second embodiment.
The L2SW 10 of the present embodiment is composed of the same components as the L2SW shown in FIG. 2, and the upstream packet processing routine 400, the downstream packet processing routine 500, and the program related to the present invention executed by the processor 11 are stored in the memory 12. A lease period monitoring routine 600 is prepared. The memory 13 includes an IP address management table 70.

  The upstream packet processing routine 400 is a program for controlling the transfer of IP packets (including DHCP packets) or ARP (Address Resolution Protocol) packets received from the user terminal 20, and the IP address management table 70 is stored as necessary. It is updated, and it is determined whether the received packet needs to be relayed to the router 32 according to the IP address management table 70.

  The downlink packet processing routine 500 is a program for controlling the transfer of IP packets (including DHCP packets) or ARP packets received from the router 32 to the user terminal 20, and updates the IP address management table 70 as necessary. Then, according to the IP address management table 70, it is determined whether the received packet needs to be relayed to the user terminal 20.

FIG. 12 shows an example of the IP address management table 70.
The IP address management table 70 corresponds to the MAC address 71 of the user terminal 20 and includes a plurality of table entries 700-1, 700-2 indicating a connection port ID 72, an assigned IP address 73, and a lease end time 74.・ ・ Consists of.

Similarly to the first embodiment, the connection port ID 72 indicates the port identifier of the input line interface that accommodates the access line connected to the user terminal having the MAC address 71, and the assigned IP address 73 is assigned to the router 32 by the router 32. Indicates the value of the IP address with a time limit assigned to, and the lease end time 74 indicates the expiration date of the assigned IP address.

When the L2SW 10 receives a connection request (DHCP DISCOVER) packet from the user terminal, a new table entry is added to the IP address management table 70 by the upstream packet processing routine 400. Also, in each table entry, when the L2SW 10 receives an IP address notification (DHCP ACK) packet returned by the router 32 in response to an IP address allocation request (DHCP REQUEST) from the user terminal, the downlink packet processing routine 500 Thus, the assigned IP address 73 and the lease end time 74 are registered.

The lease end time 74 can be extended by a request from the user terminal, and is periodically checked by the lease period monitoring routine 600. The table entry that has reached the lease end time is automatically deleted from the IP address management table 70 by the lease period monitoring routine 600.
In the first embodiment, a plurality of session IDs can be assigned to one MAC address (user terminal). However, in the second embodiment, one IP address is assigned to each MAC address (user terminal). .

FIG. 13 shows a format of a data packet and a DHCP packet transmitted and received by the L2SW 10 in this embodiment.
A data packet and a DHCP packet received by the L2SW 10 from the user terminal 20 or the router 32 include a MAC header 81, an IP header 84, and an IP payload 85. The IP header includes a protocol type 841, a source IP address 842, a destination IP address 843, and other information items. The protocol type 841 indicates a protocol applied to the IP payload 85. For example, when the IP payload includes a UDP packet, a specific value indicating the UDP packet is set in the protocol type 841.

  The DHCP packet is a kind of UDP (User Datagram Protocol) packet. As shown in FIG. 14, the IP payload 85 includes a UDP header 86 and a DHCP message 87. The UDP header 86 includes a transmission source port number 861, a destination port number 862, and other information items. In the case of a DHCP packet, the source port number and the destination port number are set to specific values indicating the DHCP protocol. If data of another protocol other than DHCP follows after the UDP header 86, values corresponding to the protocol are set. Is done.

  The DHCP message 87 includes an assigned IP address 871, a message type 872, a lease period 873, and other information items. The assigned IP address 871 indicates an IP address assigned to the user terminal by the router 32 or an assignment candidate IP address. When the assigned IP address is undetermined, a specific value indicating undetermined is set.

  In the message type 872, a code indicating a DHCP message type, for example, “DISCOVER”, “OFFER”, “REQUEST”, “ACK”, “NAK”, “DECLINE”, or “RELEASE” is set. In the lease period 873, a value (or desired value) representing the valid period of the IP address assigned to the user terminal by the router 32 is set. However, the lease period 873 becomes unnecessary depending on the type of the DHCP message.

  FIG. 15 shows a format of an ARP packet to be transmitted for the user terminal to know the MAC address corresponding to the IP address. The ARP packet includes an ARP message M after the MAC header 81.

FIG. 16 shows a flowchart of the upstream packet processing routine 400.
When the processor 11 of the L2SW 10 reads out the received packet from the input line interface 14 connected to the user network NW, the processor 11 searches the IP address management table 70 for a table entry in which the MAC address 71 matches the source address of the received packet ( Step 401). As a result of the search (402), if there is no table entry corresponding to the source MAC address, the processor 11 determines the type of the received packet (403). If the received packet is not a DHCP DISCOVER packet, the received packet is discarded. (414), and this routine is finished.

  If the received packet is a DHCP DISCOVER packet, the processor 11 counts the number of assigned IP addresses (number of table entries) registered in the IP address management table 70 with the same connection port ID 72 as the input port ID of the received packet. It is determined whether the number of IP addresses has reached a predetermined upper limit MAX (404). If the number of assigned IP addresses with the same connection port ID has already reached the upper limit value, the processor 11 discards the received packet (414) and ends this routine.

  If the number of assigned IP addresses has not yet reached the upper limit, the processor 11 includes the MAC address 71 and the connection port ID 72 including the source MAC address and input port ID of the received packet, and the assigned IP address 73 and the resource end time 74. A new table entry with a blank is generated and added to the IP address management table 70 (405). Thereafter, the processor 11 relays the received packet to the output line interface 15-n accommodating the connection line with the router 32 (413), and ends this routine.

If a table entry corresponding to the transmission source MAC address of the received packet is found in step 402, the processor 11 compares the connection port ID 72 of the retrieved table entry with the input port ID of the received packet (40 6 ). If the port IDs match, the processor 11 determines the type of the received packet (408). If the port IDs do not match, the processor 11 moves to another user network and transmits the packet. Understandably, the value of the connection port ID 72 in the table entry is changed to the input port ID of the received packet (407), and then the type of the received packet is determined (408). However, if the port IDs do not match, the received packet may be discarded (414) as shown by the broken line, and this routine may be terminated.

  If the received packet is a DHCP DISCOVER packet, the processor 11 understands that the DHCP DISCOVER packet has been transmitted again from the same user terminal, clears (409) the assigned IP address 73 of the table entry, and then receives the received packet. Is relayed to the output line interface 15-n accommodating the connection line with the router 32 (413), and this routine is terminated.

  When the received packet is a DHCP DECLINE packet or a DHCP RELEASE packet for releasing the IP address (410), the processor 11 deletes the table entry from the IP address management table 70 (412), and then sends the received packet to the router 32. Is relayed to the output line interface 15-n accommodating the connection line (413), and this routine is terminated.

  When the received packet does not correspond to any of the DHCP DISCOVER packet, the DHCP DECLINE packet, and the DHCP RELEASE packet, that is, when the determination result in Step 410 is No, the processor 11 connects the received packet to the router 32. Is relayed to the output line interface 15-n that accommodates (413), and this routine is terminated.

FIG. 17 shows a flowchart of the downstream packet processing routine 500.
When the processor 11 of the L2SW 10 reads the received packet from the input line interface 14-n connected to the router 32, the processor 11 searches the IP address management table 70 for a table entry in which the MAC address 71 matches the source address of the received packet. (Step 501). As a result of the search (502), if there is no table entry corresponding to the destination MAC address, the processor 11 discards the received packet (509) and ends this routine.

  If a table entry corresponding to the destination MAC address is found, the processor 11 determines the type of the received packet. When the received packet is a DHCP ACK (Acknowledge) packet (503), the processor 11 registers the value of the assigned IP address indicated by the received DHCP ACK packet in the assigned IP address 73 of the table entry (504). A value obtained by adding the lease period indicated by the DHCP ACK packet to the current time is set to the resource end time 74 of the table entry (505). Thereafter, the processor 11 relays the received packet to the output line interface 15 corresponding to the destination MAC address (508), and ends this routine.

  When the received packet is a DHCP NAK (Negative Acknowledge) packet (506), the processor 11 deletes the search table entry from the IP address management table 70 (507), and the output line interface corresponding to the received packet and the destination MAC address. 15 (508), this routine is terminated. If the received packet is a packet other than a DHCP ACK packet or a DHCP NAK packet, the processor 11 relays the received packet to the output line interface 15 corresponding to the destination MAC address (508), and ends this routine.

FIG. 18 shows a communication sequence for IP address assignment performed by the user terminal 20 with the router (DHCP server) 32 via the L2SW 10 in the second embodiment.
Prior to access to the Internet IPNW, the user terminal 20 transmits a DHCP DISCOVER packet to the router 32 (SQ41). The L2SW 10 that has received the DHCP DISCOVER packet executes the upstream packet processing routine 400, refers to the IP address management table 70, checks the number of assigned IP addresses per connection port, and sets the number of assigned IP addresses to the upper limit. If not reached, a new table entry is added to the IP address management table 70 (S40), and the received packet is relayed to the router 32 (SQ42). If the number of assigned IP addresses reaches the upper limit, the user request is ignored and the received packet is discarded.

  In response to the DHCP DISCOVER packet, the router 32 returns a DHCP OFFER packet (SQ43). The L2SW 10 that has received the DHCP OFFER packet executes the downlink packet processing routine 500 to check the IP address management table 70 and confirms that the table entry corresponding to the destination MAC address of the received packet has been registered ( S41), the received packet is relayed to the user terminal 20 (SQ44).

  The user terminal 20 that has received the DHCP OFFER packet then transmits a DHCP REQUEST packet to the router 32 (SQ45). The DHCP REQUEST packet is relayed to the router 32 by the L2SW 10 (SQ46). In response to the DHCP REQUEST packet, the router 32 returns a DHCP ACK packet specifying the assigned IP address and lease period (SQ47). When the L2SW 10 receives the DHCP ACK packet, the L2SW 10 checks the presence or absence of a table entry corresponding to the destination MAC address in the IP address management table, and registers the assigned IP address and lease period indicated by the received packet in the IP address management table (S42). After that, the received packet is relayed to the user terminal 20 (SQ48).

  When the user terminal 20 acquires the assigned IP address by the DHCP ACK packet, the user terminal 20 inquires about the MAC address corresponding to the assigned IP address according to the ARP protocol, and there is a user terminal having the same IP address other than the own terminal. After confirming that there is no communication (SQ50), communication with the Internet IPNW is started.

FIG. 19 shows a communication sequence of user IP packets (or ARP packets) in the second embodiment.
When the user terminal 20 applies the assigned IP address to the transmission source IP address and transmits the user IP packet (SQ51), the L2SW 10 that has received this executes the upstream packet processing routine 400 to execute the IP address management table 70. (S50), it is confirmed that the table entry corresponding to the source MAC address of the received packet has been registered in the IP address management table 70, and the received packet is relayed to the router 32 (SQ52).

  If the table entry corresponding to the source MAC address is not registered in the IP address management table 70, the L2SW 10 (upstream packet processing routine 400) discards the received packet. However, the upstream reception packet may be relayed to the router 32, and the downstream packet received from the router side may be discarded by the downstream packet processing routine 500.

  The IP packet transmitted from the server on the Internet IPNW to the user terminal 20 is transferred to the L2SW 10 via the router 32 (SQ53). When the L2SW 10 receives the IP packet, the L2SW 10 executes the downlink packet processing routine 500 to refer to the IP address management table 70 (S51), and the table entry corresponding to the destination MAC address of the received packet is stored in the IP address management table 70. After confirming that it has been registered, the received packet is relayed to the user terminal 20 (SQ54). When the table entry corresponding to the destination MAC address is not registered in the IP address management table 70, the L2SW 10 (downstream packet processing routine 500) discards the received packet.

FIG. 20 illustrates a communication sequence for releasing an IP address performed by the user terminal 20 with the router (DHCP server) 32 via the L2SW 10 in the second embodiment.
When invalidating or releasing the IP address assigned to the user terminal 20, the user terminal 20 sends a DHCP DECLINE packet or a DHCP RELEASE packet to the router 32 (SQ61). DHCP DECLINE packet, IP address assigned to the user terminal, the ARP procedure, when it is found to compete with the IP address assigned to another user terminal, is transmitted to disable the assignment of IP addresses The DHCP RELEASE packet is a DHCP packet that is transmitted to release an IP packet when a normally assigned IP packet becomes unnecessary.

The L2SW 10 that has received the DHCP packet executes the upstream packet processing routine 400 and deletes the IP address (table entry corresponding to the source MAC address) requested to be released by the received packet from the IP address management table 70 (S60). After that, the received packet is relayed to the router 32 (SQ62).
The table entry is deleted from the IP address management table 70, for example, when the resource end time is reached or a lease period extension request is received from the user terminal other than when the DHCP DECLINE packet or DHCP RELEASE packet is received. This is also done when it is rejected by the router 32.

  For example, when the user terminal 20 transmits a lease period extension request (DHCP REQUEST) packet (SQ71), the L2SW 10 executes the upstream packet processing routine 400 and relays the received packet to the router 32 (SQ72). Here, when the router 32 returns a DHCP NAK packet that refuses to extend the lease period (SQ73), the L2SW 10 executes the downstream packet processing routine 500, and the destination of the DHCP NAK packet is read from the IP address management table 70. The table entry corresponding to the MAC address is deleted (S70), and the received packet is relayed to the user terminal 20.

  In the above embodiments, a network configuration (FIGS. 1 and 10) in which one packet transfer device (L2SW) 10 is connected to an ISP management server (a router having a function as a BAS or DHCP server) has been described. However, in an actual application, a plurality of packet transfer apparatuses are connected to the management server, and a large number of user terminals communicate with the management server via these packet transfer apparatuses.

According to the embodiment of the present invention, each packet transfer device (L2SW) 10 can independently limit the number of user terminals connected to the management server for each access line, thereby reducing the load on the management server. It becomes possible to do.
In addition, according to the present invention, the number of user terminals connected to the Internet, which is a wide area network, can be limited without assuming cooperation with an ISP management server, so that it can be easily introduced into an existing network environment, For example, it is possible to increase resistance to an unauthorized DoS (Denial of Service) attack in which the same user transmits a large number of IP address assignment requests and session connection requests.

In the embodiment, the network configuration in which each line interface unit of the L2SW is connected to an individual user network via an access line has been described. However, the present invention is not limited to a specific access line accommodated in the line interface unit. but, for example, via another L2SW having a conversion function between ports VLA N and tag VLAN, it is also applicable to network configuration being connected to a plurality of user network. In this case, since a plurality of tag VLANs are multiplexed on the specific access line, for example, in the PPPoE session management table 40 shown in FIG. By applying a combination with VLAN-ID, it is possible to limit the number of connected user terminals (number of PPPoE sessions) for each VLAN.

  In the embodiment, the network configuration in which individual user terminals or a plurality of user terminals are connected to each access line via the HUB has been described. However, the present invention is accommodated in, for example, an OLT (Optical Line Terminal). Each optical fiber is split into a plurality of branch optical fibers by a splitter, and a packet received from each optical fiber is received in a PON (Passive Optical Network) in which a user terminal is connected to each branch optical fiber via an ONU (Optical Network Unit). The present invention can also be applied to an L2SW arranged in an OLT for multiplexing on a connection line with a host network.

The figure which shows the 1st Example of the network structure containing the packet transfer apparatus (L2SW) of this invention. The block block diagram of L2SW10 applied to 1st Example. The figure which shows the PPPoE session management table 40 with which L2SW10 of 1st Example is provided. The format figure of a PPPoE packet. The communication sequence diagram which shows operation | movement of L2SW at the time of the PPPoE session connection in 1st Example. The figure which shows the communication sequence of the data packet in the PPPoE session stage in 1st Example. The figure which shows the communication sequence at the time of the cutting | disconnection of the PPPoE session in 1st Example. 5 is a flowchart of an upstream PPPoE packet processing routine 100 executed by the L2SW 10. The flowchart of the downstream PPPoE packet processing routine 200 performed by L2SW10. The figure which shows the 2nd Example of the network structure containing the packet transfer apparatus (L2SW) of this invention. The block block diagram of L2SW10 applied to 2nd Example. The figure which shows the IP address management table 70 with which L2SW10 of 2nd Example is provided. The format figure of the packet which L2SW transmits / receives in 2nd Example. FIG. 14 is a format diagram of a DHCP packet included in the IP payload 87 of FIG. 13. The format diagram of an ARP packet. The flowchart of the upstream packet processing routine 400 performed by L2SW10 of 2nd Example. The flowchart of the downlink packet processing routine 500 performed by L2SW10 of 2nd Example. The communication sequence diagram which shows operation | movement of L2SW at the time of IP address allocation in 2nd Example. The figure which shows the communication sequence of the data packet in 2nd Example. The figure which shows the communication sequence for IP address release in 2nd Example.

Explanation of symbols

NW: user network, IPNW: Internet, 10: packet transfer device (L2SW),
11: processor, 14: input line interface, 15: output line interface,
20: User terminal, 21: HUB, 30: BAS, 31: Authentication server,
32: Router (DHCP server), 40: PPPoE session management table,
70: IP address management table, 100: Upstream PPPoE packet processing routine,
200: Downstream PPPoE packet processing routine, 300: Timeout monitoring routine,
400: upstream packet processing routine, 500: downstream packet processing routine,
600: Lease period monitoring routine.

Claims (10)

A packet transfer control method executed when a terminal is connected to a wide area network,
Sending an allocation request packet of specific header information to be applied to each packet transmitted from the terminal to the management server to the wide area network;
A communication device located on a communication path between the terminal and the management server manages the number of allocations of specific header information to the terminal, and based on the allocation number of the specific header information allocation request packet When the transfer to the management server is controlled and the allocation of new specific header information to the terminal exceeds the upper limit of the number of allocations, the received packet from the terminal or the management server addresses the terminal Of packets
The packet transfer control method, wherein the management server that receives the allocation request packet for the specific header information allocates the specific header information to the terminal. The communication protocol procedure between the terminal and the wide area network is PPPoE (Point-to-Point Protocol over Ethernet), and the specific header information is a PPPoE session identifier. Packet transfer control method. The packet transfer control method according to claim 1, wherein the specific header information is an IP address of the terminal, and the IP address is assigned to the terminal from the management server using DHCP. The packet transfer control method according to claim 1, wherein the communication apparatus manages the number of allocations of the specific header information in association with the fixed address of the terminal. The packet transfer control method according to claim 4, wherein the fixed address of the terminal is a MAC address of the terminal. When the communication device determines whether or not new specific header information can be allocated to the terminal based on the number of already allocated specific header information, and when it is determined that the new specific header information can be allocated, The allocation request packet of the specific header information is transferred to the management server, the fixed address is managed, and the new specific header information notified from the management server to the terminal is held in association with the fixed address. The packet transfer control method according to claim 4, wherein: The communication apparatus stores time information indicating an expiration date of the specific header information, automatically deletes the expired specific header information, and transmits the fixed address corresponding to the deleted specific header information as a transmission source Alternatively, the packet transfer control method according to claim 6, wherein the received packet as the destination is discarded. 8. The packet transfer control method according to claim 7, wherein when the communication device receives a packet, the communication device updates the time information corresponding to a fixed address that is a source or destination address of the received packet. . A new PPPoE session transmitted from the terminal when the communication apparatus holds the number of already allocated specific header information for each terminal and the number of already allocated PPPoE session identifiers of the terminal has reached a predetermined value 3. The packet transfer control method according to claim 2, wherein it is determined that the connection request is not accepted and the PPPoE discovery stage packet transmitted from the terminal is discarded. A new PPPoE session transmitted from the terminal when the communication apparatus holds the number of assigned specific header information for each terminal and the assigned number of the PPPoE session identifier of the terminal does not reach a predetermined value. 3. The packet transfer control method according to claim 2, wherein it is determined that the connection request is accepted and the PPPoE packet communicated between the terminal and the management server is relayed.

Images