Something is strange with the latest build



  • 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.



  • 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



  • 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,



  • 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)



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

    here's the /tmp/rules.debug

    rules.txt



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



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



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



  • 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>



  • 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>



  • 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.



  • Can  you please retry with next snapshot.



  • 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.



  • 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,



  • 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.



  • 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>



  • Hmmm….still no good. I dunno why this is happening. Keeps me staying at way old build...but works fine though :P
    NO NO, I'm not complaining, just want to help brush up 1.3-AA builds.

    Cheers,



  • Since I use AT&T DSL I have the luxury of being able to change the location from where my PPPoE occurs. I moved the PPPoE back to the DSL modem and switched pfSense from doing PPPoE to DHCP on the WAN interface and all is working. So this appears to be something limited to doing PPPoE on the WAN.

    FYI: ermal, if you need me to do some some testing I have a spare DSL modem that is configured not to do PPPoE that I can switch out for testing.



  • Can you all please post the files
    /var/etc/mpd_wan.conf /var/etc/mpd_wan.links?
    Or if you have the pppoe on an optional interface even the
    /var/etc/mpd_opt#.conf and /var/etc/mpd_opt#.links

    and the respective config.xml part under
    <interfaces>netstat -rn
    and arp -a output</interfaces>



  • Hi ermal,

    okay i have the same Problem.

    Version: 1.3-ALPHA-ALPHA built on Tue Oct 14 18:02:42 EDT 2008 FreeBSD 7.0-RELEASE-p5

    Here is the requested output of the commands:
    http://www.pastie.org/294062

    I recognized that also in the Dashboard sometimes the IP Address of the WAN Interface is not displayed. Also i thought that in the lastest versions i saw also my ip in the SSH Console menue. But there is just NONE(PPPOE) written. But its online. Also i have repeatingly this log entry "php: : Could not find gateway for interface(wan).". I reported a problem to Simon last time, that the NAT Rules doesnt recognize the right ip adresses if you set Outgoing Adress: Interface Address. He made a fix in the repository… since then i had the problem.

    Also it seems that the pppoe interface is working well, but the nat rules didnt. A ping from console over wlan of the router works but not for the connected clients.

    Update
    Updated to "Thu Oct 16 12:03:12" same problem. I saw that if i change the outgoing rule on my lan interface to Gateway: Default the "php: : Could not find gateway for interface(wan)" are coming up.



  • All you that had problems please retry the issue should be fixed.



  • Thanks ermal to your fast reply. The issue is fixed but the messages that he cant find the Gateway still apperars. So i think its different problem.

    Many thanks :)



  • Hello,

    Thanks alot ermal, "all" you mean is that includes port forwarding/nat issues as well? The root cause for this was due to the system couldn't get/set wan/pppoe addrs correctly? Just a curiousity. I will definitely upload the latest build and see how it goes tho…

    cheers,

    @ermal:

    All you that had problems please retry the issue should be fixed.



  • Hi

    Finally up-to-date with the latest. All issues reported here in this thread seems to be addressed and looks good for now :D I will keep my eyes on my box for a couple of more days or so.

    Thanks ermal for your dedication!

    cheers,


Log in to reply