Joshua J. Kugler
2016-Mar-23 03:12 UTC
[Gluster-users] Peer probe succeeded, but "not in 'Peer in Cluster' state"
On Tuesday, March 22, 2016 22:12:00 Russell Purinton wrote:> If the subnet mask is wrong on 122.11 it may forward all traffic to the > default gateway. The default gateway may be configured to NAT traffic from > the LAN, so the response packet would be seen by .10 as coming from .1.So, it turns out the subnet isn't wrong, but for some reason, it's still routing through the gateway, and appears to be coming from .1, instead of .11. I'm not sure why. This is a libvirt network, configured thus: <network> <name>default</name> <uuid>f137a5c4-1dd2-453a-a6e6-c161f2918d41</uuid> <forward mode='route'/> <bridge name='virbr0' stp='on' delay='0'/> <mac address='52:54:00:42:87:a9'/> <ip address='192.168.122.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.122.2' end='192.168.122.254'/> </dhcp> </ip> </network> When this was working, I was using forward mode=nat, but then two different libvirt networks couldn't talk to each other. The two machines are on the same segment, on the same virtual switch. I'm not sure why they are getting routing through the gateway. Off to do more troubleshooting! :) j -- Joshua J. Kugler - Fairbanks, Alaska Azariah Enterprises - Programming and Website Design joshua at azariah.com - Jabber: pedahzur at gmail.com PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
Pawan Devaiah
2016-Mar-23 03:39 UTC
[Gluster-users] Peer probe succeeded, but "not in 'Peer in Cluster' state"
The third statement in your route table states that for any network the default gateway is 192.168.122.1 I would suggest either you remove that statement or increase the metrics from 0, you already have a route to 192.168.122.0, it is in same broadcast domain so you don't have to go through the gateway. Cheers Dev On Wed, Mar 23, 2016 at 4:12 PM, Joshua J. Kugler <joshua at azariah.com> wrote:> On Tuesday, March 22, 2016 22:12:00 Russell Purinton wrote: > > If the subnet mask is wrong on 122.11 it may forward all traffic to the > > default gateway. The default gateway may be configured to NAT traffic > from > > the LAN, so the response packet would be seen by .10 as coming from .1. > > So, it turns out the subnet isn't wrong, but for some reason, it's still > routing through the gateway, and appears to be coming from .1, instead of > .11. > I'm not sure why. This is a libvirt network, configured thus: > > <network> > <name>default</name> > <uuid>f137a5c4-1dd2-453a-a6e6-c161f2918d41</uuid> > <forward mode='route'/> > <bridge name='virbr0' stp='on' delay='0'/> > <mac address='52:54:00:42:87:a9'/> > <ip address='192.168.122.1' netmask='255.255.255.0'> > <dhcp> > <range start='192.168.122.2' end='192.168.122.254'/> > </dhcp> > </ip> > </network> > > When this was working, I was using forward mode=nat, but then two different > libvirt networks couldn't talk to each other. The two machines are on the > same segment, on the same virtual switch. I'm not sure why they are getting > routing through the gateway. Off to do more troubleshooting! :) > > j > > -- > Joshua J. Kugler - Fairbanks, Alaska > Azariah Enterprises - Programming and Website Design > joshua at azariah.com - Jabber: pedahzur at gmail.com > PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160323/e900dc04/attachment.html>