And a ping -c 3 IP from the exec.php page also succeeds?

Wireless still non functional on alix with atheros minipci card. same issues

Can not replicate.

When I try a snmpwalk -c public -v2c hostname it works here with a snapshot from today.

In 1.3 you need to add all the gateways in the system under System -> Routing -> Gateways Tab.

After adding all the gateways you can then create a gateway group on the Gateway Group Tab. Set a priority for each wan connection that you want to have participate in each pool.

Then assign this gateway group to a firewall rule (generally the LAN rule).

Read the traffic shaper bounty thread i have gone into detail there.
Nothing is wrong with queue names and filter rules.

Resolved with version:
1.3-ALPHA-ALPHA
built on Mon Aug 11 05:54:58 EDT 2008
FreeBSD 7.0-RELEASE-p3

I didn't think it ever did that, but thought maybe you were aware of a feature I wasn't.  :)

I changed that to a feature request ticket.

No "stupid mistake autofix" coding completed yet eh?

Wonder what other network issues I caused myself with those errors…  ::)

Thanks!  ;D

@m3isp:

When creating your gateways DO NOT use special characters including spaces and capital letters. After making this change the "Never" tier reappearing for my second gate was corrected. Now to move on and test out the load balancer.

opened a ticket on this.

That used to exist in 1.2, and LAN used to not be there twice. That's a regression, we'll get it resolved.

Copy hung, it's been restarted.

@cmb:

@eskild:

Hi,
i'm having a similar problem for an opt interface on Rel 1.2 full inst:

There were error(s) loading the rules: /tmp/rules.debug:129: syntax error/tmp/rules.debug:130: syntax error /tmp/rules.debug:131: syntax error /tmp/rules.debug:224: syntax error pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [129]: pass in quick on $PubWlan proto udp from any port = 68 to 255.255.255.255 port = 67 label "allow access to DHCP server"…

I got around by changing the opt interface name to lowercase letters, but this should be fixed on 1.2.x as well.

Mixed case on 1.2 has never been a problem, this thread is entirely related to changes in 1.3. I have 1.2 installs using mixed case interface names and know many others do as well. I'm guessing you probably have an alias with the same name, which isn't valid and input validation has been added to 1.2.1 to prevent that.

Yes, you are absolutely right. I had an alias with the same name as the interface. After I changed the alias, and then the interface name, I no longer see the previous problems.

Thanks for all your help, it is highly appreciated.

loose information is now fixed…
thanks a lot !

sorry missed that. can I delete this tread and append my post to the other?

I'd suggest that you:

Ask in the 1.3 Alpha forum that I've already directed you to Read my previous post again for my advice

@ermal:

Grab a recent snapshot and retest the FloatingRules should be ok now.

Upgrade to 1.3-ALPHA-ALPHA built on Mon Aug 4 07:39:20 EDT 2008 FreeBSD 7.0-RELEASE-p3, Floating Rules works fine.