From: Jochen Hebbrecht <jochenhebbrecht@gmail.com>
To: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Ubuntu: network bridging between wireless and wired connection fails
Date: Mon, 04 May 2009 21:42:10 +0200 [thread overview]
Message-ID: <49FF4512.7030004@gmail.com> (raw)
In-Reply-To: <49FF435A.3040806@free.fr>
Nicolas de Pesloüan schreef:
> Jochen Hebbrecht a écrit :
>>
>>
>> Nicolas de Pesloüan schreef:
>>> Ok, now we understand what you are trying to do. In particular, I
>>> assume the DHCP server is on the subnet of location B (or behind a
>>> router connected on this subnet), so the expected DHCP offer will
>>> come from the wire interface (eth0) and definitely not from the
>>> wireless interface (eth1).
>>>
>> Maybe my picture isn't very clear, but my WAN access is on location
>> A. There's a router which receives an ip from the ISP. On the other
>> side, I'm having a 192.168.1.0/24 network
>
> I'm no more really sure I understand your configuration.
>
> The server you are curently trying to setup as a bridge is located in
> location B (UBUNTU SERVER) and has two interfaces : eth0 (ethernet)
> and eth1 (wifi).
>
> Am I right ?
Yes, that's totally correct. I want to receive an IP on my eth1 so my
UBUNTU server is in the same subnet as desktop A and notebook A. By
bridging eth0 and eth1 of UBUNTU SERVER, the IP packets on eth0 will be
forwarded on eth1 to the router, so my printer can ask for a DHCP OFFER
message, by sending a DHCP DISCOVER on the switch. That switch will send
the message to eth0 of UBUNTU SERVER whichs forwards (bridging!) the
packet on eth1 to the router. The router sends a DHCP OFFER back to eth1
of UBUNTU SERVER, which eventually forwards (bridging!) the message back
to switch (and so on to the printer :-))
next prev parent reply other threads:[~2009-05-04 19:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 21:13 [Bridge] Ubuntu: network bridging between wireless and wired connection fails Jochen Hebbrecht
2009-04-27 21:36 ` richardvoigt
2009-04-28 6:44 ` Jochen Hebbrecht
2009-04-28 12:40 ` Ross Vandegrift
2009-04-28 12:52 ` Jochen Hebbrecht
2009-04-28 13:37 ` Ross Vandegrift
2009-04-28 17:36 ` Jochen Hebbrecht
2009-04-28 19:00 ` richardvoigt
2009-04-28 21:16 ` Jochen Hebbrecht
2009-04-28 23:00 ` richardvoigt
2009-04-29 16:16 ` Jochen Hebbrecht
2009-04-29 16:26 ` Ross Vandegrift
2009-04-29 16:40 ` Jochen Hebbrecht
2009-04-29 16:53 ` Ross Vandegrift
2009-04-29 21:21 ` Jochen Hebbrecht
2009-04-30 4:18 ` richardvoigt
2009-04-30 6:30 ` Jochen Hebbrecht
2009-04-30 21:54 ` Nicolas de Pesloüan
2009-05-02 13:15 ` Jochen Hebbrecht
2009-05-03 17:46 ` Nicolas de Pesloüan
2009-05-04 3:59 ` richardvoigt
2009-05-04 19:29 ` Jochen Hebbrecht
2009-05-04 19:28 ` Jochen Hebbrecht
2009-05-04 19:34 ` Nicolas de Pesloüan
2009-05-04 19:42 ` Jochen Hebbrecht [this message]
2009-05-04 20:07 ` Nicolas de Pesloüan
2009-05-04 21:06 ` Jochen Hebbrecht
2009-05-04 23:33 ` richardvoigt
2009-05-05 5:49 ` Nicolas de Pesloüan
2009-05-05 16:59 ` Jochen Hebbrecht
2009-05-05 6:20 ` Nicolas de Pesloüan
2009-05-05 17:01 ` Jochen Hebbrecht
2009-05-05 18:08 ` richardvoigt
2009-05-05 19:19 ` Jochen Hebbrecht
2009-05-05 19:53 ` Jonathan Thibault
2009-05-05 20:52 ` Jochen Hebbrecht
2009-05-05 21:44 ` Nicolas de Pesloüan
2009-05-06 6:57 ` Jochen Hebbrecht
2009-05-06 15:37 ` Jochen Hebbrecht
2009-05-06 16:55 ` Jonathan Thibault
2009-05-09 11:15 ` Jochen Hebbrecht
2009-05-06 16:47 ` Jochen Hebbrecht
2009-05-06 20:07 ` Nicolas de Pesloüan
2009-05-09 11:17 ` Jochen Hebbrecht
2009-05-09 23:30 ` richardvoigt
2009-05-10 15:39 ` Nicolas de Pesloüan
2009-04-29 16:41 ` Jochen Hebbrecht
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=49FF4512.7030004@gmail.com \
--to=jochenhebbrecht@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=nicolas.2p.debian@free.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox