Re: Question about Netgraph (I'm in a mess :)

From: Gerasimos Dimitriadis (gedimitr_at_auth.gr)
Date: 11/26/03

  • Next message: Juan Rodriguez Hervella: "Re: Question about Netgraph (I'm in a mess :)"
    To: "Juan Rodriguez Hervella" <jrh@it.uc3m.es>
    Date: Wed, 26 Nov 2003 14:24:09 +0200
    
    

    Hi,

    I believe that the best approach would be to divert all the traffic from/to
    the interface you are interested. Connect
    the 'upper' and 'lower' hooks of the corresponding ng_ether node to a node
    that implements the functionality you want. By checking the 'type' value in
    the ethernet header you can find when you are dealing with IP packets, while
    letting all the others simply pass through.

    Gerasimos

    ----- Original Message -----
    From: "Juan Rodriguez Hervella" <jrh@it.uc3m.es>
    To: <freebsd-net@freebsd.org>
    Sent: Wednesday, November 26, 2003 1:53 PM
    Subject: Question about Netgraph (I'm in a mess :)

    > Hello,
    >
    > I'd like to make some modifications to the IPv6 hearder of some packets
    > before sending them out the interface. I'm thinking where's the best
    > way of doing this. So, I've found out the Netgraph tool (I didn't know it
    > before :) but now I'm wondering how to use it properly.
    >
    > As far as I understand, I could have a "ng_iface" node which would
    > have a "ipv6" hook to my new node, which would change the IPv6
    > packet.... I would grab the packets installing a new route towards the
    > "ng_iface" node, right ? Then, if I want to insert the modified packet
    > to send it out the interface, I should connect my new node to the
    > "ng_ether" node ? or again sending out the packet through the same
    > "ng_iface" node ?
    >
    > I'm a bit mix up with all this stuff, any help will be very appreciated.
    >
    > --
    > ******
    > JFRH
    > ******
    >
    > With every passing hour our solar system comes forty-three thousand
    > miles closer to globular cluster M13 in the constellation Hercules, and
    > still there are some misfits who continue to insist that there is no
    > such thing as progress.
    > -- Ransom K. Ferm
    >
    > _______________________________________________
    > freebsd-net@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-net
    > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"


  • Next message: Juan Rodriguez Hervella: "Re: Question about Netgraph (I'm in a mess :)"

    Relevant Pages

    • Terminal Server Setup
      ... description GRE Tunnel Source Interface ... input packets with dribble condition detected ... output buffer failures, ... Serial1/0 is up, line protocol is up ...
      (comp.dcom.sys.cisco)
    • Re: Tuning ADSL lines on Ciscos roputer - LONG -
      ... Last clearing of "show interface" counters never ... minute input rate 0 bits/sec, ... input packets with dribble condition detected ... output buffer failures, ...
      (comp.dcom.sys.cisco)
    • Re: Terminal Server Setup
      ... description GRE Tunnel Source Interface ... input packets with dribble condition detected ... output buffer failures, ...
      (comp.dcom.sys.cisco)
    • Re: Excessive interface resets on Cisco 1841 and FIOS line
      ... huge amount of interface resets on the WAN interface, ... access-list 4 remark HTTP Access-class list ... input packets with dribble condition detected ... output buffer failures, ...
      (comp.dcom.sys.cisco)
    • Interface counters not working
      ... get why no traffic is registering on the interface counters. ... minute input rate 0 bits/sec, ... input packets with dribble condition detected ... output buffer failures, ...
      (comp.dcom.sys.cisco)