A method at a network node of classifying in-vehicle data traffic, the method comprising: Defining at the network node a first network namespace and a second network namespace, the first network namespace comprising an ingress network interface configured to receive incoming request data packets and deliver response data packets, the second network namespace comprising an egress network interface configured to receive incoming response data packets and deliver request data packets, wherein channels are provided between the first network namespace and the second network namespace such that traffic between the ingress network interface and the egress network interface is routed through the channels; Receiving, from a vehicle, a plurality of incoming request data packets at the network node, the data packets originating from an application executing at the vehicle; For each data packet of the plurality of incoming request data packets: Extracting from a header of the data packet a source IP address for the data packet, the source IP address being associated with the vehicle; Extracting from the header of the data packet, a destination IP address for the data packet, the destination IP address being associated with a service requested by the application; Determining a volume of data for the incoming data packet by inspecting the header of the data packet; Checking the destination IP address against a routing table, and; On determining that the destination IP address is defined within the routing table, routing the incoming data packet through a channel defined for that destination IP address, or On determining that the destination IP address is not defined within the routing table, routing the incoming data packet through a default channel provided for all not-defined destination IP addresses; Updating a channel volume indicator based on the determined volume of data for the incoming request data packet; Transmitting the plurality of incoming request data packets from the network node onward to the destination IP addresses associated with each of the request data packets. Defining at the network node a first network namespace and a second network namespace, the first network namespace comprising an ingress network interface configured to receive incoming request data packets and deliver response data packets, the second network namespace comprising an egress network interface configured to receive incoming response data packets and deliver request data packets, wherein channels are provided between the first network namespace and the second network namespace such that traffic between the ingress network interface and the egress network interface is routed through the channels; Receiving, from a vehicle, a plurality of incoming request data packets at the network node, the data packets originating from an application executing at the vehicle; For each data packet of the plurality of incoming request data packets: Extracting from a header of the data packet a source IP address for the data packet, the source IP address being associated with the vehicle; Extracting from the header of the data packet, a destination IP address for the data packet, the destination IP address being associated with a service requested by the application; Determining a volume of data for the incoming data packet by inspecting the header of the data packet; Checking the destination IP address against a routing table, and; On determining that the destination IP address is defined within the routing table, routing the incoming data packet through a channel defined for that destination IP address, or On determining that the destination IP address is not defined within the routing table, routing the incoming data packet through a default channel provided for all not-defined destination IP addresses; Updating a channel volume indicator based on the determined volume of data for the incoming request data packet; Extracting from a header of the data packet a source IP address for the data packet, the source IP address being associated with the vehicle; Extracting from the header of the data packet, a destination IP address for the data packet, the destination IP address being associated with a service requested by the application; Determining a volume of data for the incoming data packet by inspecting the header of the data packet; Checking the destination IP address against a routing table, and; On determining that the destination IP address is defined within the routing table, routing the incoming data packet through a channel defined for that destination IP address, or On determining that the destination IP address is not defined within the routing table, routing the incoming data packet through a default channel provided for all not-defined destination IP addresses; On determining that the destination IP address is defined within the routing table, routing the incoming data packet through a channel defined for that destination IP address, or On determining that the destination IP address is not defined within the routing table, routing the incoming data packet through a default channel provided for all not-defined destination IP addresses; Updating a channel volume indicator based on the determined volume of data for the incoming request data packet; Transmitting the plurality of incoming request data packets from the network node onward to the destination IP addresses associated with each of the request data packets.