[PC-BSD Testing] Network problem

Jeff dejamuse at yahoo.com
Mon May 17 05:57:25 PDT 2010


Well I don't know what happened but all of a sudden it's working after a 2nd reboot.  Weird.

All I changed was the one line in resolv.conf in the jail: nameserver 192.168.1.2

After that change I rebooted but nothing changed until this morning I fired up the box and voila!

I sure would like to know what was wrong and why it's suddenly working.

Current state:

# ifconfig

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 
mtu 1500

        
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>

        ether 00:24:8c:a1:b3:f7

        inet6 fe80::224:8cff:fea1:b3f7%re0 prefixlen 64 scopeid 0x1

        media: Ethernet autoselect (100baseTX <full-duplex>)

        status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

        options=3<RXCSUM,TXCSUM>

        inet 127.0.0.1 netmask 0xff000000

        inet6 ::1 prefixlen 128

        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

pflog0: flags=0<> metric 0 mtu 33152

pfsync0: flags=0<> metric 0 mtu 1460

        syncpeer: 224.0.0.240 maxupd: 128

lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
 mtu 1500

        
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>

        ether 00:24:8c:a1:b3:f7

        inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255

        inet6 fe80::224:8cff:fea1:b3f7%lagg0 prefixlen 64 scopeid 0x5

        inet 192.168.1.12 netmask 0xffffffff broadcast 192.168.1.12

        media: Ethernet autoselect

        status: active

        laggproto failover

        laggport: re0 flags=5<MASTER,ACTIVE>

lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

        options=3<RXCSUM,TXCSUM>

        inet 10.1.1.1 netmask 0xffffff00

-----------------

rc.conf contains these lines:



defaultrouter="192.168.1.2"

cloned_interfaces="lagg0"

ifconfig_lagg0="laggproto failover laggport re0 192.168.1.10 netmask 
255.255.255.0"

ifconfig_re0="up"



--- On Sun, 5/16/10, Kris Moore <kris at pcbsd.org> wrote:

From: Kris Moore <kris at pcbsd.org>
Subject: Re: [PC-BSD Testing] Network problem
To: testing at lists.pcbsd.org
Date: Sunday, May 16, 2010, 2:44 PM





  
On 05/14/2010 13:55, Jeff wrote:

  
    
      
        I still have this weird problem with a server running in
a jail.  

        

I reloaded a database into MySQL and noted that suddenly the server
response was back to normal and Drupal could talk to the internet
again.  Then I ran the DB update script because I had updated a module,
and it broke again.  So this is more complicated than I thought. Not
sure how changing network parameters triggers this.

        

But I did notice a difference between two machines.  Both are running
Drupal with the Warden, and the one with this problem shows the static
IP for the box (192.168.1.10) associated with lagg0 (along with the
jail, 192.168.1.12), not the NIC, re0.  Whereas the other machine is
the opposite.  Does this indicate a problem?

        

# ifconfig

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
mtu 1500

       
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>

        ether 00:24:8c:a1:b3:f7

        inet6 fe80::224:8cff:fea1:b3f7%re0 prefixlen 64 scopeid 0x1

        media: Ethernet autoselect (100baseTX <full-duplex>)

        status: active

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

        options=3<RXCSUM,TXCSUM>

        inet 127.0.0.1 netmask 0xff000000

        inet6 ::1 prefixlen 128

        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2

pflog0: flags=0<> metric 0 mtu 33152

pfsync0: flags=0<> metric 0 mtu 1460

        syncpeer: 224.0.0.240 maxupd: 128

lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric
0 mtu 1500

       
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>

        ether 00:24:8c:a1:b3:f7

        inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255

        inet6 fe80::224:8cff:fea1:b3f7%lagg0 prefixlen 64 scopeid 0x5

        inet 192.168.1.12 netmask 0xffffffff broadcast 192.168.1.12

        media: Ethernet autoselect

        status: active

        laggproto failover

        laggport: re0 flags=5<MASTER,ACTIVE>

lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

        options=3<RXCSUM,TXCSUM>

        inet 10.1.1.1 netmask 0xffffff00

------------------------

Other machine:

        

# ifconfig

bge0: flags=8843<UP,BROADCAST,
         RUNNING,SIMPLEX,MULTICAST>
metric 0 mtu 1500

        options=9b<RXCSUM,TXCSUM,VLAN_ MTU,VLAN_HWTAGGING,VLAN_ HWCSUM>

        ether 00:11:11:c3:7a:e2

        inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255

        media: Ethernet autoselect (100baseTX <full-duplex>)

        status: active

plip0: flags=108810<POINTOPOINT, SIMPLEX,MULTICAST,NEEDSGIANT>

metric 0 mtu 1500

lo0: flags=8049<UP,LOOPBACK, RUNNING,MULTICAST> metric 0 mtu
16384

        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3

        inet6 ::1 prefixlen 128        inet 127.0.0.1 netmask 0xff000000

pfsync0: flags=0<> metric 0 mtu 1460

        syncpeer: 224.0.0.240 maxupd: 128

pflog0: flags=0<> metric 0 mtu 33204
        

        
      
    
  
  




Taking lagg0 out of the equation would be the first thing to try. If
that fixes the issue, then we can isolate it to a lagg problem, and let
freebsd mantainers know. Also, what does your "db update script" do? Is
it changing some drupal / sql setting and causing this? That makes it
sound like its not a network configuration problem. 



-- 
Kris Moore
PC-BSD Software
iXsystems
 

-----Inline Attachment Follows-----

_______________________________________________
Testing mailing list
Testing at lists.pcbsd.org
http://lists.pcbsd.org/mailman/listinfo/testing



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pcbsd.org/pipermail/testing/attachments/20100517/697552f7/attachment.html>


More information about the Testing mailing list