Re: [gentoo-user] SSL CUPS and SMTP on port 587
On Sun, Feb 17, 2008 at 07:18:00AM -0800, Penguin Lover Grant squawked: My ISP (Cox) blocks outgoing port 25 so I can't submit mail to my remote mail server. From what I understand, port 587 is commonly used to get around this. Can I have postfix listen on port 25 and port 587? Has anyone set that up? I do it slightly differently: I leave an SSH connection from my box to the mail server, which maps some local port to port 25 on the mail server, and send all my mail to the local port. HTH, W -- `Incidentally,' he said, `what does teleport mean?' Another moment passed. Slowly, the others turned to face him. `Probably the wrong moment to ask,' said Arthur, `It's just I remember you use the word a short while ago and I only bring it up because...' `Where,' said Ford quietly, `does it say teleport?' `Well, just over here in fact,' said Arthur, pointing at a dark control box in the rear of the cabin, `Just under the word emergency, above the word system and beside the sign saying out of order.' - Arthur finding an escape route from a certain death situation. Sortir en Pantoufles: up 436 days, 15:48 -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver)
On 12 Jun 2009, at 00:38, Grant wrote: ... I've almost got this working, but I don't know what to include in the /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 device or configuration. Do I need one? If I leave INTERFACES empty and I don't start net.wlan0, I don't have a way to define the IP address for the AP, and shorewall's loc zone is empty because net.wlan0 hasn't started. What do you want to do with your accesspoint. You will need a bridge to a wired network if you want your ap attached to that wired network. This is quite usual though... Without a bridge to a wired network, only the wlan systems are connected and can not connect to your wired systems. That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right now I just want to get wlan0 working. Do you know how to do that? I can't start net.wlan0 because it chokes on master mode, so I don't know how to specify an IP for the AP or how to fill shorewall's loc zone as that is normally filled by net.wlan0. Hi there, I haven't used Shorewall, but for this you probably want to use bridging. I fear that may not be available in Shorewall's UI. I originally wrote http://en.gentoo-wiki.com/wiki/Wireless/ Access_point, but that was some years ago now. It has had many contributions since, but I have no idea if it's up to date. Anyway, using the simple NAT-forwarding setup described in that article (surely possible in Shorewall) the wireless laptop can access the internet and wired PCs on the LAN. However it is not possible for wired PCs to (say) browse to file shares on the laptop without port- forwarding - because you use a NAT, you have exactly the same problem as accessing your home-server from the office. Bridging brings the wireless clients *seamlessly* into the wired LAN - they behave exactly like the wired clients do. One can install Apache on the wireless laptop and immediately connect to it from a wired PC. This is how all standalone ADSL wireless routers (eg Netgear DG834G) operate. I can't be of much practical help, as I have for some time been using a Fon access-point, which is plugged into a network switch near my desk and which gives me NATted wifi. It works, but I sure do miss teleportd http://abyssoft.com/software/teleport/, which is crippled without bridging. Stroller.
Re: [gentoo-user] wireless access point setup - bridging vs. routing (Was: Atheros kernel driver)
I've almost got this working, but I don't know what to include in the /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 device or configuration. Do I need one? If I leave INTERFACES empty and I don't start net.wlan0, I don't have a way to define the IP address for the AP, and shorewall's loc zone is empty because net.wlan0 hasn't started. What do you want to do with your accesspoint. You will need a bridge to a wired network if you want your ap attached to that wired network. This is quite usual though... Without a bridge to a wired network, only the wlan systems are connected and can not connect to your wired systems. That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right now I just want to get wlan0 working. Do you know how to do that? I can't start net.wlan0 because it chokes on master mode, so I don't know how to specify an IP for the AP or how to fill shorewall's loc zone as that is normally filled by net.wlan0. Hi there, I haven't used Shorewall, but for this you probably want to use bridging. I fear that may not be available in Shorewall's UI. I originally wrote http://en.gentoo-wiki.com/wiki/Wireless/Access_point, but that was some years ago now. It has had many contributions since, but I have no idea if it's up to date. Anyway, using the simple NAT-forwarding setup described in that article (surely possible in Shorewall) the wireless laptop can access the internet and wired PCs on the LAN. However it is not possible for wired PCs to (say) browse to file shares on the laptop without port-forwarding - because you use a NAT, you have exactly the same problem as accessing your home-server from the office. Bridging brings the wireless clients *seamlessly* into the wired LAN - they behave exactly like the wired clients do. One can install Apache on the wireless laptop and immediately connect to it from a wired PC. This is how all standalone ADSL wireless routers (eg Netgear DG834G) operate. I can't be of much practical help, as I have for some time been using a Fon access-point, which is plugged into a network switch near my desk and which gives me NATted wifi. It works, but I sure do miss teleportd http://abyssoft.com/software/teleport/, which is crippled without bridging. Stroller. Thanks Stroller. I'm into bridging eth1 and wlan0, but the truth is I don't even have an eth1 right now, although I plan to in the future. When I get eth1 going I'll bridge em for sure. - Grant
