search for: indev

On Fri, 07 Jan 2005 17:05:59 +0000 David Woodhouse <dwmw2@infradead.org> wrote: > On Sat, 2004-12-18 at 08:50 +0100, Andi Kleen wrote: > > It's not really an oops, just a warning that stack space got quiet > > tight. > > > > The problem seems to be that the br netfilter code is nesting far too > > deeply and recursing several times. Looks like a design

...e previous patch is that I got rid of the extra argument. I somehow didn't see it could be done without using the 'int *ret2' argument. A comment on the number of arguments to nf_hook_slow: I don't think the number of arguments should be decreased. For the bridge-nf code, f.e., the indev argument does not equal (*pskb)->dev (this is an answer to a question of Rusty in the old thread). A comment on the argument change of nf_hook_slow (sk_buff * to sk_buff **) and the bad influence on tail call optimization possibilities. From the discussion in the old thread it became clear that...

...enter my mpls diffserv backbone, I already mark to EF class. when video come to edge router, if its rate over limit, either dropped , or downgraded to BE taffic I plan use the ingress qdisc, but confused something parmeter For policy 1, a part of script follow #! /bin/sh -x TC=/usr/local/bin/tc INDEV=eth0 EGDEV="dev eth1" # tag video traffic from 172.16.40.3 to value 1, tag other traffic from # 172.16.40.5 to value 2 iptables -A input -i $INDEV -s 172.16.40.3 -m 1 iptables -A input -i $INDEV -s 172.16.40.5 -m 2 # install the ingress qdisc on the ingress interface $TC qdisc add dev $...

..../queue0 opening library handle unbinding existing nf_queue handler for AF_INET (if any) binding nfnetlink_queue as nf_queue handler for AF_INET binding this socket to queue '0' setting copy_packet mode pkt received queue0 hw_protocol=0x0800 hook=1 id=0 hw_src_addr=fc:4d:d4:d3:7f:73 indev=2 payload_len=40 entering callback pkt received queue0 hw_protocol=0x0800 hook=1 id=1 hw_src_addr=fc:4d:d4:d3:7f:73 indev=2 payload_len=40 entering callback pkt received queue0 hw_protocol=0x0800 hook=1 id=2 hw_src_addr=fc:4d:d4:d3:7f:73 indev=2 payload_len=40 entering callback pkt received...

After checking f_u32.c sources, there''s one extra parameter parsed - indev, that is nowhere described - not even in commandline help or in excellent Russell''s documentation. Does anyone know, what''s the purpose of it ?

Hi, I got the following lines from ''Linux Advanced Routing & Traffice Control HOWTO'' and got confused! iptables -A PREROUTING -i $INDEV -t mangle -p tcp --syn \ -j MARK --set-mark 1 tc qdisc add dev $INDEV handle ffff: ingress tc filter add dev $INDEV parent ffff: protocol ip prio 50 handle 1 fw \ police rate 1kbit burst 40 mtu 9k drop flowid :1 Does the second command mean that the filter will police the...

...perating system that shall finally come up. > > >> P.S the latest fedora ISO seems to boot fine in vbox perhaps you >> might want to look at their image. Enjoy the rest of your weekend. > You could try to re-pack it by a xorriso command like yours. > Use > > xorriso -indev ...imagefile...iso -toc > > to learn about the "Boot image" files and the "Volume id", > which you will have to use in the xorriso run. > E.g. with an old Fedora-LiveCD.iso this would be > > Drive current: -indev 'Fedora-LiveCD.iso' > ... >...

...> .hook = NF_IP_LOCAL_OUT, > }; > > ... > > /* Send it out. */ > return NF_HOOK(&nf_ip_local_out, skb, NULL, rt->u.dst.dev); > > This gets us down to 4 arguments from 6. I think we can kill > one more. > > It is never the case that both indev and outdev are both > set, so we can use some nf_hook_desc piece of state to > indicate which (in or out) the passed device pointer is. > > Oh yes, we can nicely add the thresh thing in here too > while we're at it. > > So the final nf_hook_desc might look somethin...

I posted this on the bugzilla page but I figured that on the mailing list it would get more attention. Please see http://bugzilla.syslinux.org/show_bug.cgi?id=49 for a description of my current issue. -- Thank you, Fernando Reyes GPG BDD75DD7 Mission Accomplish, Inc. http://missionaccomplish.com Email:design at missionaccomplish.com Tel: 7187100008 Cell: 3479275477

On 05/03/2016 02:31 AM, Thomas Schmitt via Syslinux wrote: > Hi, > > John Lewis wrote: >> https://help.ubuntu.com/community/LiveCDCustomizationFromScratch >> >> The show stopper for me was the mkisofs because the closest command I >> had available was xorrisofs and I think a switch was different. > If you have questions about xorrisofs, then just ask me. :))

