hi,
i have two internal nics
at PC1
eth1 eth2
10.0.0.1 10.0.0.2
| |
switch
|
pc2
eth0
10.0.0.3
and when I ping from pc2 -> PC1:eth2,
using tcpdump i see that PC1
send reply to (arp who has 10.0.0.2),
10.0.0.2 is at .....eth1.
why PC1 send back not proper HW address?
how I can force PC1 to say that 10.0.0.2
is at eth2?
thanks in advance!
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Roman, # echo 1 > /proc/sys/net/ipv4/conf/all/hidden # echo 1 > /proc/sys/net/ipv4/conf/eth1/hidden # echo 1 > /proc/sys/net/ipv4/conf/eth2/hidden If you don''t have support for hidden in your kernel, visit Julian''s page: http://www.linux-vs.org/~julian/ http://www.linux-vs.org/~julian/#hidden This will prevent ethernet interfaces from responding for ARP for IPs active on other devices. Good luck, -Martin : and when I ping from pc2 -> PC1:eth2, : using tcpdump i see that PC1 : send reply to (arp who has 10.0.0.2), : 10.0.0.2 is at .....eth1. : why PC1 send back not proper HW address? : how I can force PC1 to say that 10.0.0.2 : is at eth2? : : : : thanks in advance! : : : : : : _______________________________________________ : LARTC mailing list / LARTC@mailman.ds9a.nl : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ : -- Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
martin, I apply this patch and set hidden =1,arp_filter =1 too, at all nic''s but nothing changed. eth1 always reply that ip 10.0.0.2 is at eth1... It seems be so,that I can''t forward packets over two different nic''s which are in same network. bye>Roman, > ># echo 1 > /proc/sys/net/ipv4/conf/all/hidden ># echo 1 > /proc/sys/net/ipv4/conf/eth1/hidden ># echo 1 > /proc/sys/net/ipv4/conf/eth2/hidden > >If you don''t have support for hidden in your kernel, visit Julian''s page: > > http://www.linux-vs.org/~julian/ > http://www.linux-vs.org/~julian/#hidden > >This will prevent ethernet interfaces from responding for ARP for IPs >active on other devices. > >Good luck, > >-Martin > > : and when I ping from pc2 -> PC1:eth2, > : using tcpdump i see that PC1 > : send reply to (arp who has 10.0.0.2), > : 10.0.0.2 is at .....eth1. > : why PC1 send back not proper HW address? > : how I can force PC1 to say that 10.0.0.2 > : is at eth2? > : > : > : > : thanks in advance! > : > : > : > : > : > : _______________________________________________ > : LARTC mailing list / LARTC@mailman.ds9a.nl > : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > : > > >-- Roman Virdzek - System & Network Engineering ____________________________________________ JARON INTERNET GmbH Hanauer Landstrasse 196a D-60314 Frankfurt am Main Fon:+49-69-405866-36 ; Fax:+49-69-405866-29 Internet: www.jaron.de ; www.popularix.de ____________________________________________ ( Saving Private Ryan... Private Ryan exists. Overwrite? (Y/N) ) _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Roman, : I apply this patch and set hidden =1,arp_filter =1 too, : at all nic''s but nothing changed. eth1 always reply that : ip 10.0.0.2 is at eth1... : It seems be so,that I can''t forward packets over two different : nic''s which are in same network. Tarek was correct when he mentioned that you''ll need to use policy routing in addition if both of the IPs you are using fall within the same network. # ip rule add from 10.0.0.2 lookup 2 # ip rule add from 10.0.0.1 lookup 1 # ip route add 10.0.0.0/24 dev eth1 src 10.0.0.1 # ip route add 10.0.0.0/24 dev eth2 src 10.0.0.2 Turn on the ARP hiding functionality: # echo 1 > /proc/sys/net/ipv4/conf/all/hidden You''ll need to do this *after* you have brought up the interfaces and set the hidden flags explicitly. # echo 1 > /proc/sys/net/ipv4/conf/eth1/hidden # echo 1 > /proc/sys/net/ipv4/conf/eth2/hidden Good luck, -Martin : >Roman, : > : > : >If you don''t have support for hidden in your kernel, visit Julian''s page: : > : > http://www.linux-vs.org/~julian/ : > http://www.linux-vs.org/~julian/#hidden : > : >This will prevent ethernet interfaces from responding for ARP for IPs : >active on other devices. : > : >Good luck, : > : >-Martin : > : > : and when I ping from pc2 -> PC1:eth2, : > : using tcpdump i see that PC1 : > : send reply to (arp who has 10.0.0.2), : > : 10.0.0.2 is at .....eth1. : > : why PC1 send back not proper HW address? : > : how I can force PC1 to say that 10.0.0.2 : > : is at eth2? : > : : > : : > : : > : thanks in advance! : > : : > : : > : : > : : > : : > : _______________________________________________ : > : LARTC mailing list / LARTC@mailman.ds9a.nl : > : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ : > : : > : > : > : : : -- Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Sorry! Correction below: -Martin Tarek was correct when he mentioned that you''ll need to use policy routing in addition if both of the IPs you are using fall within the same network. # ip rule add from 10.0.0.2 lookup 2 # ip rule add from 10.0.0.1 lookup 1 # ip route add 10.0.0.0/24 dev eth1 src 10.0.0.1 table 1 # ip route add 10.0.0.0/24 dev eth2 src 10.0.0.2 table 2 Turn on the ARP hiding functionality: # echo 1 > /proc/sys/net/ipv4/conf/all/hidden You''ll need to do this *after* you have brought up the interfaces and set the hidden flags explicitly. # echo 1 > /proc/sys/net/ipv4/conf/eth1/hidden # echo 1 > /proc/sys/net/ipv4/conf/eth2/hidden -- Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
hi, ok thanks, it seem to be working now. why it will not working with: ip rule add iif eth2 lookup 2 ip rule add iif eth1 lookup 1 ? and another one question. i have turned on log martians, and kernel still write to me: martian source from ...........when I ping eth1 | eth2 ...but back get proper arp reply. thanks for reply bye>Sorry! Correction below: > >-Martin > > Tarek was correct when he mentioned that you''ll need to use policy routing > in addition if both of the IPs you are using fall within the same network. > > # ip rule add from 10.0.0.2 lookup 2 > # ip rule add from 10.0.0.1 lookup 1 > # ip route add 10.0.0.0/24 dev eth1 src 10.0.0.1 table 1 > # ip route add 10.0.0.0/24 dev eth2 src 10.0.0.2 table 2 > > Turn on the ARP hiding functionality: > > # echo 1 > /proc/sys/net/ipv4/conf/all/hidden > > You''ll need to do this *after* you have brought up the interfaces and > set the hidden flags explicitly. > > # echo 1 > /proc/sys/net/ipv4/conf/eth1/hidden > # echo 1 > /proc/sys/net/ipv4/conf/eth2/hidden > > >-- Roman Virdzek - System & Network Engineering ____________________________________________ JARON INTERNET GmbH Hanauer Landstrasse 196a D-60314 Frankfurt am Main Fon:+49-69-405866-36 ; Fax:+49-69-405866-29 Internet: www.jaron.de ; www.popularix.de ____________________________________________ ( I drive way too fast to worry about cholesterol. ) _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hi i have Redhat Linux 8.0 when iam trying to configure htb iam getting following error any clue [root@pdn root]# tc qdisc add dev eth0 root handle 1: htb default 12 Unknown qdisc "htb", hence option "default" is unparsable hare _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Wed, 2002-11-27 at 17:21, hare ram wrote:> Hi > > i have Redhat Linux 8.0 > when iam trying to configure htb > iam getting following error > any clue > > [root@pdn root]# tc qdisc add dev eth0 root handle 1: htb default 12 > Unknown qdisc "htb", hence option "default" is unparsable >I''m running 8.0 with kernel 2.4.18-18 htb is ok in the kernel, but the tc command isn''t the correct version. Have you got the kernel source installed? /usr/src/linux-2.4.18-18.8.0/net/sched/sch_htb.c has the following version stamp. * $Id: sch_htb.c,v 1.13 2002/05/25 09:04:50 devik Exp $ Grab an updated version of the "tc" binary from http://luxik.cdi.cz/~devik/qos/htb/v3/htb3.6-020525.tgz I was expecting a recompile but it wasn''t necessary. -- NAME : Adam Allen. EMAIL : adam@dynamicinteraction.co.uk COMMENT : ~~~~ insert your favourite signature comment here ~~~~ PGP : http://search.keyserver.net:11371/pks/lookup?op=vindex&search=adam%40dynamicinteraction.co.uk
On Wednesday 27 November 2002 18:21, hare ram wrote:> Hi > > i have Redhat Linux 8.0 > when iam trying to configure htb > iam getting following error > any clue > > [root@pdn root]# tc qdisc add dev eth0 root handle 1: htb default 12 > Unknown qdisc "htb", hence option "default" is unparsableRedhat has htb support in the kernel, but not in the tc command. So download the one from the htb webpage, or download the iproute2 code, patch it and compile it. Stef -- stef.coene@docum.org "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/