On Jun 22, 2004, at 9:02 AM, Matt Juszczak wrote:
What are some of the other approaches (if you dont mind). I can't
really do a NAT, I'd really like to stay with a bridge and not do any
routing.
Normally, something like squid listens on a specific port and only
proxies requests which are explic
> What are some of the other approaches (if you dont mind). I can't
> really do a NAT, I'd really like to stay with a bridge and not do any
> routing.
I'm using a bridging setup (specifically to grab all web traffic and
divert it all to a proxy/policy manager), I had to perform a kernel
patch in
What are some of the other approaches (if you dont mind). I can't
really do a NAT, I'd really like to stay with a bridge and not do any
routing.
Charles Swiger wrote:
On Jun 21, 2004, at 5:10 PM, Matt Juszczak wrote:
[ ... ]
So basically, I either have to use some other form of redirecting web
On Jun 21, 2004, at 5:10 PM, Matt Juszczak wrote:
[ ... ]
So basically, I either have to use some other form of redirecting web
packets (a bogus DNS server maybe), or switch to a NAT instead of a
bridge. Correct?
Yes, more or less. There are other approaches which could be taken
which are more
On Jun 21, 2004, at 4:48 PM, [EMAIL PROTECTED] wrote:
Is it possible to redirect packets that are being passed through a
bridge
based on their protocol/port, so that if a HTTP packet (port 80) goes
through the bridge, no matter what its destination is, it will be
redirected to IP address 4.3.2.1.
Matt Juszczak wrote:
Is there a way to do IP redirection without using layer 3? (IPNAT or
routing)? I have a bridge setup and want to redirect any port 80
traffic outgoing through the bridge to a specific server but it
seems I can only do this with ipfw's forward/fwd or ipnat's rdr command
You can do it with a cisco like this. You can pickup a used 250x series
cheap. Just make sure you are using IOS 12 >
ip nat pool trans 10.10.10.0 10.10.10.254 netmask 255.255.255.0
ip nat inside source list 1 interface Ethernet0 overload
ip nat inside source static tcp 10.10.10.13 110 interface Et
Renato Marques wrote:
Hmmm.. I really can't think about some solution... All of them involve a
router before, in or after the bridge.
How about proxying before the bridge?
I think that my be an option. I'll have to think on it, I appreciate
your help though. Thanks!
Hmmm.. I really can't think about some solution... All of them involve a
router before, in or after the bridge.
How about proxying before the bridge?
> So in summary, do I basically either have to do routing or a NAT, or
> find another alternative? There's no way to just bridge the tra
I know its layer 3 ... my point is that FreeBSD's bridge supports IPFW,
and IPFW allows for some IP-related things ...filtering by source IP,
destination IP, etc. etc. But in the man page for ipfw, it says that
the "forward" command in ipfw is not supported on layer 2 (bridging,
etc.). So I w
Matt Juszczak <[EMAIL PROTECTED]> writes:
> Is there a way to do IP redirection without using layer 3?
IP *is* layer 3.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMA
So in summary, do I basically either have to do routing or a NAT, or
find another alternative? There's no way to just bridge the traffic and
do what i want?
Thanks! :)
-Matt
Renato Marques wrote:
Well, in the TCP/IP Model, IP is layer 2 and TCP/UDP layer3.
I dont think a bridge could do s
Well, in the TCP/IP Model, IP is layer 2 and TCP/UDP layer3.
> I dont think a bridge could do some like that. A bridge see only IP
> packets, where are no information about ports, ports are used in TCP and
> UDP.
> Actualy, I think Layer 3 is where the IP protocol besides. NAT is done
> o
I dont think a bridge could do some like that. A bridge see only IP
packets, where are no information about ports, ports are used in TCP and
UDP.
Actualy, I think Layer 3 is where the IP protocol besides. NAT is done
on layer 4... but i could be wrong...
> Hello all,
>
> Is there a way to do
Hi,
You will need some type of layer 3 device, router or firewall, to do what
you want. A bridge works at layer 1 & 2 (physical and transport layers)
and basically just allows one type of network (cable or dsl) to talk to
antother (ethernet).
On Fri, Jun 18, 2004 at 07:05:14PM -0400, Matt Jus
15 matches
Mail list logo