4. Suddenly cannot reach net

Suddenly cannot reach net

  • M

    Earlier tonight all my machines suddenly dropped their net connections. A restart of the pfsense box and I thought it would be fine. I can ssh into the box and then using the console no problem pinging the net via number or name. But nothing behind the box can ping anything in the outside world. None of the machines or the wireless access point.

    I've changed nothing on the box in weeks so I'm not sure what on earth has happened. Anyone any ideas as to what it is and what I can do to sort it? Many thanks from a much balder person than when I used my homehub!

    0
  • M

    Can you ping with ip-address?

    Last sunday i lost internet connection, atleast my girlfriend was thinking of. few seconds testing showed that dns server needs to be booted. after that everything is fine again.

    0
  • Netgate Administrator

    @malcmail:

    Many thanks from a much balder person than when I used my homehub!

    Haha!  :D

    We are going to need more information than that. What hardware are you using? I take it you're on a home ADSL connection? How many clients?

    It seems strange that it would suddenly stop routing any traffic without any outside interference. Could it a be a memory problem, run out of states?

    Can you ping via IP or URL from LAN. If you ping via URL does it return an IP, is dns working? Is there anything in the pfSense logs?

    Steve

    0
  • M

    Thanks guys. I'll give you what detail I can remember as the box is currently sitting sulking!

    On what it can and cannot do - the pfsense box, once I patch into it via ssh or through the web interface will ping the outside world either using 8.8.8.8 or google.com. Anything behind the box won't do either.

    Hardware - from memory Pentium 4 2.6GHz, 2 RAM and about an 80GB hard drive. I think its running 2.0 but not using the dialy build update as I did that before and it caused me a bundle of headaches, much like this one!

    Home ADSL, max clients would be about 10, but generally speaking 3 PCs and a phone most the time. The pfsense box runs DHCP on a small range (200 - 210) and the devices are all set to get an IP address automatically outside of this range as the box allocates them by MAC address.

    The set up is modem using passthrough, pfsense box , wireless AP. ALl working perfectly beforehand.

    Recently I've seen apinger alerts in the log but thats not caused any issues. Plenty of states left (I think my max is 10,000 and I dont think I've seen it above 1,000). At the moment with rebooting etc there is a line about DHCP possibly not starting or similar (can't recall exactly), but DNSMASQ does load the static IPs and seems to be allocating them correctly.

    If you need any more let me know. Ta muchly.

    0
  • M

    With 2GB ram you could have somewhere near 200 000 states

    0
  • Netgate Administrator

    Anything from LAN in the firewall log?
    I doubt there will be since you can still access the GUI and ssh in.

    Do you have outbound NAT set to manual?

    You haven't changed anything?

    Steve

    0
  • M

    Its basically an out of the box set up with a couple of ports allowed from the net to my PS3 and thats it. My firewall log only logs external traffic that is allowed in.

    And nope - not touched a thing. Its been running smoothly without any interference from me for about a couple of months I'd guess. And then bang problem time.

    Outbound NAT to manual does ring a bell though. Thnk this was to do with my PS3 set up (or possibly a VPN to an internal machine). Again thats been the way for a couple months though.

    0
  • Netgate Administrator

    It would be worth checking the the outbound NAT rule left in place when you switched to manual still makes sense. It should.  :-
    Pinging from LAN do you get an IP address followed by host unreachable or request timed out. Or do you get 'cannot find host' or something similar. I.E. is DNS forwarding working at all?

    If it isn't it should show in Status: Services:

    Steve

    0
  • M

    UNless the outbound rule changed itself it should be ok lol. I can fire it up and check though.

    As for pinging from LAN on my Windows box it just had "Request timed out" 3 times over.

    0
  • M

    Check your logs, take packetcaptures while pinging etc.
    If possible or needed take screenshots

    0
  • M

    @Metu69salemi:

    Check your logs, take packetcaptures while pinging etc.
    If possible or needed take screenshots

    Is there anything in particular I should be looking for? I only ask as I'll have to take down my existing connection and fire up the box etc so then I can't connect to check.

    0
  • M

    So I fired it up again and did the packet capture thing. 192.168.1.1 is the pfsense box, 253 is the wireless AP attached to it and 124 is the machine I was using to patch into it and do the testing.  Results….

    17:49:34.600689 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:34.642125 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:34.679722 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:35.225606 IP 192.168.1.124.61889 > 192.168.1.1.53: UDP, length 35
    17:49:36.183100 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.183110 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.183118 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.183127 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.183246 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.183367 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 615
    17:49:36.183490 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.183614 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.190606 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.190634 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.190648 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.226876 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.226891 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 1460
    17:49:36.226903 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 615
    17:49:36.260860 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.291574 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.326169 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.353273 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.386807 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.415757 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:36.444788 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:49:37.417832 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
    17:49:39.231667 IP 192.168.1.124.61889 > 192.168.1.1.53: UDP, length 35
    17:49:42.513975 IP 192.168.1.124.57279 > 192.168.1.1.53: UDP, length 37
    17:49:43.507988 IP 192.168.1.124.57279 > 192.168.1.1.53: UDP, length 37
    17:49:44.509579 IP 192.168.1.124.57279 > 192.168.1.1.53: UDP, length 37
    17:49:46.235589 IP 192.168.1.124.59867 > 192.168.1.1.53: UDP, length 35
    17:49:46.512506 IP 192.168.1.124.57279 > 192.168.1.1.53: UDP, length 37
    17:49:47.233609 IP 192.168.1.124.59867 > 192.168.1.1.53: UDP, length 35
    17:49:48.235146 IP 192.168.1.124.59867 > 192.168.1.1.53: UDP, length 35
    17:49:49.255355 IP 192.168.1.124 > 192.168.1.1: ICMP echo request, id 768, seq 24576, length 40
    17:49:49.255376 IP 192.168.1.1 > 192.168.1.124: ICMP echo reply, id 768, seq 24576, length 40
    17:49:50.009050 IP 192.168.1.124.17500 > 255.255.255.255.17500: UDP, length 109
    17:49:50.046421 IP 192.168.1.124.17500 > 255.255.255.255.17500: UDP, length 109
    17:49:50.085853 IP 192.168.1.124.17500 > 192.168.1.255.17500: UDP, length 109
    17:49:50.127621 IP 192.168.1.124.17500 > 255.255.255.255.17500: UDP, length 109
    17:49:50.238148 IP 192.168.1.124.59867 > 192.168.1.1.53: UDP, length 35
    17:49:50.273123 IP 192.168.1.124 > 192.168.1.1: ICMP echo request, id 768, seq 24832, length 40
    17:49:50.273137 IP 192.168.1.1 > 192.168.1.124: ICMP echo reply, id 768, seq 24832, length 40
    17:49:50.518541 IP 192.168.1.124.57279 > 192.168.1.1.53: UDP, length 37
    17:49:51.259696 IP 192.168.1.124 > 192.168.1.1: ICMP echo request, id 768, seq 25088, length 40
    17:49:51.259710 IP 192.168.1.1 > 192.168.1.124: ICMP echo reply, id 768, seq 25088, length 40
    17:49:51.868730 IP 192.168.1.1.22 > 192.168.1.124.4428: tcp 64
    17:49:51.870171 IP 192.168.1.124.4428 > 192.168.1.1.22: tcp 32
    17:49:51.870202 IP 192.168.1.1.22 > 192.168.1.124.4428: tcp 0
    17:49:51.906523 IP 192.168.1.124.4428 > 192.168.1.1.22: tcp 32
    17:49:51.906540 IP 192.168.1.1.22 > 192.168.1.124.4428: tcp 0
    17:49:52.261198 IP 192.168.1.124 > 192.168.1.1: ICMP echo request, id 768, seq 25344, length 40
    17:49:52.261213 IP 192.168.1.1 > 192.168.1.124: ICMP echo reply, id 768, seq 25344, length 40
    17:49:53.907159 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
    17:49:54.244204 IP 192.168.1.124.59867 > 192.168.1.1.53: UDP, length 35
    17:49:54.808026 ARP, Request who-has 192.168.1.253 tell 192.168.1.124, length 46
    17:49:56.214801 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
    17:49:57.531590 IP 192.168.1.124.52212 > 192.168.1.1.53: UDP, length 37
    17:49:58.530621 IP 192.168.1.124.52212 > 192.168.1.1.53: UDP, length 37
    17:49:59.532106 IP 192.168.1.124.52212 > 192.168.1.1.53: UDP, length 37
    17:50:01.253449 IP 192.168.1.124.52593 > 192.168.1.1.53: UDP, length 35
    17:50:01.535172 IP 192.168.1.124.52212 > 192.168.1.1.53: UDP, length 37
    17:50:02.246219 IP 192.168.1.124.52593 > 192.168.1.1.53: UDP, length 35
    17:50:02.470664 38:e7:d8:c3:5b:df > ff:ff:ff:ff:ff:ff Null Supervisory, Receiver not Ready, rcv seq 64, Flags [Poll], length 46
    17:50:02.653503 IP 192.168.1.124 > 8.8.8.8: ICMP echo request, id 768, seq 26624, length 40
    17:50:03.247642 IP 192.168.1.124.52593 > 192.168.1.1.53: UDP, length 35
    17:50:03.621468 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
    17:50:05.239941 IP6 fe80::3ae7:d8ff:fec3:5bdf > ff02::2: ICMP6, router solicitation, length 16
    17:50:05.250594 IP 192.168.1.124.52593 > 192.168.1.1.53: UDP, length 35
    17:50:05.541122 IP 192.168.1.124.52212 > 192.168.1.1.53: UDP, length 37
    17:50:05.588315 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 23
    17:50:05.588368 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 0
    17:50:05.589656 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:50:06.264817 IP 192.168.1.124.4454 > 192.168.1.1.443: tcp 0
    17:50:06.264852 IP 192.168.1.1.443 > 192.168.1.124.4454: tcp 0
    17:50:07.327344 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
    17:50:07.724349 IP 192.168.1.124 > 8.8.8.8: ICMP echo request, id 768, seq 26880, length 40
    17:50:08.330001 IP6 fe80::3ae7:d8ff:fec3:5bdf > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
    17:50:09.239999 IP6 fe80::3ae7:d8ff:fec3:5bdf > ff02::2: ICMP6, router solicitation, length 16
    17:50:09.256756 IP 192.168.1.124.52593 > 192.168.1.1.53: UDP, length 35
    17:50:12.733897 IP 192.168.1.124 > 8.8.8.8: ICMP echo request, id 768, seq 27136, length 40
    17:50:13.451490 IP 192.168.1.124.59641 > 192.168.1.1.53: UDP, length 49
    17:50:14.444473 IP 192.168.1.124.59641 > 192.168.1.1.53: UDP, length 49
    17:50:15.200454 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
    17:50:15.446253 IP 192.168.1.124.59641 > 192.168.1.1.53: UDP, length 49
    17:50:16.261378 IP 192.168.1.124.64347 > 192.168.1.1.53: UDP, length 35
    17:50:17.258703 IP 192.168.1.124.64347 > 192.168.1.1.53: UDP, length 35
    17:50:17.448950 IP 192.168.1.124.59641 > 192.168.1.1.53: UDP, length 49
    17:50:17.741902 IP 192.168.1.124 > 8.8.8.8: ICMP echo request, id 768, seq 27392, length 40
    17:50:18.260308 IP 192.168.1.124.64347 > 192.168.1.1.53: UDP, length 35
    17:50:19.386249 IP 192.168.1.124.50409 > 192.168.1.1.53: UDP, length 40
    17:50:19.454453 IP 192.168.1.124.59840 > 192.168.1.1.53: UDP, length 49
    17:50:20.063939 IP 192.168.1.124.17500 > 255.255.255.255.17500: UDP, length 109
    17:50:20.099778 IP 192.168.1.124.17500 > 255.255.255.255.17500: UDP, length 109
    17:50:20.130815 IP 192.168.1.124.17500 > 192.168.1.255.17500: UDP, length 109
    17:50:20.164213 IP 192.168.1.124.17500 > 255.255.255.255.17500: UDP, length 109
    17:50:20.263254 IP 192.168.1.124.64347 > 192.168.1.1.53: UDP, length 35
    17:50:20.383401 IP 192.168.1.124.50409 > 192.168.1.1.53: UDP, length 40
    17:50:20.453533 IP 192.168.1.124.59840 > 192.168.1.1.53: UDP, length 49
    17:50:21.384966 IP 192.168.1.124.50409 > 192.168.1.1.53: UDP, length 40

    The logs look something like this (it wouldnt let me download for some reason).

    Aug 24 17:55:53 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    Aug 24 17:54:53 apinger: Error while feeding rrdtool: Broken pipe
    Aug 24 17:52:39 sshd[19555]: Accepted password for admin from 192.168.1.124 port 4461 ssh2
    Aug 24 17:52:02 sshd[40896]: Received disconnect from 192.168.1.124: 11: Connection discarded by broker
    Aug 24 17:50:53 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    Aug 24 17:50:21 kernel: rl2: promiscuous mode disabled
    Aug 24 17:49:53 apinger: Error while feeding rrdtool: Broken pipe
    Aug 24 17:49:34 kernel: rl2: promiscuous mode enabled
    Aug 24 17:45:53 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    Aug 24 17:45:52 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.124
    Aug 24 17:45:52 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.124
    Aug 24 17:45:19 php: : Creating rrd update script
    Aug 24 17:44:53 apinger: Error while feeding rrdtool: Broken pipe
    Aug 24 17:42:47 sshd[40896]: Accepted password for admin from 192.168.1.124 port 4428 ssh2
    Aug 24 17:42:17 php: : Hotplug event detected for opt1 but ignoring since interface is configured with static IP ()
    Aug 24 17:42:15 kernel: rl0: link state changed to DOWN
    Aug 24 17:42:15 check_reload_status: Linkup starting rl0
    Aug 24 17:40:53 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
    Aug 24 17:39:53 apinger: Error while feeding rrdtool: Broken pipe
    Aug 24 17:39:00 php: : Resyncing OpenVPN instances for interface WAN.
    Aug 24 17:38:54 php: : phpDynDNS: (Success) DNS hostname update successful.
    Aug 24 17:38:54 php: : phpDynDNS: updating cache file /conf/dyndns_wannoip'malc.no-ip.info'.cache: 81.155.36.99
    Aug 24 17:38:54 php: : DynDns debug information: 81.155.36.99 extracted from local system.
    Aug 24 17:38:54 php: : DynDns: Current Service: noip
    Aug 24 17:38:54 php: : DynDns: DynDns _checkStatus() starting.
    Aug 24 17:38:53 php: : DynDns: DynDns _update() starting.
    Aug 24 17:38:53 php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 217.43.234.146 WAN IP: 81.155.36.99
    Aug 24 17:38:53 php: : DynDns: Current WAN IP: 81.155.36.99 Cached IP: 217.43.234.146
    Aug 24 17:38:53 php: : DynDns debug information: 81.155.36.99 extracted from local system.
    Aug 24 17:38:53 php: : DynDns: updatedns() starting
    Aug 24 17:38:53 apinger: Starting Alarm Pinger, apinger(36058)
    Aug 24 17:38:53 check_reload_status: Reloading filter
    Aug 24 17:38:52 php: : ROUTING: change default route to 217.47.207.58
    Aug 24 17:38:20 apinger: No usable targets found, exiting
    Aug 24 17:38:20 apinger: Starting Alarm Pinger, apinger(31997)
    Aug 24 17:38:20 check_reload_status: Reloading filter
    Aug 24 17:38:18 php: : rc.newwanip: on (IP address: 192.168.1.1) (interface: lan) (real interface: rl2).
    Aug 24 17:38:18 php: : rc.newwanip: Informational is starting rl2.
    Aug 24 17:38:16 login: login on ttyv0 as root
    Aug 24 17:38:16 check_reload_status: rc.newwanip starting rl2
    Aug 24 17:38:16 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.1)
    Aug 24 17:38:14 kernel: rl1: link state changed to UP
    Aug 24 17:38:14 check_reload_status: Linkup starting rl1
    Aug 24 17:38:14 kernel: rl2: link state changed to UP
    Aug 24 17:38:14 check_reload_status: Linkup starting rl2
    Aug 24 17:38:13 php: : Restarting/Starting all packages.
    Aug 24 17:38:12 kernel: pflog0: promiscuous mode enabled
    Aug 24 17:38:12 sshlockout[16164]: sshlockout/webConfigurator v3.0 starting up
    Aug 24 17:38:12 sshd[16142]: Server listening on 0.0.0.0 port 22.
    Aug 24 17:38:12 sshd[16142]: Server listening on :: port 22.
    Aug 24 17:38:12 kernel: WARNING: R/W mount of / denied. Filesystem is not clean - run fsck
    Aug 24 17:38:12 kernel: WARNING: / was not properly dismounted
    Aug 24 17:38:12 kernel: Trying to mount root from ufs:/dev/ad0s1a
    Aug 24 17:38:12 kernel: uhub3: 6 ports with 6 removable, self powered
    Aug 24 17:38:12 kernel: Root mount waiting for: usbus3
    Aug 24 17:38:12 kernel: Root mount waiting for: usbus3
    Aug 24 17:38:12 kernel: Root mount waiting for: usbus3
    Aug 24 17:38:12 kernel: GEOM: ad0s1: geometry does not match label (16h,63s != 16h,255s).
    Aug 24 17:38:12 kernel: acd0: CDRW <philips cdd5301="" h1.1="">at ata1-master UDMA33
    Aug 24 17:38:12 kernel: GEOM: ad0: partition 1 does not end on a track boundary.
    Aug 24 17:38:12 kernel: GEOM: ad0: partition 1 does not start on a track boundary.
    Aug 24 17:38:12 kernel: uhub2: 2 ports with 2 removable, self powered
    Aug 24 17:38:12 kernel: uhub1: 2 ports with 2 removable, self powered
    Aug 24 17:38:12 kernel: uhub0: 2 ports with 2 removable, self powered
    Aug 24 17:38:12 kernel: uhub3: <sis 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus3
    Aug 24 17:38:12 kernel: ugen3.1: <sis>at usbus3
    Aug 24 17:38:12 kernel: uhub2: <sis 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
    Aug 24 17:38:12 kernel: ugen2.1: <sis>at usbus2
    Aug 24 17:38:12 kernel: uhub1: <sis 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
    Aug 24 17:38:12 kernel: ugen1.1: <sis>at usbus1
    Aug 24 17:38:12 kernel: uhub0: <sis 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
    Aug 24 17:38:12 kernel: ugen0.1: <sis>at usbus0
    Aug 24 17:38:12 kernel: ad0: 78167MB <maxtor 6y080l0="" yar41bw0="">at ata0-master UDMA133
    Aug 24 17:38:12 kernel: usbus3: 480Mbps High Speed USB v2.0
    Aug 24 17:38:12 kernel: usbus2: 12Mbps Full Speed USB v1.0
    Aug 24 17:38:12 kernel: usbus1: 12Mbps Full Speed USB v1.0
    Aug 24 17:38:12 kernel: usbus0: 12Mbps Full Speed USB v1.0
    Aug 24 17:38:12 kernel: IPsec: Initialized Security Association Processing.
    Aug 24 17:38:12 kernel: firewire0: bus manager 0
    Aug 24 17:38:12 kernel: firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me)
    Aug 24 17:38:12 kernel: Timecounters tick every 1.000 msec
    Aug 24 17:38:12 kernel: Timecounter "TSC" frequency 2589374588 Hz quality 800
    Aug 24 17:38:12 kernel: p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
    Aug 24 17:38:12 kernel: atkbd0: [ITHREAD]
    Aug 24 17:38:12 kernel: atkbd0: [GIANT-LOCKED]
    Aug 24 17:38:12 kernel: kbd0 at atkbd0
    Aug 24 17:38:12 kernel: atkbd0: <at keyboard="">irq 1 on atkbdc0
    Aug 24 17:38:12 kernel: atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
    Aug 24 17:38:12 kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    Aug 24 17:38:12 kernel: sc0: VGA <16 virtual consoles, flags=0x300>
    Aug 24 17:38:12 kernel: sc0: <system console="">at flags 0x100 on isa0
    Aug 24 17:38:12 kernel: orm0: <isa option="" roms="">at iomem 0xc0000-0xcbfff,0xcc000-0xd3fff pnpid ORM0000 on isa0
    Aug 24 17:38:12 kernel: pmtimer0 on isa0
    Aug 24 17:38:12 kernel: ppi0: <parallel i="" o="">on ppbus0
    Aug 24 17:38:12 kernel: lpt0: Interrupt-driven port
    Aug 24 17:38:12 kernel: lpt0: [ITHREAD]
    Aug 24 17:38:12 kernel: lpt0: <printer>on ppbus0
    Aug 24 17:38:12 kernel: plip0: [ITHREAD]
    Aug 24 17:38:12 kernel: plip0: <plip network="" interface="">on ppbus0
    Aug 24 17:38:12 kernel: ppbus0: <parallel port="" bus="">on ppc0
    Aug 24 17:38:12 kernel: ppc0: [ITHREAD]
    Aug 24 17:38:12 kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
    Aug 24 17:38:12 kernel: ppc0: <parallel port="">port 0x378-0x37f,0x778-0x77b irq 7 on acpi0
    Aug 24 17:38:12 kernel: uart0: [FILTER]
    Aug 24 17:38:12 kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
    Aug 24 17:38:12 kernel: fdc0: [FILTER]
    Aug 24 17:38:12 kernel: fdc0: <floppy drive="" controller="">port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0
    Aug 24 17:38:12 kernel: atrtc0: <at realtime="" clock="">port 0x70-0x73 irq 8 on acpi0
    Aug 24 17:38:12 kernel: acpi_tz0: <thermal zone="">on acpi0
    Aug 24 17:38:12 kernel: rl2: [ITHREAD]
    Aug 24 17:38:12 kernel: rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Aug 24 17:38:12 kernel: rlphy2: <realtek internal="" media="" interface="">PHY 0 on miibus2
    Aug 24 17:38:12 kernel: miibus2: <mii bus="">on rl2
    Aug 24 17:38:12 kernel: rl2: <realtek 10="" 8139="" 100basetx="">port 0xc400-0xc4ff mem 0xec127000-0xec1270ff irq 18 at device 15.0 on pci0
    Aug 24 17:38:12 kernel: rl1: [ITHREAD]
    Aug 24 17:38:12 kernel: rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Aug 24 17:38:12 kernel: rlphy1: <realtek internal="" media="" interface="">PHY 0 on miibus1
    Aug 24 17:38:12 kernel: miibus1: <mii bus="">on rl1
    Aug 24 17:38:12 kernel: rl1: <realtek 10="" 8139="" 100basetx="">port 0xc000-0xc0ff mem 0xec126000-0xec1260ff irq 19 at device 8.0 on pci0
    Aug 24 17:38:12 kernel: rl0: [ITHREAD]
    Aug 24 17:38:12 kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Aug 24 17:38:12 kernel: rlphy0: <realtek internal="" media="" interface="">PHY 0 on miibus0
    Aug 24 17:38:12 kernel: miibus0: <mii bus="">on rl0
    Aug 24 17:38:12 kernel: rl0: <realtek 10="" 8139="" 100basetx="">port 0xbc00-0xbcff mem 0xec125000-0xec1250ff irq 17 at device 6.0 on pci0
    Aug 24 17:38:12 kernel: usbus3: <ehci (generic)="" usb="" 2.0="" controller="">on ehci0
    Aug 24 17:38:12 kernel: usbus3: EHCI version 1.0
    Aug 24 17:38:12 kernel: ehci0: [ITHREAD]
    Aug 24 17:38:12 kernel: ehci0: <ehci (generic)="" usb="" 2.0="" controller="">mem 0xec124000-0xec124fff irq 23 at device 3.3 on pci0
    Aug 24 17:38:12 kernel: usbus2: <sis 5571="" usb="" controller="">on ohci2
    Aug 24 17:38:12 kernel: ohci2: [ITHREAD]
    Aug 24 17:38:12 kernel: ohci2: <sis 5571="" usb="" controller="">mem 0xec123000-0xec123fff irq 22 at device 3.2 on pci0
    Aug 24 17:38:12 kernel: usbus1: <sis 5571="" usb="" controller="">on ohci1
    Aug 24 17:38:12 kernel: ohci1: [ITHREAD]
    Aug 24 17:38:12 kernel: ohci1: <sis 5571="" usb="" controller="">mem 0xec122000-0xec122fff irq 21 at device 3.1 on pci0
    Aug 24 17:38:12 kernel: usbus0: <sis 5571="" usb="" controller="">on ohci0
    Aug 24 17:38:12 kernel: ohci0: [ITHREAD]
    Aug 24 17:38:12 kernel: ohci0: <sis 5571="" usb="" controller="">mem 0xec121000-0xec121fff irq 20 at device 3.0 on pci0
    Aug 24 17:38:12 kernel: pci0: <multimedia, audio="">at device 2.7 (no driver attached)
    Aug 24 17:38:12 kernel: ata1: [ITHREAD]
    Aug 24 17:38:12 kernel: ata1: <ata 1="" channel="">on atapci0
    Aug 24 17:38:12 kernel: ata0: [ITHREAD]
    Aug 24 17:38:12 kernel: ata0: <ata 0="" channel="">on atapci0
    Aug 24 17:38:12 kernel: atapci0: <sis 962="" 963="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4000-0x400f irq 16 at device 2.5 on pci0
    Aug 24 17:38:12 kernel: fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode
    Aug 24 17:38:12 kernel: fwohci0: fwohci_intr_core: BUS reset
    Aug 24 17:38:12 kernel: fwohci0: Initiate bus reset
    Aug 24 17:38:12 kernel: dcons_crom0: bus_addr 0x1888000
    Aug 24 17:38:12 kernel: dcons_crom0: <dcons configuration="" rom="">on firewire0
    Aug 24 17:38:12 kernel: fwip0: Firewire address: 00:00:10:dc:00:1a:d8:20 @ 0xfffe00000000, S400, maxrec 2048
    Aug 24 17:38:12 kernel: fwip0: <ip over="" firewire="">on firewire0
    Aug 24 17:38:12 kernel: if_fwe0: Fake Ethernet address: 02:00:10:1a:d8:20
    Aug 24 17:38:12 kernel: fwe0: <ethernet over="" firewire="">on firewire0
    Aug 24 17:38:12 kernel: firewire0: <ieee1394(firewire) bus="">on fwohci0
    Aug 24 17:38:12 kernel: fwohci0: Link S400, max_rec 2048 bytes.
    Aug 24 17:38:12 kernel: fwohci0: Phy 1394a available S400, 2 ports.
    Aug 24 17:38:12 kernel: fwohci0: EUI64 00:00:10:dc:00:1a:d8:20
    Aug 24 17:38:12 kernel: fwohci0: No. of Isochronous channels is 4.
    Aug 24 17:38:12 kernel: fwohci0: OHCI version 1.0 (ROM=1)
    Aug 24 17:38:12 kernel: fwohci0: [ITHREAD]
    Aug 24 17:38:12 kernel: fwohci0: <sis 7007="">mem 0xec120000-0xec120fff irq 17 at device 2.3 on pci0
    Aug 24 17:38:12 kernel: isa0: <isa bus="">on isab0
    Aug 24 17:38:12 kernel: isab0: <pci-isa bridge="">at device 2.0 on pci0
    Aug 24 17:38:12 kernel: vgapci0: <vga-compatible display="">port 0x9000-0x907f mem 0xe0000000-0xe7ffffff,0xec000000-0xec01ffff irq 16 at device 0.0 on pci1
    Aug 24 17:38:12 kernel: pci1: <pci bus="">on pcib1
    Aug 24 17:38:12 kernel: pcib1: <pci-pci bridge="">at device 1.0 on pci0
    Aug 24 17:38:12 kernel: agp0: <sis 651="" host="" to="" agp="" bridge="">on hostb0
    Aug 24 17:38:12 kernel: pci0: <acpi pci="" bus="">on pcib0
    Aug 24 17:38:12 kernel: pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff,0x480-0x48f,0x1000-0x10bf,0x10c0-0x113f on acpi0
    Aug 24 17:38:12 kernel: acpi_button1: <sleep button="">on acpi0
    Aug 24 17:38:12 kernel: acpi_button0: <power button="">on acpi0
    Aug 24 17:38:12 kernel: cpu0: <acpi cpu="">on acpi0
    Aug 24 17:38:12 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
    Aug 24 17:38:12 kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
    Aug 24 17:38:12 kernel: acpi0: Power Button (fixed)
    Aug 24 17:38:12 kernel: acpi0: [ITHREAD]
    Aug 24 17:38:12 kernel: acpi0: <award awrdacpi="">on motherboard
    Aug 24 17:38:12 kernel: padlock0: No ACE support.
    Aug 24 17:38:12 kernel: cryptosoft0: <software crypto="">on motherboard
    Aug 24 17:38:12 kernel: kbd1 at kbdmux0
    Aug 24 17:38:12 kernel: wlan: mac acl policy registered
    Aug 24 17:38:12 kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc076b830, 0) error 1
    Aug 24 17:38:12 kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Aug 24 17:38:12 kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Aug 24 17:38:12 kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc076b770, 0) error 1
    Aug 24 17:38:12 kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Aug 24 17:38:12 kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Aug 24 17:38:12 kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xc076b6b0, 0) error 1
    Aug 24 17:38:12 kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Aug 24 17:38:12 kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Aug 24 17:38:12 kernel: module_register_init: MOD_LOAD (wpi_fw, 0xc095ffd0, 0) error 1
    Aug 24 17:38:12 kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
    Aug 24 17:38:12 kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
    Aug 24 17:38:12 kernel: ioapic0 <version 1.4="">irqs 0-23 on motherboard
    Aug 24 17:38:12 kernel: ioapic0: Changing APIC ID to 2
    Aug 24 17:38:12 kernel: ACPI APIC Table: <award awrdacpi="">Aug 24 17:38:12 kernel: avail memory = 1019367424 (972 MB)
    Aug 24 17:38:12 kernel: real memory = 1073741824 (1024 MB)
    Aug 24 17:38:12 kernel: Features2=0x400 <cnxt-id>Aug 24 17:38:12 kernel: Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Aug 24 17:38:12 kernel: Origin = "GenuineIntel" Id = 0xf27 Family = f Model = 2 Stepping = 7

    Anything else you'd like to see?</fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe></cnxt-id></award></version></software></award></acpi></power></sleep></acpi></acpi></sis></pci-pci></pci></vga-compatible></pci-isa></isa></sis></ieee1394(firewire)></ethernet></ip></dcons></sis></ata></ata></multimedia,></sis></sis></sis></sis></sis></sis></ehci></ehci></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></thermal></at></floppy></parallel></parallel></plip></printer></parallel></isa></system></generic></keyboard></at></cpu></maxtor></sis></sis></sis></sis></sis></sis></sis></sis></philips>

    0
  • M

    Are you having multiwan? you're logs show multiple public ip's as gateway

    0
  • M

    @Metu69salemi:

    Are you having multiwan? you're logs show multiple public ip's as gateway

    Nope and not sure I follow. Ther eare 3 interfaces - but the OPT1 isnt connected to anything so I think it has powered down at startup. the remaining interfaces are rl2 being the LAN (which sometimes describes itself as fwep0 I think) and rl1 the WAN side (sometimes calling itself fw something)

    0
  • M

    weird, if your hardware doesnt even know what it has inside

    0
  • M

    @Metu69salemi:

    weird, if your hardware doesnt even know what it has inside

    Its been fun trying to get it work in the first palce. If I used autodetect when setting up te interfaces it came up with the strange names. But after setting up as rl0 etc it worked fine for long enough.

    0
  • Netgate Administrator

    fwep0 and fwip0 are your firewire interface. Probably worth disabling it in the bios if you're not using it. I doubt it will have any effect on your problem.

    Steve

    0
  • M

    @stephenw10:

    fwep0 and fwip0 are your firewire interface. Probably worth disabling it in the bios if you're not using it. I doubt it will have any effect on your problem.

    Steve

    Thanks for that. A bit weird as when I set it up using autodetect it would pick these up even when I jammed the ethernet cable into the NICs. Might see if I can disable the firewire altogether grabs handful of wire.

    Thanks for that one. :)

    0
  • M

    bump ANyone any other ideas?

    It did ask me to run fsck but I can't make head nor tail of what came out of that.

    0
Log in to reply
 

Products

Services

Support

News

Resources

Company

Our Mission

We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive for past announcements.

© Copyright 2002 - 2019 Rubicon Communications, LLC | Privacy Policy