Opened 6 years ago

Closed 5 years ago

#220 closed System Defect (fixed)

New Network System strange behavior

Reported by: yerenkow Owned by: kris
Priority: major Milestone: 8.0
Component: System Configuration Version: 8.0-ALPHA
Keywords: Cc: trac-bugs@…


I have such nic:

ath0 (which became wlan1)

Before I enter some settings, it all creates into lagg0, but only ipv6.

I couldn't configure anything.
Disable fwe0 and bge0 make my wlan1 find access point, but only in ipv6 - nothing works.

Change History (3)

comment:1 Changed 6 years ago by kris

Can you provide more details?

Right now I don't have the GUI tools to setup to enable ipv6 across the lagg0 interface. Is that what you are missing, or is IPv6 the only thing working?

Just so you know, we are trying out the lagg0 interface, since it provides automatic fail-over between wifi / wired, so you can unplug ethernet, go wifi, and not lose any active connections. It does require a bit different configuration in rc.conf, but it seems to be working ok on my laptop here.

comment:2 Changed 6 years ago by yerenkow

More info:
After trying to set network settings, X session locks; no new programs can be started;
If do logout-login - network systray icon appear, but wlan1 have only ipv6.

Here is rc.conf part:
ifconfig_="ifconfig bge0 ether"
ifconfig_="ether ${ifconfig_##*ether}"
interface_lagg0="laggproto failover laggport bge0 laggport wlan1 DHCP"
ifconfig_ath0="ifconfig bge0 ether"
ifconfig_ath0="ether ${ifconfig_ath0##*ether}"

ifconfig lagg0 didn't show laggport wlan1.

After few reboots, lagg0 show laggport wlan1, and pings are working (however, wlan1 have no ip4, only ip6).
lagg0 have ip4 which should be given to wlan1 (as told me so my router)

comment:3 Changed 5 years ago by kris

  • Resolution set to fixed
  • Status changed from new to closed

Should be fixed now, was a bug in pc-sysinstall, all those ifconfig_="" lines were messing stuff up, had to fix that first :P

Note: See TracTickets for help on using tickets.