Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
No, AFAIK DRBD uses only TCP and not UDP.
So whatever you are doing for firewalls and services do it for TCP only.
On Mon, 2006-09-11 at 22:57 +1000, Tony's Linux wrote:
> hi,
>
> i just found the problem. It is the firewall on Suse that is stopping it from
> running.
> Does drbd only use TCP or TCP and UDP. I guess adding the line to
> "/etc/services" file:
>
> drbd 7788/TCP
>
> should do it. Am i right or do i also need UDP ?
>
> Thanks
> On Monday 11 September 2006 21:49, Milind Dumbare wrote:
> > On Mon, 2006-09-11 at 21:18 +1000, Tony's Linux wrote:
> > > hi,
> > >
> > > Can someone kindly point what configuration is wrong in my conf file.
> > > Thanks for helping.
> > >
> > > The error status:
> > >
> > > drbd driver loaded OK; device status:
> > > version 0.7.21 (apo:79/proto:74)
> > > SVN Revision: 2326 build
> > > 0: cs:WFConnection st:Primary/Unknown Id:Consistent
> > > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
> > > 1: cs:Unconfigured
> >
> > This isn't error. Your peer is not connected.
> > See cs: (connection status) Waiting for connection.
> >
> > > My drbd.conf:
> > >
> > > resource drbd-mirror1 {
> > > protocol C;
> > > startup {
> > > degr-wfc-timeout 120;
> > > }
> > >
> > > disk {
> > > on-io-error detach;
> > > }
> > >
> > > syncer {
> > > rate 100M;
> > > group 1;
> > > al-extents 257;
> > > }
> > >
> > > on suse-master {
> > > device /dev/drbd0;
> > > disk /dev/hda5;
> > > meta-disk internal;
> > > address 192.168.10.10:7788;
> > > }
> > >
> > > on suse-slave {
> > > device /dev/drbd0;
> > > disk /dev/hda5;
> > > meta-disk internal;
> > > address 192.168.10.11:7788;
> >
> > is drbd up on this machine?
> >
> > > }
> > >
> > > }
> > >
> > > _______________________________________________
> > > drbd-user mailing list
> > > drbd-user at lists.linbit.com
> > > http://lists.linbit.com/mailman/listinfo/drbd-user
>
>
--
-Milind
"There is no place like 127.0.0.1"