![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Network geeking
Well I swapped out the 802.11b router and NIC for 802.11g versions today. It was painless but I'm not sure the port triggering for bittorrent is working properly. It could just be that the swarms for the two torrents I'm using to test things are slow as well as small. With the previous router I had issues with DHCP so I had static IPs on the local machines and therefore could use port forwarding to send all torrent traffic to my machine. Since ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
hafoc doesn't use bittorrent that was an adequate solution. Now that DHCP is working on the LAN I figured that I should use port triggering to avoid a possible (though unlikely) IP change issue but I'm not seeing the nice little green "lights" on my torrents, just the yellow of a firewalled connection. I haven't made any changes to the firewall and it was working fine with the old router so something must be up with the router settings. I tried port forwarding for the heck of it but there was no appreciable change so I don't think it's the fact I went over to port triggering that's keeping the "your firewalled" indicator up.
Now pardon me while I go and happily geek for a bit more. :)
hafoc doesn't use bittorrent that was an adequate solution. Now that DHCP is working on the LAN I figured that I should use port triggering to avoid a possible (though unlikely) IP change issue but I'm not seeing the nice little green "lights" on my torrents, just the yellow of a firewalled connection. I haven't made any changes to the firewall and it was working fine with the old router so something must be up with the router settings. I tried port forwarding for the heck of it but there was no appreciable change so I don't think it's the fact I went over to port triggering that's keeping the "your firewalled" indicator up.Now pardon me while I go and happily geek for a bit more. :)