From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB shaping different subnets...
Date: Tue, 05 Aug 2003 14:15:40 +0000 [thread overview]
Message-ID: <marc-lartc-106009406609139@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106009132605524@msgid-missing>
Rokas,
: ADSL modem-----ppp0[LINUX box]eth0 (192.168.1.254)---HUB---LAN
Got it.
: I use HTB to shape download and upload traffic. I use HTB shape on eth0
: interface for download traffic, and shape on ppp0 interface for upload
: traffic.
Perfect.
: I want to connect some other computers to the LAN, but I want to give
: them IP adresses from 192.168.2.1-254 range that these new PC's
: couldn't "see" old PC's in the LAN.
If you are indeed using a hub, then each of the machines on the internal
network will be able to see the others, and all of the traffic, but only
under two potential conditions:
- a user puts the NIC into promiscuous mode
- a user adds a route to the other IP network via the NIC
But, these are security considerations, and probably not a problem for
you.
: But I want these new PC's to be able to get to the Internet through my
: LINUX box. I think I have to use IP aliasing on my LINUX box's eth0
: interface to do this.
Yes, you can do this. There'd be no problem here.
: Am I right, or is it any other mean to do it ? (I don't want to install
: a new ethernet interface for the new subnet to my LINUX box).
This will bring up a new address on eth0, cause the kernel to respond for
ARP, and add a route to the 192.168.2.0/24 network:
ip address add 192.168.2.254/24 dev eth0
I'd recommend, additionally that you block all traffic to/from each of the
192.168.x.0/24 networks:
iptables -A FORWARD -s 192.168.2.0/24 -d 192.168.1.0/24 -j DROP
iptables -A FORWARD -s 192.168.1.0/24 -d 192.168.2.0/24 -j DROP
Note, that still doesn't prevent users on each segment from potentially
seeing each other (see above)--it just means that the IP networks will not
be able to forward packets through your linux box to each other.
: But if I used IP aliasing on eth0 interface, would I be able to shape
: download traffic, because I have to shape eth0 interface for download
: traffic ??? Please give me some comments about this question.
You may need to alter your traffic control configuration to include
references to the new IP range, but there is no problem with this
solution.
-Martin
--
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/
next prev parent reply other threads:[~2003-08-05 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 13:48 [LARTC] HTB shaping different subnets Rokas Zakarevicius
2003-08-05 14:04 ` Albert Manyà
2003-08-05 14:15 ` Martin A. Brown [this message]
2003-08-06 5:30 ` Rokas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-106009406609139@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.