From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Olek <ned_wed@o2.pl>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridge and port forwarding
Date: Sat, 27 Mar 2010 20:00:36 -0700 [thread overview]
Message-ID: <20100327200036.7e4cc31d@nehalam> (raw)
In-Reply-To: <7515418c.2b6d6e39.4ba7656f.e09eb@o2.pl>
On Mon, 22 Mar 2010 13:41:19 +0100
Olek <ned_wed@o2.pl> wrote:
> Hi,
> I'm stuck with the configuration of my server.
> Currently my network is set up like this:
>
>
> Internet
> |
> |
> Router
> (WAN 192.168.0.99, LAN 192.168.1.99,
> port forwarding 1-65535)
> |
> |
> Ubuntu Server 64-bit
> (WAN(eth0) 192.168.1.110, LAN-bridge(eth1,eth2) 192.168.0.110)
>
>
> Description of the problem:
> When I connect my desktop to the router LAN and try to access FTP, SSH or others the server answers correct (brigde enabled).
> When I try to access the server from the Internet, i get no answer.
> When the bridge is disabled I can easily access SSH or FTP from the Internet.
>
> My bridge config:
> ifconfig eth1 promisc up
> ifconfig eth2 promisc up
Unnecessary step. Bridge has done this automatically for at least
5 years, probably more. But old instructions never die.
> brctl addbr mybridge
> brctl addif mybridge eth1
> brctl addif mybridge eth2
>
> The firewall is disabled, to get sure it's not blocking network traffic.
> Maybe someone knows what's causing this problem?
You need to assign IP address to br0, not the ethernets in the bridge?
next prev parent reply other threads:[~2010-03-28 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 12:41 [Bridge] Bridge and port forwarding Olek
2010-03-28 3:00 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-29 7:38 Olek
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=20100327200036.7e4cc31d@nehalam \
--to=shemminger@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=ned_wed@o2.pl \
/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.