[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: Re: [ifupdown] dhcp clients and zcip (zeroconf)
From: "Jason Schoon" <floydpink () gmail ! com>
Date: 2006-04-28 18:03:33
Message-ID: 78a54e1b0604281103t767712d8p72eb6944b3944c16 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 4/28/06, Paul Fox <pgf@brightstareng.com> wrote:
>
> > > > Typically we do this:
> > > >
> > > > Run dhcpc on eth0. If we get a leasefail, run zcip on eth0:1. If
> we
> > > > eventaully get a dhcp address it is configured on eth0 and we have
> both
> > > > eth0 and eth0:1 (from zcip) configured. New traffic is sent on the
> dhcp
> > > > configured interface, but we maintain the zcip configured one so
> that
> > > > existing connections are not dropped.
>
> what's used as the source address for outbound traffic? i'd guess the
> dhcp
> address if it exists, else the eth0:1 address? clearly you'd want to use
> the routable dhcp address as often as possible.
The route table takes care of all of that. As soon as you have a DHCP
address, and are able to talk to things on the DHCP subnet, you will thus
use that interface and the source will be the routable, DHCP address.
> Correct. They are technically the same interface, but having the aliased
> > makes everything play well together. In all actuality, having both on
> the
> > same interfaces didn't cause any problems for me except with the Samba
> > server on our device. This seemed like a nice way to segment things
> though.
>
> what was the samba problem?
I wanted to be able to start the daemon right away when the device started,
and I didn't want to have to hardcode any interface lines into the config
file, since our IP settings can be very dynamic. Samba would only advertise
its shares (and possibly only listen, I can't remember) on the first address
on an interface. Thus, it only advertised shares on the Zcip address, and
none of the local subnet devices thought any shares were available.
I'm sure there is probably some buried config option, or I could have made a
patch, but all of this led me to come up with the aliased solution, which I
liked better anyway.
paul
> =---------------------
> paul fox, pgf@brightstareng.com
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>
[Attachment #5 (text/html)]
On 4/28/06, <b class="gmail_sendername">Paul Fox</b> <<a \
href="mailto:pgf@brightstareng.com">pgf@brightstareng.com</a>> wrote:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > > \
> Typically we do this:<br> > > ><br> > > > Run dhcpc on \
eth0. If we get a leasefail, run zcip on eth0:1. If we<br> > \
> > eventaully get a dhcp address it is configured on eth0 and we have both \
<br> > > > eth0 and eth0:1 (from zcip) configured. New traffic is \
sent on the dhcp<br> > > > configured interface, but we maintain the zcip \
configured one so that<br> > > > existing connections are not dropped. \
<br><br>what's used as the source address for outbound traffic? i'd guess \
the dhcp<br>address if it exists, else the eth0:1 address? clearly you'd \
want to use<br>the routable dhcp address as often as possible.</blockquote> \
<div><br>The route table takes care of all of that. As soon as you have a DHCP \
address, and are able to talk to things on the DHCP subnet, you will thus use that \
interface and the source will be the routable, DHCP address. \
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > \
Correct. They are technically the same interface, but having the aliased \
<br> > makes everything play well together. In all actuality, having \
both on the<br> > same interfaces didn't cause any problems for me except with the \
Samba<br> > server on our device. This seemed like a nice way to \
segment things though. <br><br>what was the samba problem?</blockquote><div><br>I \
wanted to be able to start the daemon right away when the device started, and I \
didn't want to have to hardcode any interface lines into the config file, since our \
IP settings can be very dynamic. Samba would only advertise its shares (and \
possibly only listen, I can't remember) on the first address on an interface. \
Thus, it only advertised shares on the Zcip address, and none of the local subnet \
devices thought any shares were available. <br><br>I'm sure there is probably some \
buried config option, or I could have made a patch, but all of this led me to come up \
with the aliased solution, which I liked better anyway.<br></div><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> paul<br>=---------------------<br> paul fox, <a \
href="mailto:pgf@brightstareng.com">pgf@brightstareng.com</a><br>_______________________________________________<br>busybox \
mailing list<br><a href="mailto:busybox@busybox.net"> busybox@busybox.net</a><br><a \
href="http://busybox.net/cgi-bin/mailman/listinfo/busybox">http://busybox.net/cgi-bin/mailman/listinfo/busybox</a><br></blockquote></div><br>
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic