2.0.2 x86 upgrades - 1 issue [solved] - 1 note for pfBlocker users



  • I've done six 2.0.1 -> 2.0.2 upgrades (all x86) so far.
    2 were manual and 4 were auto-updates.

    Packages:
    Squid 3 (upgraded from 2) + SquidGuard + Sarg
    Unbound
    pfBlocker
    widescreen
    OpenVPN Package Installer

    ½ have IKE VPNs
    ½ have OpenVPNs (1 has both)

    My results:
    On all -> pfBlocker needed to be manually started after the reboot. Afterward it's fine.

    On one -> My LAN connection would drop following a check_reload_status.
    This was an older machine w/ a Realtek based PCMCIA adapter.

    It would happen as early as 5pm and as late as 2am.  I have Offsite backups over IKE VPN between 6:30pm and 2am.
    Sometimes the connection drops would coincide w/ a backup, sometimes not.

    This seems to have fixed it:
    System -> Advanced -> Miscellaneous -> check in Schedule States box.

    Log of problem for reference.  This would happen 4x-10x a night.

    Jan 2 17:13:14 	check_reload_status: Reloading filter
    Jan 2 17:13:14 	apinger: Starting Alarm Pinger, apinger(53774)
    Jan 2 17:13:13 	apinger: Exiting on signal 15.
    Jan 2 17:13:13 	php: : rc.newwanip: on (IP address: 192.168.70.1) (interface: lan) (real interface: rl1).
    Jan 2 17:13:13 	php: : rc.newwanip: Informational is starting rl1.
    Jan 2 17:13:10 	check_reload_status: rc.newwanip starting rl1
    Jan 2 17:13:10 	php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.70.1)
    Jan 2 17:13:08 	php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.70.1)
    Jan 2 17:13:08 	kernel: rl1: link state changed to UP
    Jan 2 17:13:08 	check_reload_status: Linkup starting rl1
    Jan 2 17:13:06 	kernel: rl1: link state changed to DOWN
    Jan 2 17:13:06 	check_reload_status: Linkup starting rl1
    

    I have 4 upgrades left to do. I'm pretty optimistic.



  • @LinuxTracker:

    On all -> pfBlocker needed to be manually started after the reboot. Afterward it's fine.

    Pfblocker disables the service after package/system reinstall/upgrade  ;)



  • My problem w/ the Realtek adapter periodically dropping the LAN connection has returned.

    Interestingly, the WAN adapter is also dropping it's connection.

    Checking the Schedule States box didn't work after all.

    I'm trying the States option just below it.
    (I doubt it will solve the problem but it may help my broken network services recover.)

    EDIT: As I'm writing this I discovered that the LAN connection is autoselecting 10Mbps.
    I may have a bad LAN cable.

    I'll replace the cable, set the States settings back to default and see if that sorts out both NICs.

    If I don't update this thread you can assume that was the problem.



  • Still having problem I mentioned in OP.

    On one machine, my LAN adapter resets periodically throughout the day.

    Jan 10 03:44:23 	check_reload_status: Reloading filter
    Jan 10 03:44:23 	apinger: Starting Alarm Pinger, apinger(14339)
    Jan 10 03:44:22 	apinger: Exiting on signal 15.
    Jan 10 03:44:22 	php: : rc.newwanip: on (IP address: 192.168.70.1) (interface: lan) (real interface: rl1).
    Jan 10 03:44:22 	php: : rc.newwanip: Informational is starting rl1.
    Jan 10 03:44:19 	check_reload_status: rc.newwanip starting rl1
    Jan 10 03:44:19 	php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.70.1)
    Jan 10 03:44:17 	php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.70.1)
    Jan 10 03:44:17 	kernel: rl1: link state changed to UP
    Jan 10 03:44:17 	check_reload_status: Linkup starting rl1
    Jan 10 03:44:15 	kernel: rl1: link state changed to DOWN
    Jan 10 03:44:15 	check_reload_status: Linkup starting rl1
    

    It's a DLink PCMCIA w/ a Realtek rtl8169b chipset.

    I've replaced the LAN cable.
    I've changed the states settings as mentioned in above post.
    I've upgraded to 2.0.3 PreRelease.
    I set the adapter to 10Mbps Full.

    As near as I can see none of it has had an effect.

    Can anyone suggest a network config or Realtek-specific setting (or anything else) I could try?

    and

    @marcelloc:

    Pfblocker disables the service after package/system reinstall/upgrade

    Thanks marcelloc. I suppose I should keep that in mind.



  • @LinuxTracker:

    Still having problem I mentioned in OP.

    On one machine, my LAN adapter resets periodically throughout the day.
    It's a DLink PCMCIA w/ a Realtek rtl8169b chipset.

    Looks like it's fixed now.
    In the end I bought another adapter and it hasn't reset since.

    FYI: Went from a DLink DFE-690TXD rtl8139b to a Netgear GA311 rtl8169s pcmcia cardbus NIC - $8 delivered from Amazon.



  • Same machine - but the onboard WAN adapter is resetting now.  It probably has been all along, but not as often.
    (LAN adapter still OK after swapping out.)

    The WAN adapter has a chip from the Realtek 8139 family. So did the buggy DLink card I replaced.

    I've found freeBSD threads where folks were struggling w/ Realtek 8139 (and 8169) drivers w/ diff 8.1/8.2 releases.
    Links are at the bottom for reference.

    A few folks found relief by adding the appropriate line(s) the following to the /boot/loader.conf file.

    dev.rl.0.prefer_iomap="0" # for rl0
    dev.rl.1.prefer_iomap="0" # for rl1
    dev.rl.3.prefer_iomap="0" # for rl3
    

    We'll see if this works for me.

    Note: I keep adding to this thread because I'm convinced someone else will run into this.
    I'm hoping to same them some time.

    Links for ref:
    http://forums.freebsd.org/showthread.php?t=17122
    http://forums.freebsd.org/showthread.php?t=22701

    PS: My adapters are set to default but
    LAN = 8169 Gigabit card is running at 100baseTX <full-duplex>(was running at Gigabit)
    WAN = 8139 10/100BaseTX adapter is running at 10baseT/UTP <full-duplex>(was running at 100baseTX)
    Maybe related to this -> http://forums.freebsd.org/showthread.php?t=22664</full-duplex></full-duplex>



  • LinuxTracker - you may want to consider this nic if you have to purchase another pcmcia adapter in the future. I moved off realtek and onto this card based on the dc driver and it's been great. Fully supported and no issues. Given the time you'll save troubleshooting, it'll pay for itself immediately.

    NETGEAR FA511 10/100Mbps PCMCIA Ethernet Adapter
    http://www.amazon.com/NETGEAR-FA511-32-bit-CardBus-Mobile/dp/B00005NWV1/



  • @trunix:

    LinuxTracker - you may want to consider this nic if you have to purchase another pcmcia adapter in the future. I moved off realtek and onto this card based on the dc driver and it's been great.

    Appreciate the reply.
    Unfortunately the WAN adapter is giving me trouble right now and it's onboard.
    The notebook only has one PCMCIA slot and for whatever reason I don't like USB NICs.

    The location where this is has a newer notebook on hand; I'll just swap it out.
    That should put an end to this saga - or at least to this thread.

    @trunix:

    NETGEAR FA511 10/100Mbps PCMCIA Ethernet Adapter

    I was wondering what chipset was inside that card.
    It took me a while but I finally found a partial list of Netgear Chipsets
    http://tuto.netgear-forum.com/Documentation/Chipsets/


Log in to reply