Something is strange with the latest build

nocer · Oct 8, 2008, 8:42 AM

Hi,

I'm happened to be noticed that the latest build have some issues such as port forwarding doesn't seem to work. Everything is dropped on the WAN and nothing is forwarded. Fall back to older build recover the situation. Never touched the config since last week or so the difference is only a build. I also noticed that the latest kernel has -p5 patch applied so that wondering if that caused as side-effect, or just a php glitch while creating pf rules as usual… ???

cheers,

EDIT: found "php: : WARNING! /etc/rc.newwanip could not deterimine the previous ip address ( wan )." in the system.log repeatedly. This might be a root cause...

eri-- · Oct 8, 2008, 1:35 PM

Can yo uplease post the generated /tmp/rules.debug?

Or if you can find any differences between the working version and this one would be even better.

ArkAngel · Oct 8, 2008, 2:16 PM

Same behavior here with the exact same error message in the system logs.
Using Oct 8, 7:11 AM build.

Ark

Edit: I also use PPPoE if that can help…

nocer · Oct 8, 2008, 8:51 PM

Hi

My apologies, 'cos I was kinda rush for recover and didn't make copies, but there's no difference as far as /tmp/rules.debug is concerned. I also remember the system couldn't set WAN address even WAN was up and running with IP address assigned by PPPoE;

*** Welcome to pfSense 1.3-ALPHA-ALPHA-pfSense on pfsense ***

WAN(WAN)* -> em0 -> NONE
LAN(LAN)* -> em1 -> 192.168.101.1

pfSense console setup

0) Logout (SSH only)
…snip...

So I suspected everything $WAN related in the rules, especially port forwarding, got dropped.
*However, I was able to see WAN address in the WebGUI via Interface stats/gadget.

@ermal:

Can yo uplease post the generated /tmp/rules.debug?

Or if you can find any differences between the working version and this one would be even better.

I will keep evidence next time.

cheers,

Stef · Oct 9, 2008, 5:25 AM

You're not alone,

I've got the same problem.

I started having that problem 2 nights ago.

Didn't change rules before the problem either.

Upgraded yesterday evening and still same problem.

Will look tonight if I find the debug info and up it

All outgoing trafic works fine.

greyman · Oct 9, 2008, 11:19 AM

Would like to add a me to. Below is my build information.

built on Wed Oct 8 17:46:25 EDT 2008 FreeBSD 7.0-RELEASE-p5

nocer · Oct 11, 2008, 1:00 AM

Hi

just bumps…anybody touched any new builds since then? I must keep my box running for this week end and won't have time to play.

cheers,

morbus · Oct 11, 2008, 10:42 AM

I had this problem on 1.3-ALPHA-ALPHA built on Thu Oct 9 08:43:51 EDT 2008

I had to open edit for each rule and save it again and then apply changes then it worked but I had only just upgraded from 1.2 so assumed it was to do with the upgrade (full new install then restore the xml to the new install)

Stef · Oct 11, 2008, 11:13 AM

Hi after the last update thursday evening, it's still not ok.

here's the /tmp/rules.debug

rules.txt

eri-- · Oct 12, 2008, 9:49 AM

If possible, can you give me output of ifconfig command and the output of cat /tmp/pppoe0_router?

greyman · Oct 12, 2008, 1:22 PM

ermail, I have an interface pppoe0 when I run ifconfig -a but there is no such file /tmp/pppoe0_router.

eri-- · Oct 12, 2008, 2:31 PM

Can you give me the output of ifconfig just the pppoe0 interface one you can clear the adresses if you want

greyman · Oct 12, 2008, 4:07 PM

pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
inet6 fe80::200:24ff:fec9:54cc%pppoe0 prefixlen 64 scopeid 0xf
inet 70.252.167.xxx –> 70.252.167.xxx netmask 0xffffffff</up,pointopoint,running,noarp,simplex,multicast>

nocer · Oct 13, 2008, 1:21 PM

Hi

Jee…still no luck. I neither find /tmp/pppoe0_router so here's ifconfig(changed MTU accordingly to fit my ISP's)

pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1454
inet6 fe80::204:23ff:fea7:f8b6%pppoe0 prefixlen 64 scopeid 0x7
inet 219.102.xxx.xxx --> 210.165.xxx.xxx netmask 0xffffffff

And, compared /tmp/rules.debug bit by bit for both working 1002-build and the several non-working builds from 11th/12th. The rules are identical. No changes made, no remove, no modify, nothing.

What's next?

cheers,</up,pointopoint,running,noarp,simplex,multicast>

greyman · Oct 13, 2008, 10:37 PM

I can add one thing. when looking for /tmp/pppoe0_router I found /tmp/vr1_router. vr1 in my case is the port that my AT&T speedstream DSL modem is attached to.

eri-- · Oct 13, 2008, 10:45 PM

Can you please retry with next snapshot.

greyman · Oct 13, 2008, 10:52 PM

That should not be a problem. This is a home network and I have a 4801 running off a CF for when things break ;-). Just let me know the build time I am looking for that you want me to test.

nocer · Oct 14, 2008, 12:33 AM

Hi

Yeah, I was thinking to have spare 2.5"HDD for the situation like this, actually look'n for some CF solution instead… :P

@ermal, Thank you always for you dedication. Really looking forward to playing the next snap.

@greyman:

That should not be a problem. This is a home network and I have a 4801 running off a CF for when things break ;-). Just let me know the build time I am looking for that you want me to test.

Cheers,

greyman · Oct 14, 2008, 2:30 AM

Looks like the last snapshot to be generated was on the 10/11/2008. So I guess we are looking for anything that is newer than your post ermal.

I also second nocer's comments about your time and dedication.

greyman · Oct 14, 2008, 3:48 AM

No go… ;(

Here is the build info: built on Mon Oct 13 22:27:46 EDT 2008

ifconfig pppoe0

pppoe0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
inet6 fe80::200:24ff:fec9:54cc%pppoe0 prefixlen 64 scopeid 0xd
inet 70.255.104.xxx --> 70.255.105.xxx netmask 0xffffffff

There are no files referencing vr1 or pppoe0 in /tmp</up,pointopoint,running,noarp,simplex,multicast>