...TEPs must drop such traffic as otherwise the host will receive multiple copies of BUM traffic. This is called "non-DF filtering" [2]. Filtering of multicast and broadcast traffic can be achieved using the following flower filter: # tc filter add dev bond0 egress pref 1 proto all flower indev vxlan0 dst_mac 01:00:00:00:00:00/01:00:00:00:00:00 action drop Unlike broadcast and multicast traffic, it is not currently possible to filter unknown unicast traffic. The classification into unknown unicast is performed by the bridge driver, but is not visible to other layers. Implementation ====...

...TEPs must drop such traffic as otherwise the host will receive multiple copies of BUM traffic. This is called "non-DF filtering" [2]. Filtering of multicast and broadcast traffic can be achieved using the following flower filter: # tc filter add dev bond0 egress pref 1 proto all flower indev vxlan0 dst_mac 01:00:00:00:00:00/01:00:00:00:00:00 action drop Unlike broadcast and multicast traffic, it is not currently possible to filter unknown unicast traffic. The classification into unknown unicast is performed by the bridge driver, but is not visible to other layers. Implementation ====...

...: Unrecognized option '-efi-boot' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE So the efi-boot option is not known. >In any case i would be interested to see what xorriso reports >about the boot equipment of your already existing ISO > > $xorriso -indev ...path.to.ISO... \ > -report_el_torito plain \ > -report_system_area plain \ > -print '' \ > -print '===== Proposed bootability options with -as mkisofs :' \ > -print '' \ > -report_el_torito as_m...

Thomas Schmitt via Syslinux said on Sat, Oct 24, 2015 at 12:56:49AM +0200: >Needed is a EFI FAT image > 32 MiB and a new xorriso (available >on demand). My test script on RHEL 7.1 creates that even if I could make it smaller as the kernel + initrd fits in less than 32 MB. So let me make that try first ! o I changed myline in the script to dd a 30 MB image file, burt the ISO with it, and

...done by SYSLINUX. You need other bootloaders or boot strategies for that. They can be combined with ISOLINUX in the same ISO image. Examples are netinst ISOs of Debian (not their LiveCDs), or ISOs of Archlinux, Gentoo, Fedora, or openSuSE. xorriso-1.4.2 will show you their equipment by xorriso -indev debian-8.4.0-amd64-netinst.iso \ -report_el_torito plain -report_system_area plain It will make proposals of boot related xorrisofs options to reproduce the shown equipment by xorriso -indev debian-8.4.0-amd64-netinst.iso \ -report_el_torito as_mkisofs > I would > ne...

...d the packet to be resummed. Without this fix, forwarding between smart/dumb interfaces causes an oops. diff -Nru a/net/bridge/br_forward.c b/net/bridge/br_forward.c --- a/net/bridge/br_forward.c Mon Sep 8 09:29:44 2003 +++ b/net/bridge/br_forward.c Mon Sep 8 09:29:44 2003 @@ -59,6 +59,7 @@ indev = skb->dev; skb->dev = to->dev; + skb->ip_summed = CHECKSUM_NONE; NF_HOOK(PF_BRIDGE, NF_BR_FORWARD, skb, indev, skb->dev, __br_forward_finish);

same patch as 2.4, just the offsets are changed. diff -Nru a/net/bridge/br_forward.c b/net/bridge/br_forward.c --- a/net/bridge/br_forward.c Mon Sep 8 09:31:19 2003 +++ b/net/bridge/br_forward.c Mon Sep 8 09:31:19 2003 @@ -69,6 +69,7 @@ indev = skb->dev; skb->dev = to->dev; + skb->ip_summed = CHECKSUM_NONE; NF_HOOK(PF_BRIDGE, NF_BR_FORWARD, skb, indev, skb->dev, br_forward_finish);

...ope of the boot images resp. the operating system that shall finally come up. > P.S the latest fedora ISO seems to boot fine in vbox perhaps you > might want to look at their image. Enjoy the rest of your weekend. You could try to re-pack it by a xorriso command like yours. Use xorriso -indev ...imagefile...iso -toc to learn about the "Boot image" files and the "Volume id", which you will have to use in the xorriso run. E.g. with an old Fedora-LiveCD.iso this would be Drive current: -indev 'Fedora-LiveCD.iso' ... Volume id : 'Fedora-LiveCD'...

Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El Torito boot img : 1 BIOS...

Hi, if I inspect an hybrid ISO with tools like fdisk and gdisk, then looks like hybrid ISO has both the MBR and GPT in order to support both the BIOS and UEFI: # gdisk -l /dev/sdb GPT fdisk (gdisk) version 0.8.10 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT