Lagg + vlans
-
Looks like when you switched off lagg0 it didn't unassign that IP, I'll check into that. If you reboot is everything brought up correctly?
-
No, i am afraid not.
It didn't after my upgrade and didn't after a fresh install. -
I just tried to add a vlan on lagg0, no dhcp this time.
Just a vlan, added an interface gave it the 172.16.20.254 ip.
Now i still cant ping that address form a machine within that vlan.
And again i get errors in syslog about ifconfig, and an interesting one, the mac change. the machine in vlan2 has 2 interfaces and 2 ips on the vlan, and pfsense notices the machine but does not respond to his ping. nor routes its traffic.I have here the syslog part and the netstat -rn:
Syslog:
Jan 1 17:01:45 pfsense php: /interfaces_vlan_edit.php: The command '/sbin/ifconfig lagg0 vlanhwtag' returned exit code '1', the output was 'ifconfig: vlanhwtag: Invalid argument' Jan 1 17:01:45 pfsense php: /interfaces_vlan_edit.php: The command '/sbin/ifconfig lagg0 vlanmtu' returned exit code '1', the output was 'ifconfig: vlanmtu: Invalid argument' Jan 1 17:01:45 pfsense php: /interfaces_vlan_edit.php: The command '/sbin/ifconfig lagg0 vlanhwfilter' returned exit code '1', the output was 'ifconfig: vlanhwfilter: Invalid argument' Jan 1 17:01:46 pfsense kernel: vlan0: changing name to 'lagg0_vlan2' Jan 1 17:01:48 pfsense check_reload_status: syncing firewall Jan 1 17:02:08 pfsense check_reload_status: syncing firewall Jan 1 17:02:10 pfsense php: /interfaces_assign.php: Creating rrd update script Jan 1 17:02:14 pfsense check_reload_status: syncing firewall Jan 1 17:02:20 pfsense check_reload_status: reloading filter Jan 1 17:02:21 pfsense check_reload_status: syncing firewall Jan 1 17:02:51 pfsense check_reload_status: syncing firewall Jan 1 17:02:53 pfsense apinger: Exiting on signal 15. Jan 1 17:02:53 pfsense apinger: Starting Alarm Pinger, apinger(32229) Jan 1 17:02:53 pfsense apinger: No usable targets found, exiting Jan 1 17:02:53 pfsense php: /interfaces.php: Creating rrd update script Jan 1 17:02:57 pfsense check_reload_status: reloading filter Jan 1 17:05:28 pfsense check_reload_status: syncing firewall Jan 1 17:05:34 pfsense check_reload_status: reloading filter Jan 1 17:07:23 pfsense kernel: arp: 172.16.20.161 moved from 00:0c:29:88:6a:e0 to 00:0c:29:88:6a:d6 on lagg0_vlan2 Jan 1 17:07:48 pfsense sshd[34134]: Accepted keyboard-interactive/pam for root from 172.16.10.96 port 55486 ssh2netstat -rn:
Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 82.192.91.254 UGS 2 24884628 em0 82.192.91.0/24 link#1 U 0 337691 em0 82.192.91.115 link#1 UHS 0 0 lo0 127.0.0.1 link#5 UH 0 18 lo0 127.0.0.2 127.0.0.1 UHS 0 0 lo0 172.16.1.0/29 link#1 U 0 2 em0 172.16.1.6 link#1 UHS 0 0 lo0 172.16.10.0/24 link#9 U 5 42901917 lagg0 172.16.10.254 link#9 UHS 0 0 lo0 172.16.20.0/24 link#10 U 0 0 lagg0_ 172.16.20.254 link#10 UHS 0 0 lo0 172.16.50.0/24 link#2 U 0 1562 em1 172.16.50.254 link#2 UHS 0 0 lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%em0/64 link#1 U em0 fe80::20b:dbff:fe90:e66f%em0 link#1 UHS lo0 fe80::%em1/64 link#2 U em1 fe80::20b:dbff:fe90:e670%em1 link#2 UHS lo0 fe80::%em2/64 link#3 U em2 fe80::202:a5ff:fe4e:acba%em2 link#3 UHS lo0 fe80::%em3/64 link#4 U em3 fe80::202:a5ff:fe4e:acbb%em3 link#4 UHS lo0 fe80::%lo0/64 link#5 U lo0 fe80::1%lo0 link#5 UHS lo0 fe80::%lagg0/64 link#9 U lagg0 fe80::202:a5ff:fe4e:acba%lagg0 link#9 UHS lo0 fe80::%lagg0_vlan2/64 link#10 U lagg0_vl fe80::20b:dbff:fe90:e66f%lagg0_vlan2 link#10 UHS lo0 ff01:1::/32 fe80::20b:dbff:fe90:e66f%em0 U em0 ff01:2::/32 fe80::20b:dbff:fe90:e670%em1 U em1 ff01:3::/32 fe80::202:a5ff:fe4e:acba%em2 U em2 ff01:4::/32 fe80::202:a5ff:fe4e:acbb%em3 U em3 ff01:5::/32 ::1 U lo0 ff01:9::/32 fe80::202:a5ff:fe4e:acba%lagg0 U lagg0 ff01:a::/32 fe80::20b:dbff:fe90:e66f%lagg0_vlan2 U lagg0_vl ff02::%em0/32 fe80::20b:dbff:fe90:e66f%em0 U em0 ff02::%em1/32 fe80::20b:dbff:fe90:e670%em1 U em1 ff02::%em2/32 fe80::202:a5ff:fe4e:acba%em2 U em2 ff02::%em3/32 fe80::202:a5ff:fe4e:acbb%em3 U em3 ff02::%lo0/32 ::1 U lo0 ff02::%lagg0/32 fe80::202:a5ff:fe4e:acba%lagg0 U lagg0 ff02::%lagg0_vlan2/32 fe80::20b:dbff:fe90:e66f%lagg0_vlan2 U lagg0_vl[edit]
the following line bothers me:172.16.20.0/24 link#10 U 0 0 lagg0_Shouldn't it be somethink more then lagg_ ?
[/edit]I hope this sheds more light on the problem and someone can help me :-)
Kind regards, Marcus
-
I know…. I should not bump.
But now the vacation is over. I would bring the topic under the attention of the experts.
I am trying t provide as much info as possible. I cannot be the only one with the problem ???Kind Regards, Marcus van Dam
-
See the same here. So I made a bug report http://redmine.pfsense.org/issues/show/296#change-829
-
Can you please edit interfaces.inc in /etc/inc and remove a line that has hwvlantag in it?!
It should fix your problem.
-
Well, not really.
I can create the vlan, and it shows up in ifconfig,
But when i try to add an OPT2 interface and assign it to the vlan the webinterface hangs, the console still works until you press enter. You can press 8 to start and shell, but as soon as you run "ifconfig" the process freezes, you have to reboot with CRTL-ALT-DEL.I hope this helps.
-
I also found some interesting links about this problem:
Same problem but then in the freebsd treads
http://forums.freebsd.org/showthread.php?t=7668Kernel bug that might explain it al
http://www.freebsd.org/cgi/query-pr.cgi?pr=141646 -
@ermal:
Can you please edit interfaces.inc in /etc/inc and remove a line that has hwvlantag in it?!
It should fix your problem.
Deleting the line does not change anything, hw tagging are still shown on ifconfig. If I do ifconfig emX -vlanhwtag for every em nic I can get as fare as receiving a IP on my static failover trunk but even pinging the gateway fails.
As DJ wrote freezing often happens when assigning nics. -
I cannot seem to get an interface assigned with vlanhwtag turned off. It worked when turned on.
Now it just crashes on every commando you give the machine after assigning. -
Is everyone here trying using Intel em cards? Curious what driver(s) have issues, as that seems to be the cause.
I did get lagg + VLAN trunk working fine with fxp cards, haven't had a chance to test em yet but will, as well as a few other NICs I have available.
-
@cmb:
Is everyone here trying using Intel em cards? Curious what driver(s) have issues, as that seems to be the cause.
I did get lagg + VLAN trunk working fine with fxp cards, haven't had a chance to test em yet but will, as well as a few other NICs I have available.
I am using the Intel
PRO/1000 MT Dual Port Server Adapter (http://www.intel.com/products/server/adapters/pro1000mt-dualport/pro1000mt-dualport-overview.htm) in an Dell 1650 machine.
unfortunately i do not have a second setup to test with different cards.It seems to be related to the em(4) driver.