4. Strange Playstation 3 issue. DHCP DNS related?

Strange Playstation 3 issue. DHCP DNS related?

  • N

    So here is my issue… I have a Playstation 3, Xbox 360, and a few computers plugged into a switch. I used to have a WRT54G as my router and everything was happy. Now everything works BUT my PS3 but I could only find info on UPnP and such but I can't even get that far...

    The PS3 will not get an IP address from the DHCP and here is what I've tried so far....

    Changing the patch cable
    Using the same port as a known working device
    Setting up a static DHCP with the MAC address
    Full static manual input

    When I do DHCP or Static DHCP it times out trying to get an address from the DHCP. When I set it all manually I can see my media server and from my desktop I can ping the PS3 but it still can't connect to the internet.

    Also I get the same exact results if I connect through my wireless access point.

    Any ideas?

    0
  • W

    Where is pfSense in this network? What version of pfSense?

    Have you had other systems successfully allocated an address by DHCP? Wired systems and wireless?

    0
  • N

    @wallabybob:

    Where is pfSense in this network? What version of pfSense?

    Have you had other systems successfully allocated an address by DHCP? Wired systems and wireless?

    I'm running 1.2-Release.

    The network is as follows…

    cable modem > pfSense > Cisco 2950 > 8 Port netgear switch

    I also have a WRT54G in AP mode plugged into the 2950, no DHCP on that just forwarding to the pfsense box

    I have 4+ computers plugged into the 2650 without any issues, 4 laptops that connect fine over wireless, then 3 computers, xbox 360 and PS3 all hook into the netgear. Everything on the netgear works except for the PS3. None of my devices have any static settings they all receive DHCP leases on a regular basis.

    0
  • W

    You have enough DHCP addresses?

    pfSense is actually seeing the DHCP request from the PS3?

    DHCP allocation to the PS3 is listed in the DHCP log? (from the web gui see Status -> DHCP leases and Status -> System logs, DHCP tab)

    0
  • N

    @wallabybob:

    You have enough DHCP addresses?

    pfSense is actually seeing the DHCP request from the PS3?

    DHCP allocation to the PS3 is listed in the DHCP log? (from the web gui see Status -> DHCP leases and Status -> System logs, DHCP tab)

    Yup I have plenty of free DHCP Addresses.

    Here is the PS3 hitting the DHCP in the log.

    10-22-2008 22:31:18 Local7.Info 192.168.18.1 Oct 23 07:31:17 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:18 Local7.Info 192.168.18.1 Oct 23 07:31:17 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:15 Local7.Info 192.168.18.1 Oct 23 07:31:14 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:15 Local7.Info 192.168.18.1 Oct 23 07:31:14 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:13 Local7.Info 192.168.18.1 Oct 23 07:31:12 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:13 Local7.Info 192.168.18.1 Oct 23 07:31:12 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:10 Local7.Info 192.168.18.1 Oct 23 07:31:09 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:10 Local7.Info 192.168.18.1 Oct 23 07:31:09 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:07 Local7.Info 192.168.18.1 Oct 23 07:31:07 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:07 Local7.Info 192.168.18.1 Oct 23 07:31:07 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:04 Local7.Info 192.168.18.1 Oct 23 07:31:04 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:04 Local7.Info 192.168.18.1 Oct 23 07:31:04 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:02 Local7.Info 192.168.18.1 Oct 23 07:31:01 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:31:02 Local7.Info 192.168.18.1 Oct 23 07:31:01 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:59 Local7.Info 192.168.18.1 Oct 23 07:30:58 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:59 Local7.Info 192.168.18.1 Oct 23 07:30:58 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:56 Local7.Info 192.168.18.1 Oct 23 07:30:56 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:56 Local7.Info 192.168.18.1 Oct 23 07:30:56 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:53 Local7.Info 192.168.18.1 Oct 23 07:30:53 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:53 Local7.Info 192.168.18.1 Oct 23 07:30:53 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:51 Local7.Info 192.168.18.1 Oct 23 07:30:50 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:51 Local7.Info 192.168.18.1 Oct 23 07:30:50 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:49 Local7.Info 192.168.18.1 Oct 23 07:30:48 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:49 Local7.Info 192.168.18.1 Oct 23 07:30:48 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:46 Local7.Info 192.168.18.1 Oct 23 07:30:46 dhcpd: DHCPOFFER on 192.168.18.240 to 00:19:c5:b0:e2:ac (skynetfw.local) via dc5
    10-22-2008 22:30:46 Local7.Info 192.168.18.1 Oct 23 07:30:46 dhcpd: DHCPDISCOVER from 00:19:c5:b0:e2:ac (skynetfw.local) via dc5

    0
  • W

    Given that you have had other systems accept a DHCP assigned address from pfsense and have communication between the PS3 and another system it looks as if the DHCP response to the PS3 is being generated and leaving the pfSense system in which case the DHCP response is possibly getting blocked between pfSense and the PS3 OR the PS3 is not accepting the response.

    Can you look at any sort of log on the PS3 or look at a trace on the PS3 LAN interface? Is there any sign the PS3 has seen the DHCP response?

    Is there any chance the PS3 might think a previously assigned DHCP lease for a different IP address is still current and is refusing to accept a different address and keeps retrying in the hope that some server will reassign the previously used IP address?

    Do you have any firewall rules that block the DHCP response to the PS3?

    0
  • L

    after having the same issue and playing around for hours, I came up with a workaround somewhat.

    You see - The PS3 fragments ip packets, but sets the DF bit to "1"

    To pf, this is a no no.

    The workaround I put in place gets my ps3 connected, but playing games online still has issues at times, depending on what game.

    I use a Nokia IP530 as my pfsense box, and a Cisco 2811 for GRE to my brother's house for off-site data replication.

    What I did was…

    1. Added a new vlan on my switch ( vlan 200 )
    2. Connected my Wireless ap (WRT54G w/ dd-wrt) and the Cisco 2811 Fa0/1 to Vlan 200
    3. Configured the management IP on the WRT54G and IP settings on Fa0/1
    4. Configured proper routing
    5. This is where it gets tricky - You need to tell the Cisco router to clear the "DF" bit in the IP packets that come from the PS3.  Do this by creating a route-map and placing an ip policy on the interface.  For example...

    access-list 100 permit tcp 192.168.20.0 0.0.0.255 any
    route-map cleardf permit 10
    match ip address 100
    set ip df 0
    !
    inter fa0/1
    ip policy route-map cleardf
    !

    After that's all said and done, by running a tcpdump on the interface between your router and firewall, you should see that the flags on the packets coming from the ps3 have been set to None (instead of [DF] like before), and your ps3 will connect.

    You could also setup another router (actiontec… dlink... linksys etc...) behind your pfsense box and connect your ps3 to that.  I got it to work that way as well... double natting.  I guess the lower-grade routers don't seem to care about the DF bit.

    Hope this helps...

    0
  • K

    You could try if setting the System->Advanced->"Clear DF bit instead of dropping" -option makes any difference.

    0
  • L

    doesn't work for some reason… tried it.

    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 2019 Rubicon Communications, LLC | Privacy Policy