[PC-BSD Testing] Network problem

[Brodey Dover]

http://lists.pcbsd.org/mailman/listinfo/testing

<http://lists.pcbsd.org/mailman/listinfo/testing>visit the list and follow
the directions for unregistering.

On Sun, May 16, 2010 at 3:44 PM, Michael Rotfort
<rotfortmichael at gmail.com>wrote:

>
> Dear kris ,
> I have already uninstalled(succsesfully) the pc-bsd OS  .
> Because this reason i dont interested to be a part of a mailing list...
> please remove me if you can ...
> Yevgeny Rotfort
>
> 2010/5/16 Kris Moore <kris at pcbsd.org>
>
>> 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
>>
>>
>> _______________________________________________
>> Testing mailing list
>> Testing at lists.pcbsd.org
>> http://lists.pcbsd.org/mailman/listinfo/testing
>>
>>
>
> _______________________________________________
> 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/20100516/a5f5b384/attachment.html>